test

Sun Java System Instant Messaging 7 2006Q1 Administration Guide

Configuring Instant Messaging After Installing or Upgrading

The Instant Messaging software is not configured by the installer. Instead, you need to run the configure utility after you install the software.

If you are using the BEA web container, you need to create a PASSFILE before you can configure Instant Messaging. If you are not using the BEA Web Container, skip to To Configure Instant Messaging After Installation.

ProcedureTo Create the PASSFILE for the BEA Web Container

Steps

  1. Create a file named installation directory/SUNWiim/lib/PASSFILE.

  2. Add the following lines to the file you created:


    DS_DIRMGR_DN=Directory Manager Bind DN 
DS_DIRMGR_PASSWORD=Directory Manager Bind Password
DS_HOST=LDAP Host Name
DS_PORT=LDAP Port Number
DS_BASE_DN=Base DN

  3. Fill in the values for each of the variables.

ProcedureTo Configure Instant Messaging After Installation

Steps

  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

    Command-line: 


    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 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 JavaTM 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 theAccess 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 JavaTM System Application Server.

    If Instant Messaging will use Access Manager policies in a Sun JavaTM 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. Configure the web container and client systems to support Instant Messaging.

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