This example installs Instant Messaging by itself. It is not uncommon for Instant Messaging to be installed in a separate installation session after other components have been installed and configured.
If you are using single sign-on or Access Manager managed policies, Access Manager is required. For guidelines, refer to Instant Messaging and Access Manager Example
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).
The following high-level tasks are required:
Running the Java ES installer
At component selection, choosing Instant Messaging
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
Verifying installation directories
Selecting the Configure Later option
Instant Messaging cannot be configured during installation.
Running the installation
Viewing the Installation Summary and Log
Completing post-install configuration
Configuring Instant Messaging After a Configure Later Installation
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 | |
Troubleshooting | |
Upgrading | |
Deployment scenarios |
Sun Java System Communications Deployment Planning Guide |