Sequence Issues

• 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 used with Instant Messaging include Messaging Server, Calendar Server, and Portal Server (with Access Manager).

To Develop a Sequence for Instant Messaging

The following high-level tasks are required:

Steps

1. Running the Java ES installer

2. At component selection, choosing Instant Messaging

3. Resolving incompatibilities

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

4. Verifying installation directories

5. Selecting the Configure Later option

   Instant Messaging cannot be configured during installation.

6. Running the installation

7. Viewing the Installation Summary and Log

8. Completing post-install configuration

   Configuring Instant Messaging After a Configure Later Installation

9. Starting Instant Messaging (after starting any other components that Instant Messaging might depend on)

   Starting and Stopping Instant Messaging Server and Multiplexor

   The following table contains additional Instant Messaging information.

   Task	Relevant Information
   Postinstallation configuration	Configuring Instant Messaging After a Configure Later Installation
   Starting and stopping	Starting and Stopping Instant Messaging Server and Multiplexor
   Uninstalling	Instant Messaging Uninstallation Behavior
   Troubleshooting	Instant Messaging Troubleshooting Tips
   Upgrading	Sun Java Enterprise System 2005Q4 Upgrade Guide
   Deployment scenarios	Sun Java System Communications Deployment Planning Guide