Instant Messaging and Access Manager Example

This example installs Instant Messaging with Access Manager, using a remote Directory Server, and Web Server as the web container.

Requirements and Sequence Issues

For the Instant Messaging Core subcomponent, Access Manager is required, but not necessarily a local copy. For the Instant Messaging Resources subcomponent, the Access Manager SDK must be local to Instant Messaging. Access Manager requires a web container, which can be remote. If you use Access Manager, Directory Server is required, but not necessarily a local copy. If you are using Access Manager with Instant Messaging, you must also use Access Manager SDK.

You must use Access Manager Legacy (6.x) installation type if you are installing Access Manager with Portal Server, Messaging Server, Calendar Server, Delegated Administrator, or Instant Messaging. Access Manager Realm (7.x) installation type can only be used if you are not installing any of these components.

• The installer does not automatically select components that Instant Messaging depends on. You are responsible for selecting these components.

• If you are deploying other components with Instant Messaging, the other components must be configured before configuring Instant Messaging.

  Java ES components that are commonly deployed with Instant Messaging include Messaging Server, Calendar Server, and Portal Server (with Access Manager).

To Develop a Sequence for Host A

The following high-level tasks are required:

Step

Installing and starting Directory Server

Because Administration Server provides a graphical interface for Directory Server, you might also want to select Administration Server.

Directory Server Only Example

To Develop a Sequence for Host B

The following high-level tasks are required:

Steps

1. Running the Java ES installer

2. At component selection, choosing Instant Messaging and Web Server

3. Deselecting Directory Server and specifying the remote copy when prompted

4. Resolving incompatibilities

   The installer verifies software on your host and provides guidance if incompatibilities are identified.

5. Verifying installation directories

6. Selecting the Configure Now or Configure Later option

   Instant Messaging cannot be configured during installation.

   1. For the Configure Now option, configuration pages are displayed for Web Server.

      Gather your configuration information from the tables in Chapter 1, Configuration Information, in Sun Java Enterprise System 2005Q4 Installation Reference

   2. For the Configure Later option, configuration pages are not displayed.

7. Running the installation

8. Viewing the Installation Summary and Log

9. Completing post-install configuration

   • Web Server Postinstallation Configuration

   • Configuring Instant Messaging After a Configure Later Installation (Optional) For remote components: During Instant Messaging configuration, specify any remote locations for Directory Server, Access Manager, and Web Server.

10. Starting the components in this order:

    1. Starting and Stopping Web Server

    2. Starting and Stopping Instant Messaging Server and Multiplexor