This example installs Communications Express for messaging services in a 2-host Schema 2 environment. A remote copy of Directory Server is used.
On Linux: To use this sequence example, also refer to known issue 6283991 in the Sun Java Enterprise System 2005Q4 Release Notes.
Communications Express requires either Access Manager or the Access Manager SDK for Schema 2. A local copy of Access Manager SDK is always required, but you can use a remote copy of Access Manager. Directory Server is required for Access Manager and Communications Express, but Directory Server does not need to be on the local host. Communications Express requires a local web container which can be either Application Server or Web Server.
To use messaging services, Communications Express requires a local copy of Messaging Server, which requires a local copy of Administration Server. To use calendar services, Communications Express requires Calendar Server, but Calendar Server does not need to be on the local host. This example uses messaging services.
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.
If you are using Messaging Server or Web Server with Sun Cluster software, you must perform a precise series of tasks before installing any components. Refer to Sun Cluster Software Example to see Sun Cluster guidelines.
The remote Directory Server must be installed and running before installing any components that depend on it.
The following high-level tasks are required:
Installing and starting Directory Server
Because Administration Server provides a graphical interface for Directory Server, you might also want to select Administration Server.
The following high-level tasks are required:
Running the Java ES installer
At component selection, choosing Communications Express, Access Manager, Messaging Server, and Web Server
Administration Server, Directory Server, and the Directory Preparation Tool are automatically selected.
Deselecting Directory Server
When you are prompted to choose a local or remote Directory Server, choose remote (the Directory Server that is already installed and running on Host A).
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
Selecting the Configure Now option
Communications Express cannot be configured during installation, and will require postinstallation configuration.
Configuration pages are displayed for those components that can be configured during installation.
Reviewing the configuration pages
Running the installation
Viewing the Installation Summary and Log
Completing post-install configuration:
Starting the components
Starting and Stopping Web Server (Access Manager automatically starts)
Using the following URL to access the default Communications Express login page:
http://webcontainer-host:webcontainer-port/ uri-path-CommsExpress |
Using the following URL to access the default Access Manager Login page:
http://web-container-host:web-container-port /amserver/UI/Login |