Sun Java System Instant Messaging 7.2 Administration Guide

ProcedureTo Configure Instant Messaging After Installation

  1. Change to the directory in which you installed Instant Messaging.

    By default, this directory is /opt/SUNWiim on Solaris, and /opt/sun/im on Linux.

  2. Run the configure utility in one of the following ways:

    Graphical user interface:



    configure --nodisplay

    From a state file:

    configure --nodisplay --noconsole --state statefile

    where statefile is the path to the state file you want to use. If you are configuring using a state file, you will not be prompted for configuration information. Instead, the values from the state file are used to configure the software. See Performing a Silent Instant Messaging Configuration for information on generating a state file.

    If you are configuring using the graphical user interface or the command line, a series of prompts appears, requesting information that will set up the initial configuration for Instant Messaging. The prompts that appear vary depending on the components you installed. Fill in the requested information using the values from your Instant Messaging checklist. See Completing the Configuration Checklist.

  3. If you install the Sun Java System Access Manager on a different host from the Instant Messaging server, you need to manually copy the imServices files from the Instant Messaging server host to the Access Manager host after you run the configure utility.

    To do this:

    1. Locate the imService_*.properties files on the Instant Messaging server host.

      By default, these files are located under /opt/SUNWiim/lib/ on Solaris and /opt/sun/im/lib/ on Linux.

    2. Copy the files to the locale directory on the Access Manager host.

      By default this directory is /opt/SUNWam/locale on Solaris and /opt/sun/identity/locale on Linux.

  4. If you are using Access Manager to manage Instant Messaging policies, run the imadmin assign_services command.

    imadmin assign_services

    You will be prompted for the Base DN of the organization under which user entries are stored. This command adds Instant Messaging and presence services to existing users under the organization you specify.

  5. Restart Sun Java System Application Server.

    If Instant Messaging will use Access Manager policies in a Sun Java System Application Server deployment, you need to restart the Application Server when you finish configuring Instant Messaging. If you do not restart the Application Server, Instant Messaging services will not appear in the Access Manager console (amconsole).

  6. If you intend to use the XMPP/HTTP Gateway, you may need to modify the location of the default log file for the XMPP/HTTP gateway in httpbind_log4j.conf if:

    • On Solaris, you chose to use a location for logs other than the default

    • On Linux, regardless of the path you chose

    To do this:

    1. Open the httpbind_log4j.conf file.

      This file is stored at the location you specified in httpbind.conf file as the value for the httpbind.log4j.config parameter. By default the file is stored in the following directory under the default Instant Messaging instance:

    2. Set the value of the log4.appender.appender_ID.file parameter to the location where log files are stored.

      By default, on Linux, this value is /var/opt/sun/im/default/log. If you chose another location for log files when you ran configure, enter that path as the value for the parameter.

  7. If necessary, configure Access Manager–based services for SSO and policy management.

    See Adding Instant Messaging and Presence Services to a Sub-organization in Access Manager for Single Sign-On and Policy Management Support for information.

  8. Configure the web container and client systems to support Instant Messaging.

    For instructions, see Chapter 2, Setting up and Launching Instant Messenger.