Communications Suite Example

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

Requirements and Sequence Issues

Directory Server is required for all the communications product components, but not necessarily a local copy. 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 remote copies of Calendar Server and Messaging Server.

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 must be installed in the same location as Portal Server. Access Manager and Portal Server cannot use different web containers.

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

In this example, the following installation sessions are used:

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

• 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 product 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 product components in each session before proceeding to the next session.

To Develop a Sequence for Host A

The following high-level tasks are required:

1. Checking the installation sequence guidelines

   Check to see what guidelines apply to this example and make adjustments as needed.

2. Checking the installation prerequisites

   Check to see what tasks you might need to perform for this installation before starting.

3. Installing Access Manager, Directory Server, and Directory Preparation Tool

   Identity Management Example

4. Running Directory Preparation Tool

5. Starting Access Manager and Directory Server

To Develop a Sequence for Host B

The following high-level tasks are required:

1. Checking the installation sequence guidelines

   Check to see what guidelines apply to this example and make adjustments as needed.

2. Checking the installation prerequisites

   Check to see what tasks you might need to perform for this installation before starting.

3. 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.

To Develop a Sequence for Host C

The following high-level tasks are required:

1. Checking the installation sequence guidelines

   Check to see what guidelines apply to this example and make adjustments as needed.

2. Checking the installation prerequisites

   Check to see what tasks you might need to perform for this installation before starting.

3. 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:

1. Checking the installation sequence guidelines

   Check to see what guidelines apply to this example and make adjustments as needed.

2. Checking the installation prerequisites

   Check to see what tasks you might need to perform for this installation before starting.

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

4. Performing Web Server post-installation configuration

   To Configure Web Server After a Configure Later Installation

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

   Access Manager SDK With Container Configuration Example

6. Performing Messaging Server post-installation configuration

   Messaging Server Postinstallation Configuration

7. Starting Messaging Server

   To Start Messaging Server

8. 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

9. 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:

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:

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.

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