Messaging Server Installation

The default factory is different in Java ES 2004Q2 and Java ES 2005Q1 (6200472)

Existing deployments who do not wish to upgrade the server will have to explicitly set the property of collaboration session factory object to use the Legacy protocol implementation. In the API place the following constructor to create a ColloaborationSessionFactor: CollaborationSessionFactory factory = newCollaborationSessionFactory(“com.iplanet.im.client.api.ilMSessionFactory”);

Problem installing Messaging Server and Directory Server on different machines (no specific ID)

Solution

To install Messaging Server and Directory Server on different machines

Steps

1. Install and configure Directory Server and Administration Server on the directory system.

2. Install Administration Server and Messaging Server on the Messaging system. Administration Server can be configured during the installation, but Messaging Server cannot.

3. Configure Messaging Server.

Using Messaging Server (and Directory Server) with Schema 2 support (4916028)

In order to use Messaging Server with Schema 2 support, you must install Access Manager and Directory Server.

Solution Currently, the only way to get Schema 2 support into Directory Server is to install Access Manager.

Access Manager also requires Web Server (or Application Server) to act as its web container. If Access Manager is not installed with Directory Server, then only Schema 1 is used by Messaging Server. Because there are no user selectable options for Schema 1 or 2 during the Java Enterprise System installation, Access Manager must be installed to update Directory Server.