Convergence 1.0 Initial Configuration

Completing the Sun Convergence Installation: Initial Configuration

After you install the Convergence software with the Communications Suite installer, you must configure the Convergence to complete the installation. You perform this initial runtime configuration by running the Convergence configuration program, init-config.

After you configure Convergence the first time, you can change the configuration settings and property values by using the Convergence command-line interface, iwcadmin. For more information about ongoing administration of Convergence, see Convergence Administration Guide.

This chapter describes the following topics:

Gather Your Convergence Configuration Information

Convergence Components

You can configure the Convergence to communicate with the following back-end Communication Suite servers:

  • Messaging Server
  • Calendar Server
  • Instant Messaging Server

You can choose to configure any or all of these components. Only the configured components will appear in the Convergence user interface and be available to all Convergence users.

Configure Messaging Server and Calendar Server First

Before you run the Convergence configuration program, you must install and configure Messaging Server and Calendar Server (if you want to use these services in Convergence).

You do not have to configure IM before you configure Convergence. However, to enable IM service, you must take the steps described in Configure IM Components to Enable Communication with Instant Messaging Server.

Web Containers

The Convergence server must be deployed to a Web container. You can configure Convergence on

  • Sun Java TM System Application Server 9.1 Update 1

Configuration Worksheets

Before you run the configuration program, you should gather configuration information by filling out the Convergence Configuration Worksheets.

Configure IM Components to Enable Communication with the Instant Messaging Server

To enable Convergence to communicate with Instant Messaging Server, you must configure values for the following IM Server features before you run the Convergence configuration program:

  • Httpbind Component JID
  • Httpbind Component Password
  • Avatar Component JID
  • Avatar Component Password

You need to configure these components manually, after you install and configure IM.

A Note About Configuring the IM Server

When you are configuring the Instant Messaging Server (with the IM configure utility), be sure that the XMPP/HTTP Gateway Deployment parameter is set false. The XMPP/HTTP Gateway is deployed through the Convergence server; its value is set when you configure Convergence.

About the Httpbind Component JID and Avatar Component JID

The Httpbind JID and Avatar JID can be any string. These values do not have to identify a particular IM host and domain name. However, these values should be meaningful. For example, a good practice might be to include the host and domain name in these JIDs to make the identifiers easy to recognize.

The passwords for Httpbind JID and Avatar JID can be unique. They do not have to match any other password used for IM or another back-end service.

The JIDs and passwords that you configure in the iim.conf file must match the Httpbind and Avatar JIDs that you will configure when you configure Convergence with the init-config program.

Configuring Multiple Instances of Convergence with One IM Server

If you are configuring multiple instances of Convergence to use one IM server, you must add a unique httpbind and avatar.jid value for each instance of Convergence. For example, if you configure three instances of Convergence, the IM server configuration (iim.conf) file must have three instances of httpbind component configuration:

iim_server.components=agent-calendar,httpbind1,httpbind2,httpbind3,avatar1,avatar2,avatar3

! httpbind1 component (HTTP/XMPP Gateway)
! ======================================
iim_agent.httpbind1.enable="true"
httpbind1.jid=convergence1-jid
httpbind1.password=secret

! httpbind2 component (HTTP/XMPP Gateway)
! ======================================
iim_agent.httpbind2.enable="true"
httpbind2.jid=convergence2-jid
httpbind2.password=secret

! httpbind3 component (HTTP/XMPP Gateway)
! ======================================
iim_agent.httpbind3.enable="true"
httpbind3.jid=convergence3-jid
httpbind3.password=secret

Similarly, in this example, the IM server configuration (iim.conf) file must have three instances of avatar component configuration:

! avatar1 component
! =======================
iim_agent.avatar1.enable = "true"
avatar1.jid=convergence1-jid 
avatar1.password=secret 

! avatar2 component
! =======================
iim_agent.avatar2.enable = "true"
avatar2.jid=convergence2-jid 
avatar2.password=secret 

! avatar3 component
! =======================
iim_agent.avatar3.enable = "true"
avatar3.jid=convergence3-jid 
avatar3.password=secret

You must run the Convergence init-config script for each instance of Convergence. For details, see Run the Convergence Configuration Program. When you set the values for the Httpbind Component JID and Aavatar Component JID, be sure that these values correspond to the values you have set for this particular instance of Convergence in the iim.conf file.

To configure the IM Server components

  1. Perform the initial configuration of Instant Messaging by running the IM configure program. For details, see Completing the Instant Messaging 7.3 Installation: Initial Configuration.
  2. Edit the im-svr-base/config/iim.conf file.

    By default, the im-svr-base is /opt/sun/comms/im on Solaris and Linux systems.
  3. Add the Avatar component to the im_server.components property. For example, this entry can look like this:
     im_server.components = "agent-calendar, httpbind, avatar"


  4. Set the iim_agent.enable property to true.

  5. Provide the Httpbind JID and password. For example:
    httpbind.varrius.com


  6. Add the following entries to configure the Avatar component:
    ! avatar component
! =============
iim_agent.avatar.enable = "true"
avatar.jid = "<avatar.varrius.com>"
avatar.password = "<password>"


    If you are configuring more than one Convergence client to use this IM server, add a unique httpbind and avatar.jid value for each instance of Convergence. For details, see Configuring Multiple Instances of Convergence with One IM Server.

  7. Restart IM Server.

Run the Convergence Configuration Program

The steps described in this section walk you through configuring Convergence by using the configuration program, init-config.

Before you run the configuration program

Be sure that the back-end servers and web container are up and running:

  • Directory Server
  • Messaging Server
  • Calendar Server
  • Application Server 9.1 Update 1

    Verify whether users are able to log in to the back-end servers correctly:
  • Messaging Server
  • Calendar Server

To launch the configuration program

  1. Log in as (or become) root.
  2. Go to the iwc-base/sbin directory.

    For example, on Solaris and Linux, go to:

    # cd /opt/sun/comms/iwc/sbin

  3. Enter the command:

    # ./init-config

    The configuration program starts, displaying the first panel. The sections that follow lead you through the configuration panels.

    This chapter describes how to run the configuration program in GUI mode.

    To invoke the configuration program in command-line (non-GUI) mode, enter the command:

    # ./init-config -nodisplay

To enter information in the configuration program panels

The following steps lead you sequentially through the panels displayed by the init-config program.

If you'd rather read a list than a task-based procedure, you can refer instead to the configuration values shown in Worksheet 1-1 and Worksheet 1-2 as you run the program.

  1. Welcome
    The first panel in the configuration program is a copyright page. Click Next.
  2. Select the directory to store configuration and data files

    Select the directory where you want to store the Convergence configuration and data files. The default configuration and data directory is located here:
    • Solaris and Linux: /var/opt/sun/comms/iwc
      This directory should be separate from the iwc-base directory. (On Solaris and Linux, this is /opt/sun/comms/iwc by default.)

      Enter the name of the directory, or keep the default, and click Next.

      If the directory does not exist, a dialog appears asking if you want to create the directory or choose a new directory. Click Create Directory to create the directory or Choose New to enter a new directory.

      A dialog appears indicating that the components are being loaded. This may take a few minutes.
  3. Select Services to configure

    Select the service or services you want to configure:
    • Mail Service---the Convergence servlets that communicate with Messaging Server and GUI components that provide end-user access to mail service.
    • Calendar Service---the Convergence servlets that communicate with Calendar Server and GUI components that provide end-user access to calendar service.
    • Instant Messaging Service---the Convergence servlets that communicate with Instant Messaging Server and GUI components that provide end-user access to Instant Messaging service.
      Note: To configure the Instant Messaging Service, you must also select either Mail Service or Calendar Service (or both). You cannot select Instant Messaging Service only.
      Click Next.
  4. Convergence server host name and DNS domain name

    Enter the host name of the machine on which Convergence is being configured.

    For example: mymachine

    Enter the DNS domain name of the Convergence host machine.

    For example: siroe.com

    Click Next.

  5. Application Server 9.1 Update 1 Configuration Details

    Installation directory. Enter the Application Server 9.1 installation directory. By default, on Solaris this directory is /opt/SUNWappserver.

    Domain directory. Enter the Application Server 9.1 domain directory. By default, on Solaris this directory is /opt/SUNWappserver/domains/domain1.

    Document root directory. Enter the Application Server 9.1 document root directory. By default, on Solaris this directory is /opt/SUNWappserver/domains/domain1/docroot.

    You can browse to select any of these directories.

    Server Target Name. Enter the Application Server 9.1 target name. For example: server.

    Virtual Server Identifier. Enter the Application Server 9.1 virtual server identifier. For example: server.

    Server Instance HTTP port. Enter the Application Server 9.1 target HTTP port number. Default port is 8080.

    Click Next.

    The configuration program checks if the directories you specified are valid. If a directory is invalid or does not exist, a dialog box tells you to choose a new directory.

    Next, the configuration program checks if an Application Server 9.1 target connection is alive. If not, a dialog box warns you that the configuration program could not connect to the specified target and your configuration may not be completed. You can accept the specified values or choose new Application Server 9.1 configuration values.
  6. Application Server: Administration Instance Details

    Administration Server Port. Enter the Administration Server port number. For example: 4848

    Administrator User ID. Enter the Administration Server administrator user ID. For example: admin

    Administrator Password. Enter the administrator user password.

    If you are using a Secure Administration Server Instance, check the Secure Administration Server Instance box. If you are not, leave the box unchecked.

    Click Next.

    The configuration program checks if an Application Server 9.1 Adminstration Instance is alive. If not, a dialog box warns you that the configuration program could not connect to the specified target and your configuration may not be completed. You can accept the specified values or choose new Application Server 9.1 configuration values.

    Next, the configuration program checks if the credentials are valid. An Information dialog box is displayed with Application Server's Administration Instance running in normal or secure mode.

  7. Enter the URI path where Convergence will be deployed.

    For example, enter /iwc.

    Click Next.
  8. Specify whether or not you want hosted domain support

    Select this option if you have enabled hosted domain support in both Calendar Server and Convergence.
  9. Specify the LDAP User/Group configuration details.

    The Communications Suite servers (Messaging Server, Calendar Server, Instant Messaging) store user and group data in an LDAP directory. This screen asks you to supply configuration information that enables the Convergence server to connect to the Directory Server managing this data.

    User/Group LDAP URL. Enter the LDAP host and port where the User/Group is located. The URL should be in the format: ldap://LDAP host name:LDAP port number.

    For example: ldap://siroe.com:389

    Bind DN. Enter the LDAP distinguished name (DN) of the administrator used to bind to the Directory Server. This administrator should have appropriate privileges to manage the User/Group data.

    For example cn=Directory Manager.

    Bind Password. Enter the password for the Bind DN.

    Click Next.

    The configuration program checks if the LDAP connection is alive and the credentials are valid. If not, an error box tells you that the configuration program could not connect to the specified target. You need to provide valid User/Group LDAP details.

  10. Confirm the base distinguished name (DN) of the DC Tree suffix.
    For example: o=isp

    The Convergence configuration program retrieves this base DN from the Directory Server and displays it. Use the displayed value, or change it if your configuration uses another base DN.

    This base DN is used to perform domain lookups. If the Communications Suite servers are using Schema 1, this configuration setting specifies the DN of the DC Tree suffix. If the Communications Suite servers are using Schema 2, this setting specifies the DN of the root suffix under which the User/Group tree is located. You must enter (confirm) a value for this item whether you are using Schema 1 or Schema 2.

    In a Schema 1 directory layout, Convergence uses the DC Tree suffix to search for domain information. In a Schema 2 directory layout, there is only one root suffix; both domain and user/group data are located under this one suffix.

    Click Next.

  11. Enter the default domain name.

    When a user logs into Convergence without including a mail domain component in the user name, this domain is used by default to supply the fully qualified domain name. The default domain name is used when a domain name is required but not provided explicitly during login/authentication.

    For example: sesta.com

    In this example, if a user logs in as fred, the user name is qualified as fred@sesta.com.

  12. Specify the Mail Service configuration details.

    This screen appears only if you selected Messaging Service in the Select Components to Be Configured screen.

    Webmail Host Name. Enter the name of the machine where Messaging Server is installed. For example: ms.sesta.com

    Webmail Server Port Number. Enter the Messaging Server HTTP (mshttpd) port number. For example, the default is: 8990

    Access in SSL mode. Select this option if you want a connection between Convergence and Messaging Server in secure mode. If you select this option, make sure that the Messaging Server Port Number provided above is an SSL port.


    Webmail Server Admin UserID. Enter the Messaging Server administrator user ID. For example: admin

    By default, the Messaging Server administrator user ID is admin. This value is chosen during Messaging Server configuration.

    Webmail Server Admin Password. Enter the Messaging Server administrator user password.

    Click Next.

    The configuration program checks if Messaging Server connection is alive and Credentials are valid. If not, a warning box displayed that the configuration program could not connect to the specified target.

  13. Specify the Calendar Service configuration details.

    This screen appears only if you selected Calendar Server in the Select Components to Be Configured screen.

    Calendar Server Host Name. Enter the name of the machine where Calendar Server is installed. For example: cs.siroe.com

    Calendar Server Port Number. Enter the Calendar Server HTTP port number. For example: 80 (Default Calendar Server port is 80.)

    Access in SSL mode. Select this option if you want connection between Commnucation Center and Calendar Server in secure mode, Make sure that Calendar Server Port Numebr provided above is SSL port if you select this option.


    Calendar Server Admin User ID. Enter the Calendar Server administrator user ID. For example: calmaster

    Calendar Server Admin Password. Enter the Calendar Server administrator user password.

    Click Next.

    The configuration program checks if the Calendar Server connection is alive and Credentials are valid. If not, a warning box is displayed, stating that the configuration program could not connect to the specified target.

  14. Specify the Instant Messaging Service configuration details.

    This screen appears only if you selected Instant Messaging Service in the Select Components to Be Configured screen.

    Note: You must configure the Httpbind Component JID, Httpbind Component Password, Avatar Component JID, and Avatar Component Password in the IM Server before you enter these values in the Convergence configuration program. For details, see Configure IM Components to Enable Communication with the Instant Messaging Server.

    Server Domain Name. Enter the domain name of the Instant Messaging server. For example: varrius.com. If multiple domains need to be supported, enter the domain names separated by spaces.
    Server Host Name. Enter the name of the machine where Instant Messaging is installed. For example: im.varrius.com

    Server Port Number. Enter the Instant Messaging Server HTTP port number. For example: 5269 ((Default Instant Messaging Server port is 5269.)

    Note: The following items, Httpbind Component JID, Httpbind Component Password, Avatar Component JID, and Avatar Component Password, must match the JID values and passwords that you configured in the iim.conf file for the IM Server. If multiple instances of Convergence use one IM server, these items must match the JID values in the iim.conf file configured for this particular instance of Convergence. For details, see Configuring Multiple Instances of Convergence with One IM Server.


    Httpbind Component JID. Enter Instant Messaging Server httpbind component JID. This value must match the JID you configured in the iim.conf file. For example: httpbind.varrius.com
    Httpbind Component Password. Enter the Instant Messaging Server httpbind component password
    Avatar Component JID. Enter Instant Messaging Server avatar component jid. For example: avatar.varrius.com
    Avatar Component Password. Enter Instant Messaging Server avatar component password.

    Click Next.
  15. Specify the Convergence Administrator details

    The Administrator username and password are needed for ongoing administration of Convergence, implemented by using the Administration Utility iwcadmin. The user details for the Convergence Administrator are stored in the Convergence configuration files, not in the Directory Server. This administrator user is not tied to any back-end server administrator accounts.

    Username. Enter the administrator username. For example admin

    Password. Enter the password, make sure that password is more than 6 charactors
    Password Again. Enter the password again to confirm
  16. Ready to Configure

    The verification panel displays the items that will be configured.

    Click Configure Now to begin the configuration.

    To change information on a previous panel, click Back.
  17. Task Sequence

    The Task Sequence Panel displays a sequence of tasks being performed. The actual configuration takes place as these tasks are displayed.

    When the panel displays "All Tasks Passed," you can click Next to continue or Cancel stop the tasks from being performed and exit.


  18. Installation Summary

    The Installation Summary panel displays the product installed and a Details... button that displays more information about this configuration.

    A log file for the init-config program is created in the iwc-base/install directory. (On Solaris and Linux, the default path is /opt/sun/comms/iwc/install.) The name of the log file is Iwc-config-YYYYMMDDHHMMSS.log, where YYYYMMDDHHMMSS identifies the 4-digit year, month, date, hour, minute, and second of the configuration.

    Click Close to complete the configuration.

Perform Silent Installation

The Convergence initial runtime configuration program automatically creates a silent installation state file (called saveState). This file contains internal information about the configuration program and is used for running silent installations.

The silent installation saveState file is stored in the /opt/sun/comms/iwc/data/setup/Iwc-config-YYYYMMDDHHMMSS/ directory, where YYYYMMDDHHMMSS identifies the 4-digit year, month, date, hour, minute, and second of the saveState file.

For example, once you have run the init-config program once, you can run it in silent install mode:

         _iwc-base_/sbin/init-config -nodisplay -noconsole -state
         _fullpath_/saveState

The fullpath variable is the full directory path of where the saveState file is located.

Labels

configuring configuring Delete
convergence convergence Delete
guide guide Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (14)

 

  1. Mar 12, 2008

    nate_keegan says:

    I am working on installing Kendo in the beta program with IM Server integration....

    I am working on installing Kendo in the beta program with IM Server integration.

    The section Configure IM Components to Enable Communication with the Instant Messaging Server mentions the following:

    Provide the Httpbind JID and password. the Httpbind JID should be a meaningful string
    What relationship does the JID have with a DNS name/hostname? Also, is the password mentioned here relative to a JCS component or something arbitrary for this portion of the configuration?

    The same is true of the avatar configuration (Add the following entries to configure the Avatar component)

    The same information on this page applies to the single host deployment ( http://wikis.sun.com/display/CommSuite/Sun+Java+Communications+Suite+6+on+a+Single+Host) as we are asked to add the following to iim.conf:

    iim_server.components = "agent-calendar,httpbind,avatar"
! httpbind component (HTTP/XMPP Gateway)
! ======================================
iim_agent.httpbind.enable = "true"
httpbind.jid = "wireless.httpbind.comms.beta.com"
httpbind.password = "adminpass"

! avatar component
! ======================================
iim_agent.avatar.enable = "true"
avatar.jid = "wireless.avatar.comms.beta.com"
avatar.password = "adminpass"

    I get that wireless.comms.beta.com is the hostname used in the single host deployment, however, is
    wireless.httpbind.comms.beta.com and wireless.avatar.comms.beta.com supposed to be an actual DNS/host name or
    is it an arbitrary thing for the sake of the configuration (if so it would seem that one would just use the actual
    DNS/host name of the IM server


    1. Mar 12, 2008

      joesciallo says:

      Nate, Here's what one of our engineers said: "As far as the JIDs are concerned...

      Nate,

      Here's what one of our engineers said:

      "As far as the JIDs are concerned, they can be any arbitrary string. We have been embedding the host and domain in the string by convention but it doesn't have to be that way. Because the server can be distributed from the gateway the only stipulation is that the entries in the server's iim.conf file and in the gateway config files should match. That goes for passwords too. So when you view the httpbind jid in the iim.conf and the httpbind.conf files they should match. The JID is our way of providing component authentication with the server. Naming all JIDs the same (such as hostname) will probably cause problems especially when the server is talking to multiple components which may be running on the same host. Hence we use "httpbind" and "avatar" in our examples to distinguish the two."

      1. Mar 13, 2008

        nate_keegan says:

        That makes sense I appreciate the clarification 

        That makes sense

        I appreciate the clarification 

  2. Mar 13, 2008

    Steven_Kahn says:

    Nate, Just revised this Communication Center Initial Configuration page to incor...

    Nate,
    Just revised this Communication Center Initial Configuration page to incorporate our experts' responses to your comments. See the section, "About the Httpbind Component JID and Avatar Component JID" and the revisions to Step 15 on configuring the IM components for Communication Center.

  3. May 12, 2008

    DNReddy says:

    If you'd rather read a list than a task-based procedure, you can refer instead...
    • If you'd rather read a list than a task-based procedure, you can refer instead to the configuration values shown in Table 1-1 and Table 1-2 as you run the program. => Links to Tables does not work.
    • Panel numbers are not in serials( 1 to 3, then again started from 1).
    • Panel headers : not consistant, few are BOLD, few are not.
    • Application Server Instance HTTP port. Enter the Application Server 9.1 target HTTP port number. => add Default port is 4848
    • Combine Panel 10 and 11(calendar details are collected in single panel now)
    • Calendar Server Port Number. Enter the Calendar Server HTTP port number. For example: 80 (default calendar server port is 80)
    • IM Server Port Number. Enter the Instant Messaging Server HTTP port number. For example: 5222 (default IM server port is 5222)

    1. May 12, 2008

      Steven_Kahn says:

      Reddy, Thanks for your comments. Michael incorporated them.

      Reddy,
      Thanks for your comments. Michael incorporated them.

  4. May 14, 2008

    DNReddy says:

    few corrections: Panel 5 : Server Instance HTTP port. Enter the Application Se...

    few corrections:

    • Panel 5 : Server Instance HTTP port. Enter the Application Server 9.1 target HTTP port number. Default port is 8080 not 4848
    • Panel 13: All calendar details are collected in one Panel, so
      • Change Panel heading to "Specify the Calendar Service configuration details."
      • Remove "Click Next" in the middle
      • Remove next line "The configuration program checks if Calendar Server connection is alive. If not, a warning box displayed that the configuration program could not connect to the specified target."
      • Remove next panel header(Specify the Calendar Server Administrator details.)
      • Change Last Line after "Click Next" to "configuration program checks if Calendar Server connection is alive and Credentials are valid. If not, a warning box displayed that the configuration program could not connect to the specified target."

  5. May 14, 2008

    Steven_Kahn says:

    Reddy-- Sorry we missed some of your earlier comments. Now all your most recent ...

    Reddy--
    Sorry we missed some of your earlier comments. Now all your most recent comments are incorporated & the changes made.

  6. Dec 05, 2008

    slon1975 says:

    I am attempting to connect Sun IM server with Sun Convergence client. I believe ...

    I am attempting to connect Sun IM server with Sun Convergence client. I believe I have setup the config files correctly (iim.conf and httpbind.conf), however in the log files for Sun IM, I am getting this error in xmppd.log

    [04 Dec 2008 18:52:23,484] WARN xmppd [default-iim_server-worker 3] [ComponentPacketDispatcher] failed to validate handshake for mailreader.httpbind.domain.com 07c7885111bfac3db54b6ef399cfc607c0547566 instead of a96c2c5e0d7be2d4dfb6961445d38b1f4ba4ec33

    Any idea with what I'm doing wrong? The settings in both files seem to match, password and JID are concerned. Any ideas would be great.

    1. Dec 05, 2008

      Swetha_Raj says:

      Could you also send the httpbind.log for the same ? You can set the log level to...

      Could you also send the httpbind.log for the same ?
      You can set the log level to DEBUG for both xmppd and httpbind logs.
      For debug logs of xmppd - Change the "log4j.logger.xmppd=DEBUG" in /opt/sun/comms/im/config/log4j.conf
      For debug logs of httpbind - Change the "log4j.logger.httpbind=DEBUG" in /opt/sun/comms/iwc/config/httpbind_log4j.conf

      Also check if the values for "iim_server.domainname" in iim.conf and "default.domains" in httpbind .conf match

      1. Dec 08, 2008

        slon1975 says:

        Swetha_Raj, Here is a snippet of the xmppd.log: bash-3.00# tail -f xmppd.log ...

        Swetha_Raj,

        Here is a snippet of the xmppd.log:

        bash-3.00# tail -f xmppd.log
        at java.lang.Thread.run(Thread.java:595)
        Caused by: java.io.EOFException: already closed
        at com.iplanet.im.server.io.MuxChannel.read(MuxChannel.java:156)
        at org.jabberstudio.jso.io.src.ChannelStreamSource.read(ChannelStreamSource.java:228)
        at net.outer_planes.jso.ixp.IxpParser.fill(IxpParser.java:94)
        at net.outer_planes.jso.ixp.IxpParser.process(IxpParser.java:134)
        at net.outer_planes.jso.AbstractStream$Input.process(AbstractStream.java:166)
        at net.outer_planes.jso.AbstractStream.process(AbstractStream.java:1176)
        ... 5 more
        [08 Dec 2008 16:56:31,072] INFO xmppd [default-iim_server-worker 0] New client connection 1 through multiplexor: /127.0.0.1, client address: /10.31.3.22
        [08 Dec 2008 16:56:32,604] WARN xmppd [default-iim_server-worker 0] [ComponentPacketDispatcher] failed to validate handshake for az2mailreader.httpbind.domain.com 0b73f649edd8da26a7c171d6764ebbba171d1831 instead of 115e92a449a40884a73781331f7e66935114f46a
        [08 Dec 2008 16:56:32,605] INFO xmppd [default-iim_server-worker 0] Closing client for channel : 1,az2mailreader.httpbind.domain.com
        [08 Dec 2008 16:56:32,606] INFO xmppd [default-iim_server-worker 0] already closed
        org.jabberstudio.jso.StreamException: already closed
        at net.outer_planes.jso.AbstractStream.process(AbstractStream.java:1179)
        at com.iplanet.im.server.ConnectedStreamEndPoint.process(ConnectedStreamEndPoint.java:359)
        at com.iplanet.im.server.ConnectedStreamEndPoint.dataAvailable(ConnectedStreamEndPoint.java:312)
        at com.iplanet.im.server.io.MuxChannel$MuxReadRunnable.run(MuxChannel.java:340)
        at org.netbeans.lib.collab.util.Worker.run(Worker.java:244)
        at java.lang.Thread.run(Thread.java:595)
        Caused by: java.io.EOFException: already closed
        at com.iplanet.im.server.io.MuxChannel.read(MuxChannel.java:156)
        at org.jabberstudio.jso.io.src.ChannelStreamSource.read(ChannelStreamSource.java:228)
        at net.outer_planes.jso.ixp.IxpParser.fill(IxpParser.java:94)
        at net.outer_planes.jso.ixp.IxpParser.process(IxpParser.java:134)
        at net.outer_planes.jso.AbstractStream$Input.process(AbstractStream.java:166)
        at net.outer_planes.jso.AbstractStream.process(AbstractStream.java:1176)
        ... 5 more
        [08 Dec 2008 16:56:39,150] INFO xmppd [mux_tickle_timer] sent CMD_PING
        [08 Dec 2008 16:56:39,152] INFO xmppd [default-iim_server-worker 1] recieved CMD_PING response
        [08 Dec 2008 16:56:43,612] INFO xmppd [default-iim_server-worker 0] recieved CMD_PING request
        [08 Dec 2008 16:56:43,612] INFO xmppd [default-iim_server-worker 0] sent CMD_PING ack
        [08 Dec 2008 16:57:10,632] INFO xmppd [default-iim_server-worker 3] New client connection 2 through multiplexor: /127.0.0.1, client address: /10.31.3.22
        [08 Dec 2008 16:57:12,164] WARN xmppd [default-iim_server-worker 1] [ComponentPacketDispatcher] failed to validate handshake for az2mailreader.httpbind.domain.com 43a985d040e4ccf55b38108c1f0c7317ba4eea06 instead of 5e51dd475ecf7ddd967730a00c5ace2a0512541b
        [08 Dec 2008 16:57:12,165] INFO xmppd [default-iim_server-worker 1] Closing client for channel : 2,az2mailreader.httpbind.domain.com
        [08 Dec 2008 16:57:12,166] INFO xmppd [default-iim_server-worker 1] already closed
        org.jabberstudio.jso.StreamException: already closed
        at net.outer_planes.jso.AbstractStream.process(AbstractStream.java:1179)
        at com.iplanet.im.server.ConnectedStreamEndPoint.process(ConnectedStreamEndPoint.java:359)
        at com.iplanet.im.server.ConnectedStreamEndPoint.dataAvailable(ConnectedStreamEndPoint.java:312)
        at com.iplanet.im.server.io.MuxChannel$MuxReadRunnable.run(MuxChannel.java:340)
        at org.netbeans.lib.collab.util.Worker.run(Worker.java:244)
        at java.lang.Thread.run(Thread.java:595)
        Caused by: java.io.EOFException: already closed
        at com.iplanet.im.server.io.MuxChannel.read(MuxChannel.java:156)
        at org.jabberstudio.jso.io.src.ChannelStreamSource.read(ChannelStreamSource.java:228)
        at net.outer_planes.jso.ixp.IxpParser.fill(IxpParser.java:94)
        at net.outer_planes.jso.ixp.IxpParser.process(IxpParser.java:134)
        at net.outer_planes.jso.AbstractStream$Input.process(AbstractStream.java:166)
        at net.outer_planes.jso.AbstractStream.process(AbstractStream.java:1176)

        ---Snippet of httpbind.log----

        [08 Dec 2008 16:53:22,561] ERROR httpbind [Thread-28] Error opening stream to se rver: az4chat.domain.com : 5222
        [08 Dec 2008 16:53:22,561] INFO httpbind [Thread-28] Component specified is not known : az2mailreader.httpbind.domain.com
        org.jabberstudio.jso.StreamException: Component specified is not known : az2mail reader.httpbind.domain.com
        at net.outer_planes.jso.AbstractStream.firePacketTransferredEvent(Abstra ctStream.java:697)
        at net.outer_planes.jso.AbstractStream$Input$1.addExtendedData(AbstractS tream.java:116)
        at net.outer_planes.jso.AbstractStream$Input.process(AbstractStream.java :204)
        at net.outer_planes.jso.AbstractStream.process(AbstractStream.java:1176)
        at net.outer_planes.jso.AbstractStream.openInbound(AbstractStream.java:9 50)
        at net.outer_planes.jso.AbstractStream.open(AbstractStream.java:890)
        at com.sun.im.gateway.http.ComponentSession.createStream(ComponentSessio n.java:558)
        at com.sun.im.gateway.http.ComponentSession.connectAndAuthenticate(Compo nentSession.java:307)
        at com.sun.im.gateway.http.ComponentSession$ConnectRunnable.run(Componen tSession.java:714)
        at java.lang.Thread.run(Thread.java:595)
        [08 Dec 2008 16:53:36,581] ERROR httpbind [Thread-28] Error opening stream to se rver: az4chat.domain.com : 5222
        [08 Dec 2008 16:53:36,581] INFO httpbind [Thread-28] Component specified is not known : az2mailreader.httpbind.domain.com
        org.jabberstudio.jso.StreamException: Component specified is not known : az2mail reader.httpbind.domain.com
        at net.outer_planes.jso.AbstractStream.firePacketTransferredEvent(Abstra ctStream.java:697)
        at net.outer_planes.jso.AbstractStream$Input$1.addExtendedData(AbstractS tream.java:116)
        at net.outer_planes.jso.AbstractStream$Input.process(AbstractStream.java :204)
        at net.outer_planes.jso.AbstractStream.process(AbstractStream.java:1176)
        at net.outer_planes.jso.AbstractStream.openInbound(AbstractStream.java:9 50)
        at net.outer_planes.jso.AbstractStream.open(AbstractStream.java:890)
        at com.sun.im.gateway.http.ComponentSession.createStream(ComponentSessio n.java:558)
        at com.sun.im.gateway.http.ComponentSession.connectAndAuthenticate(Compo nentSession.java:307)
        at com.sun.im.gateway.http.ComponentSession$ConnectRunnable.run(Componen tSession.java:714)
        at java.lang.Thread.run(Thread.java:595)
        [08 Dec 2008 16:53:50,623] ERROR httpbind [Thread-28] Error opening stream to se rver: az4chat.domain.com : 5222
        [08 Dec 2008 16:53:50,623] INFO httpbind [Thread-28] Component specified is not known : az2mailreader.httpbind.domain.com
        org.jabberstudio.jso.StreamException: Component specified is not known : az2mail reader.httpbind.domain.com
        at net.outer_planes.jso.AbstractStream.firePacketTransferredEvent(Abstra ctStream.java:697)
        at net.outer_planes.jso.AbstractStream$Input$1.addExtendedData(AbstractS tream.java:116)
        at net.outer_planes.jso.AbstractStream$Input.process(AbstractStream.java :204)
        at net.outer_planes.jso.AbstractStream.process(AbstractStream.java:1176)
        at org.netbeans.lib.collab.xmpp.FeatureIdentifier.process(FeatureIdentif ier.java:122)
        at com.sun.im.gateway.http.ComponentSession.createStream(ComponentSessio n.java:559)
        at com.sun.im.gateway.http.ComponentSession.connectAndAuthenticate(Compo nentSession.java:307)
        at com.sun.im.gateway.http.ComponentSession$ConnectRunnable.run(Componen tSession.java:714)
        at java.lang.Thread.run(Thread.java:595)
        [08 Dec 2008 16:54:04,641] ERROR httpbind [Thread-28] Error opening stream to se rver: az4chat.domain.com : 5222
        [08 Dec 2008 16:54:04,641] INFO httpbind [Thread-28] Component specified is not known : az2mailreader.httpbind.domain.com
        org.jabberstudio.jso.StreamException: Component specified is not known : az2mail reader.httpbind.domain.com
        at net.outer_planes.jso.AbstractStream.firePacketTransferredEvent(Abstra ctStream.java:697)
        at net.outer_planes.jso.AbstractStream$Input$1.addExtendedData(AbstractS tream.java:116)
        at net.outer_planes.jso.AbstractStream$Input.process(AbstractStream.java :204)
        at net.outer_planes.jso.AbstractStream.process(AbstractStream.java:1176)
        at net.outer_planes.jso.AbstractStream.openInbound(AbstractStream.java:9 50)
        at net.outer_planes.jso.AbstractStream.open(AbstractStream.java:890)
        at com.sun.im.gateway.http.ComponentSession.createStream(ComponentSessio n.java:558)
        at com.sun.im.gateway.http.ComponentSession.connectAndAuthenticate(Compo nentSession.java:307)
        at com.sun.im.gateway.http.ComponentSession$ConnectRunnable.run(Componen tSession.java:714)
        at java.lang.Thread.run(Thread.java:595)
        [08 Dec 2008 16:54:24,660] ERROR httpbind [Thread-28] Error opening stream to se rver: az4chat.domain.com : 5222
        [08 Dec 2008 16:54:24,661] INFO httpbind [Thread-28] Component specified is not known : az2mailreader.httpbind.domain.com
        org.jabberstudio.jso.StreamException: Component specified is not known : az2mail reader.httpbind.domain.com
        at net.outer_planes.jso.AbstractStream.firePacketTransferredEvent(Abstra ctStream.java:697)
        at net.outer_planes.jso.AbstractStream$Input$1.addExtendedData(AbstractS tream.java:116)
        at net.outer_planes.jso.AbstractStream$Input.process(AbstractStream.java :204)
        at net.outer_planes.jso.AbstractStream.process(AbstractStream.java:1176)
        at net.outer_planes.jso.AbstractStream.openInbound(AbstractStream.java:9 50)
        at net.outer_planes.jso.AbstractStream.open(AbstractStream.java:890)
        at com.sun.im.gateway.http.ComponentSession.createStream(ComponentSessio n.java:558)
        at com.sun.im.gateway.http.ComponentSession.connectAndAuthenticate(Compo nentSession.java:307)
        at com.sun.im.gateway.http.ComponentSession$ConnectRunnable.run(Componen tSession.java:714)
        at java.lang.Thread.run(Thread.java:595)
        [08 Dec 2008 16:54:44,690] ERROR httpbind [Thread-28] Error opening stream to se rver: az4chat.domain.com : 5222
        [08 Dec 2008 16:54:44,690] INFO httpbind [Thread-28] Component specified is not known : az2mailreader.httpbind.domain.com
        org.jabberstudio.jso.StreamException: Component specified is not known : az2mail reader.httpbind.domain.com
        at net.outer_planes.jso.AbstractStream.firePacketTransferredEvent(Abstra ctStream.java:697)
        at net.outer_planes.jso.AbstractStream$Input$1.addExtendedData(AbstractS tream.java:116)
        at net.outer_planes.jso.AbstractStream$Input.process(AbstractStream.java :204)
        at net.outer_planes.jso.AbstractStream.process(AbstractStream.java:1176)
        at net.outer_planes.jso.AbstractStream.openInbound(AbstractStream.java:9 50)
        at net.outer_planes.jso.AbstractStream.open(AbstractStream.java:890)
        at com.sun.im.gateway.http.ComponentSession.createStream(ComponentSessio n.java:558)
        at com.sun.im.gateway.http.ComponentSession.connectAndAuthenticate(Compo nentSession.java:307)
        at com.sun.im.gateway.http.ComponentSession$ConnectRunnable.run(Componen tSession.java:714)
        at java.lang.Thread.run(Thread.java:595)
        [08 Dec 2008 16:55:04,732] ERROR httpbind [Thread-28] Error opening stream to se rver: az4chat.domain.com : 5222
        [08 Dec 2008 16:55:04,732] INFO httpbind [Thread-28] Component specified is not known : az2mailreader.httpbind.domain.com
        org.jabberstudio.jso.StreamException: Component specified is not known : az2mail reader.httpbind.domain.com
        at net.outer_planes.jso.AbstractStream.firePacketTransferredEvent(Abstra ctStream.java:697)
        at net.outer_planes.jso.AbstractStream$Input$1.addExtendedData(AbstractS tream.java:116)
        at net.outer_planes.jso.AbstractStream$Input.process(AbstractStream.java :204)
        at net.outer_planes.jso.AbstractStream.process(AbstractStream.java:1176)
        at org.netbeans.lib.collab.xmpp.FeatureIdentifier.process(FeatureIdentif ier.java:122)
        at com.sun.im.gateway.http.ComponentSession.createStream(ComponentSessio n.java:559)
        at com.sun.im.gateway.http.ComponentSession.connectAndAuthenticate(Compo nentSession.java:307)
        at com.sun.im.gateway.http.ComponentSession$ConnectRunnable.run(Componen tSession.java:714)
        at java.lang.Thread.run(Thread.java:595)
        [08 Dec 2008 16:55:56,713] INFO httpbind [httpSSLWorkerThread-8080-4] Creating a new session - sid 4571617911889296702 , rid : 385039520
        [08 Dec 2008 16:55:56,876] INFO httpbind [httpSSLWorkerThread-8080-3] Creating a new session - sid 2328265126693956747 , rid : 512892054
        [08 Dec 2008 16:55:56,964] INFO httpbind [httpSSLWorkerThread-8080-0] Creating a new session - sid 4286952330613394002 , rid : 291062570
        [08 Dec 2008 17:04:37,777] INFO httpbind [httpSSLWorkerThread-8080-4] Creating a new session - sid 1449562747249164065 , rid : 650653103
        [08 Dec 2008 17:04:37,957] INFO httpbind [httpSSLWorkerThread-8080-1] Creating a new session - sid 5010339779565950930 , rid : 691500077
        [08 Dec 2008 17:04:38,047] INFO httpbind [httpSSLWorkerThread-8080-2] Creating a new session - sid 5487734576412779827 , rid : 396533874
        ... 5 more

        httpbind.conf matches the syntax on iim.conf

        httpbind.conf settings:

        httpbind.config=default
        default.domains=domain.com
        #default.domains=domain.com
        #default.hosts=az2mailreader.domain.com:5222
        default.hosts=az4chat.domain.com:5222
        #default.hosts=az4chat.domain.com:5269
        default.componentjid=az2mailreader.httpbind.domain.com
        default.password=adminpass
        #log4j config filename is specified in the servlet params
        #httpbind.log4j.config=/etc/opt/SUNWiim/default/config/httpbind_log4j.conf

        1. Parameters specified to NGC, commenting these out will make the gateway act 'n
          ormally' ...
        2. without SSO/proxy auth, and NGC authorization. (Can be used to test with third
          party/other xep124 clients).

        httpbind.external.auth.commsclient.delegate=com.sun.comms.client.web.authorizati
        on.XMPPAuthorizationManager
        httpbind.external.auth.handler=com.sun.im.gateway.http.util.CommsClientExternalA
        uthHandler

        #Uncomment these options if component password is encrypted
        httpbind.component.password.cipher.delegate=com.sun.comms.client.config.auth.sun
        .PasswordUtil
        httpbind.component.password.cipher=com.sun.im.gateway.http.util.CommsClientCiphe
        r

        1. Avatar Component configuration
          #avatar.server_url=az2mailreader.domain.com:5222
          #avatar.server_url=az4chat.domain.com:5222
          avatar.server_url=az4chat.domain.com:5269
          avatar.component_jid=az2mailreader.avatar.domain.com
          avatar.component_password=adminpass
          avatar.timeout=5000
          avatar.cache_size=100
          avatar.image_threshold=4096
        2. Maximum allowed avatar upload size in bytes
          avatar.max_photo_size=100000
        3. Limit on dimension(width,height) of images being served.
          avatar.maxwidth=2000
          avatar.maxheight=2000

        Syntax of iim.conf settings:

        ! httpbind component (HTTP/XMPP Gateway)
        ! ======================================
        iim_agent.httpbind.enable = "true"
        httpbind.jid ="az2mailreader.httpbind.domain.com"
        httpbind.password = "adminpass"
        !
        !avatar component
        !
        iim_agent.avatar.enable = "true"
        avatar.jid="az2mailreader.avatar.domain.com"
        avatar.password= "adminpass"

        Port settings are to listen to 5269 instead of 5222 for multiplexor.

        Once changes have been made to the config files, I restart BOTH iim server as well as App Server 9.

        When logging into a convergence web client, I continue to see the "connecting" under the buddy list for Instant Messaging. Mail and Calendar work fine. Any information you can give to help resolve this would be great.

        1. Dec 09, 2008

          Steven_Kahn says:

          Hi slon1975, Thanks for sending in the preceding comments. However, at this poin...

          Hi slon1975,
          Thanks for sending in the preceding comments. However, at this point it looks like they concern your own software deployment more than the information on the page. In the future, please use the comments feature on this page to address specific issues with this document. For questions concerning problems with your deployment, please use either the Sun Messaging Server forum (http://forums.sun.com/forum.jspa?forumID=708) or open a support call with Sun.

          Thanks again,
          Steven

          1. Dec 09, 2008

            slon1975 says:

            Steven, This is specific to this page. I am attempting to connect Sun Convergen...

            Steven,

            This is specific to this page. I am attempting to connect Sun Convergence with Sun IM. This is NOT Sun Messaging related. The user earlier requested the log files I sent over to try and help resolve this issue. It is a bug with the Sun Convergence or Sun IM software. I will contact Sun Support, but was hoping to resolve this on the forum.

  7. Dec 09, 2008

    Steven_Kahn says:

    Hi slon1975, It looks like there's an IM forum you can try, too: http://forums.s...

    Hi slon1975,
    It looks like there's an IM forum you can try, too: http://forums.sun.com/forum.jspa?forumID=732

    --Steven

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact