This topic provides information you can use to plan your Lotus® Expeditor Server deployment in a clustered environment.
- Before you begin
- Guidelines for implementing cluster environments
Before you begin
Review Planning considerations
for the Lotus Expeditor Server environment before reviewing this section for planning considerations specific to clusters.
In WebSphere® Application Server, a cluster is composed of multiple identical copies of an application server. A cluster member is a single application server in the cluster. Lotus Expeditor Server is installed as a collection of enterprise application services within the WebSphere Application Server infrastructure. The exception to this is WebSphere MQ Everyplace®. The services provided by MQ Everyplace do not run as an enterprise application service. All of the clustering features available within the WebSphere Application Server infrastructure are also available and apply to Lotus Expeditor Server. Consequently, an Lotus Expeditor Server cluster is simply a collection of multiple Lotus Expeditor Servers that are identically configured.
When planning for Lotus Expeditor Server clusters, you must also take into account any cluster planning required for the WebSphere Application Server nodes. For further information, see product planning documentation for the WebSphere Application Server Network Deployment version supported by the Lotus Expeditor Server version that you are using.
Guidelines for implementing cluster environments
Cluster environments should be implemented according to the following guidelines:
- In production and clustered environments, it is recommended to configure an external Web server. See Adding or updating a Web server configuration for more information.
- Ensure that WebSphere Application Server is installed properly on each node. Make sure that all appropriate interim fixes are applied to each node. The Deployment Manager (from WebSphere Application Server Network Deployment) should always be at the same fix level or higher than any managed WebSphere Application Server node.
- Ensure that the Lotus Expeditor Server is installed properly with databases on a remote database server.
- The Deployment Manager node must be installed separately before the cells and clusters can be configured. See the WebSphere Application Server Network Deployment Information Center for details.
- After the primary Lotus Expeditor Server is installed and configured in a managed environment, use the Lotus Expeditor Server configuration wizard Advanced Clustering Services to create the initial cluster.
- Install additional secondary Lotus Expeditor Server nodes into the cluster. These nodes must already be members of the Deployment Manager cell to which the primary Lotus Expeditor Server belongs.
The following limitations apply when implementing a Lotus Expeditor Server cluster:
- There can only be one primary Lotus Expeditor Server installation per cell. Additional nodes must be installed using the secondary node install process.
- Lotus Expeditor Server services cannot be configured for vertical clustering.
- Lotus Expeditor Server cannot be clustered using database server that is local to the Lotus Expeditor Server.
- Uninstallation of the primary node, when there are secondary nodes in the cluster, is not recommended. You must uninstall the secondary nodes before uninstalling the primary node.
Parent topic: Planning for deployment: XPD622