Instant Messaging

Examine your deployment architecture for computer systems with instances of Instant Messaging.

Instant Messaging provides instant messaging services to end users.

• If instant messaging services are provided as part of a solution that uses Java ES messaging and calendar services, Instant Messaging looks up user data in the same LDAP organization as Messaging Server and Calendar Server. In this type of solution, Instant Messaging shares all of the dependencies for Messaging Server and Calendar Server. These dependencies are met when Messaging Server and Calendar Server are installed and configured. In this type of solution, it is logical to install Instant Messaging after Messaging Server and Calendar Server.

• If instant messaging services are provided without messaging and calendar services, Instant Messaging has a solution-level dependency on a source of user data. This dependency is met with Directory Server, or Directory Server and Access Manager.

TheInstant Messaging client resources subcomponent has a local dependency on a web container. Web Server or Application Server can be used. If your solution distributes the Instant Messaging sub components, the web container must be installed on the same computer as the client resources.

If your solution uses Access Manager single sign-on, Instant Messaging also has a dependency on Access Manager. This dependency can be satisfied with a local Access Manageror Access Manager SDK. Typically, in a distributed solution, the deployment architecture will specify a local copy of the Access Manager SDK, which supports interaction with a remote instances of Access Manager.

Basic Installation Procedures for Instant Messaging

The basic steps for installing and configuring Instant Messaging are the following:

1. Use the Java ES installer to install Instant Messaging on all computers systems specified in your deployment architecture.

   1. When you install Instant Messaging you satisfy the web container dependency by installing the web container in which Instant Messaging runs or by specifying a wed container already installed on the computer.

   2. If the solution uses Access Manager single sign-on, you satisfy the Access Manager dependency by installing either a copy of the Access Manager SDK or a local copy of Access Manager.

2. Run the Instant Messaging configuration wizard. When you configure Instant Messaging you must specify the repository for user and group data (typically a Directory Server instance, specified with a URL).

3. Start and verify all instances of Instant Messaging.

4. If your solution uses load balancing for the Instant Messaging instances, verify that the load balancer is working properly.

Choosing Configuration Values for Instant Messaging

For each Instant Messaging instance in your solution, you must input values that configure the instance to interoperate with the other components in the solution. Use Table 3–13 to help you choose configuration values. For detailed information on the input values, see Chapter 1, “Configuring Instant Messaging after Installation,” in Sun Java System Instant Messaging 7 2005Q1 Administration Guide.

Table 3–13 Key Configuration Values for Instant Messaging

Input Field	Choosing a Value for Your Solution
Sun Java System Instant Messaging Server, Sun Java System Instant Messaging Resources, Sun Java System Access Manager Instant Messaging Service	Select the subcomponents specified in the deployment architecture. For more information, see Analyzing a Deployment Architecture and Distributed Subcomponents.
Runtime User ID, Runtime Group, HTTP Port, Document Root Directory	Use these fields to specify the Web Server instance in which Instant Messaging client resource runs.
Are you planning to leverage an Access Managerdeployment for SSO? and Are you planning to leverage an Access Manager deployment for Policy?	Use these fields to specify how Instant Messaging interacts with Access Manager.
Domain Name, IM Server Port, Multiplexor Port, Disable Server, Remote IM Host Name	Domain name is the mail domain that your solution is using. It was established when Messaging Server was configured. For more information, see Table 3–9.
LDAP Host Name, LDAP Port Number, Base DN, Bind DN, Bind Password	Specify the Directory Server instance used for user and group data. Bind DN and Bind Password are the directory manager account and password. Base DN is the LDAP organization for Instant Messaging user data. If the solution also includes Messaging Server, Base DN is the email domain LDAP organization created by Messaging Server configuration. For more information see Table 3–9. If your solution uses load-balanced Directory Server instances, type the logical URL for the load-balanced directory service.
SMTP Server	Specify the computer running Messaging Server. If your solution uses load-balanced or clustered Messaging Server instances, use the logical URL for the load-balanced messaging service.
Instant Messenger Resources Codebase	Specify the location from which users will download Instant Messenger client resources.
Assign IM Service to Existing Users

Adding Procedures for Instant Messaging to Your Installation Plan

To add installation and configuration instructions for Instant Messaging, do the following:

1. If the Instant Messaging instances are load balanced, add an instruction to your installation plan to confirm that the load balancer is functioning before any Java ES software is installed.

2. Next, in your plan, list all of the computers with Instant Messaging instances.

   1. The Instant Messaging client resources subcomponent has a local dependency on a web container. Each computer that runs this subcomponent must also run an instance of the specified web container. Your deployment architecture should indicate which web container your solution is using.

   2. For each computer, add an instruction to run the Java ES installer and select Instant Messaging. Add an instruction to select either Web Server or Application Server as the web container. Add an instruction to select either Access Manager SDK or Access Manager.

   3. If the computers that run Instant Messaging are already listed in your plan (if the plan already has instructions for installing another component on the same computer) simply add an instruction to select Instant Messaging. You can install Instant Messaging at the same time as the other components, and deploy it to the same web container, but your plan must put the instructions for configuring, starting, and verifying any Directory Server, Access Manager, Messaging Server, or Calendar Server instances ahead of the instructions for configuring or starting the Instant Messaging instances.

3. Add an instruction to run the Instant Messaging configuration utility. Underneath this instruction, list the key values for configuring the instance. Use Table 3–13 to help you select configuration values.

4. Underneath each Web Server or Application Server instances, list the key values for configuring the instance. For information on selecting configuration values for these components, see Web Server or Application Server. If your plan already installs Web Server or Application Server on the computer, you do not need to repeat this step. You can deploy Communications Express to the same web container instance when you run the Instant Messaging configuration utility.

5. For each computer, add an instruction to start and verify the Instant Messaging instance.

6. If the Instant Messaging instances are load balanced, add an instruction to verify operation of the load balancer.