Before you start
Clustering is a key technique that you can use to improve the availability and the scalability of a WebSphere® Process Server environment. With WebSphere Process Server (hereafter called Process Server), you can use clustering techniques in many different ways to address availability and scalability. Each pattern centers around the number of Process Server clusters and cluster members. The most used environment is the Remote Messaging and Remote Support topology. This topology provides three separate clusters: a remote messaging cluster, a support infrastructure cluster, and an application deployment target cluster. With this three-cluster pattern, resources are allocated to the cluster that handles the highest loads. This pattern is the most flexible and versatile, and is preferred by most users. The components are divided between the three clusters.
- Learn how to setup and configure a double remote messaging and remote support topology.
- Understand the constraints and implications of a double Remote Messaging and Remote Support topology.
You should be familiar with the WebSphere Process Server topologies and cluster setups.
You need the following software:
- WebSphere Process Server v6.1.2 or above with all current iFixes installed
- A running WebSphere Process Server cell of the Remote Messaging and Remote Support topology
- WebSphere Application Server v126.96.36.199
- DB2® v8.1
Note: The figures used in this tutorial are taken from a WebSphere Process Server v6.1.2 environment. However, the guidelines in this tutorial are also applicable for version 6.2 of WebSphere Process Server.