Guidelines for setting up a cluster

 

+

Search Tips   |   Advanced Search

Before you begin

A cluster is composed of multiple identical copies of an appserver. A cluster member is a single appserver in the cluster.

All of the clustering features available within the WAS infrastructure are also available and apply to WebSphere Portal.

A WebSphere Portal cluster is simply a collection of multiple WebSphere Portal servers that are identically configured.

Guidelines for implementing cluster environments

The instructions provided here for installing a WebSphere Portal follow the approach recommended by WAS, which involves using the Plug-ins installation wizard to install the binary plug-in module after the cell has been set up.

• Windows: Select a Web server topology diagram and roadmap
• UNIX: Select a Web server topology diagram and roadmap
• i5/OS: Select a Web server topology diagram and roadmap

The deployment manager node must be installed separately before the cells and clusters can be configured.

WAS provides database session persistence and memory-to-memory replication as techniques for HTTP session failover in a clustered environment. Review the following information to determine whether you want to use one of these techniques in the cluster:

• Windows: Task overview: Managing HTTP sessions
• UNIX: Task overview: Managing HTTP sessions
• i5/OS: Task overview: Managing HTTP sessions

You can create an WebSphere Virtual Enterprise dynamic cluster to run WebSphere Portal. For each node that will be part of the dynamic cluster, follow the "Setting up a cluster" instructions using a WebSphere Virtual Enterprise deployment manager.

Important for i5/os only: Dynamic clusters are not supported because WebSphere Virtual Enterprise does not support installation on i5/OS.

The WasRemoteHostName and WasSoapPort properties, located in wkplc.properties, must be accurate at all times as many ConfigEngine scripts depend on them. If you are in a standalone environment, these parameters should point to the host name and soap port for server1. If you are in a clustered environment, these parameters should point to the Deployment manager host name and soap port. Only modify these properties when instructed to during the installation instructions.

If you add a node to a cell or change a node's configuration after it has been federated to the deployment manager, synchronize the node's configuration.

If you are planning to configure an external security manager to perform authentication or authorization for in a cluster environment, install the WebSphere Portal cluster first. Verify that the cluster is working properly before proceeding with the configuration of any external security managers.

i5/OS: Set up a recycling procedure WebSphere Portal database with the following command; this procedure automatically removes the unused journal files:

CHGJRN JRN(QWPS60/QSQJRN) DLTRCV(*YES)

QWPS60 is a default name of the WebSphere Portal database.

Parent topic:

Cluster