Communication and Collaboration Services Example

This example installs most of the Java ES components to implement communication and collaboration services across four hosts.

If you are using any of these components with Sun Cluster software, you must perform a precise series of tasks before installing any Java ES components. Refer to Sun Cluster Software Example

Requirements and Sequence Issues

Directory Server is required for all the communications components, but not necessarily a local copy. A local copy of Administration Server is required by Messaging Server. Access Manager or the Access Manager SDK is required, but Access Manager can be remote. In this example, Web Server fulfills the Access Manager requirement for a web container. Although Calendar Server and Messaging Server do not require a local web container, Communications Express does. Communications Express can use a remote copy of Calendar Server, but Messaging Server must be local.

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.

To implement single sign-on, Instant Messaging requires Access Manager and a local or remote web container. Portal Server Secure Remote Access requires Access Manager and a local web container. Portal Server Secure Remote Access also requires Portal Server, but not necessarily a local copy. Portal Server Secure Remote Access must be installed in same location as Portal Server. Access Manager andPortal Server cannot use different web containers.

For large deployments, you might deploy each component on a separate server, in approximately the same order shown in this example. For small deployments, components are installed in separate installation sessions on fewer servers.

To use this sequence example, also refer to known issue 6284663 in the Sun Java Enterprise System 2005Q4 Release Notes.

In this example, the following installation sessions are used:

• Session 1, Host A: Installing Access Manager and Directory Server

• Session 2, Host B: Installing Portal Server and Web Server (using remote Directory Server and Access Manager on Host A)

• Session 3, Host C: Installing Calendar Server (using remote Directory Server and Access Manager on Host A)

• Session 4, Host D: Installing Communications Express, Messaging Server, Access Manager SDK, and Web Server (using remote Directory Server and Access Manager on Host A, and remote Calendar Server on Host C)

• Session 5, Host D: Installing Instant Messaging (using remote Directory Server and Access Manager on Host A) after the other components are installed and functioning

• Session 6, Host D: Installing Portal Server Secure Remote Access (using remote Directory Server and Access Manager on Host A)

  By dividing the installation into a number of sessions, you are able to verify the components in each session before proceeding to the next session.

To Develop a Sequence for Host A

The following high-level tasks are required:

Step

Installing and starting Access Manager and Directory Server

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

Identity Management Example

To Develop a Sequence for Host B

The following high-level tasks are required:

Step

Installing and starting Portal Server and Web Server, specifying the remote Access Manager and Directory Server that are installed and running on Host A

A web container and the Access Manager SDK must be local to Portal Server.

• Access Manager and Portal Server Example

• Portal Server Using a Remote Access Manager Example

To Develop a Sequence for Host C

The following high-level tasks are required:

Step

Installing and starting Calendar Server, specifying the remote Access Manager and Directory Server that are installed on Host A

Access Manager SDK must be local to Messaging Server and Calendar Server.

Install only Calendar Server using the Calendar Server and Messaging Server Example.

To Develop a Sequence for Host D (First Session)

The following high-level tasks are required:

Steps

1. Installing Communications Express, Messaging Server, Access Manager SDK, and Web Server using the Configure Later option

2. Performing Web Server post-installation configuration

   To Configure Web Server After a Configure Later Installation

3. Performing AM SDK configuration to work with the local Web Server and the remote Access Manager

   Access Manager SDK With Container Configuration Example

4. Performing Administration Server post-installation configuration

   To Configure Administration Server After a Configure Later Installation

5. Performing Messaging Server post-installation configuration

   Messaging Server Postinstallation Configuration

6. Starting Messaging Server

   To Start Messaging Server

7. Performing Communications Express post-installation configuration

   During this configuration, provide information for Access Manager on Host A, Calendar Server on Host C, and Messaging Server on Host D.

   To Configure Communications Express After a Configure Later Installation

8. Restarting Web Server on Host D

   Starting and Stopping Web Server

To Develop a Sequence for Host D (Second Session)

The following high-level tasks are required:

Steps

1. Installing Instant Messaging

   Instant Messaging Only Example

2. Performing Instant Messaging post-installation configuration

   Instant Messaging Postinstallation Configuration

To Develop a Sequence for Host D Third Session)

The following high-level tasks are required:

Steps

1. Installing Portal Server Secure Remote Access, specifying the remote Access Manager and Directory Server that are installed on Host A

   As a Portal Server Secure Remote Access requirement, Portal Server is also installed.

   Portal Server Using a Remote Access Manager Example

2. Establishing an initial user and setting up single sign-on