WebSphere Portal v6 - Set up a cluster
These instructions can be used to set up a cluster in either a horizontal or vertical scaling topology.
If while following these instructions you run into issues, we can back out the cluster and return to the non-clustered configuration.
- Install WAS Network Deployment (ND) on the deployment manager machine
IBM WAS ND on the deployment manager machine must be installed to the same product revision level as the WAS ND levels used on the cluster nodes and must have the same corrective service levels applied.
- Install and federate the primary node
When installing WebSphere Portal into a cluster environment, install the primary node. This machine will serve as the basis for the applications shared by the cluster members. We can install WebSphere Portal to a node that is already managed by the deployment manager, or we can install to a new profile and before federating the profile.
- Create the cluster
After the primary node is installed and running as a managed node under deployment manager control, create the cluster.
- Install and federate secondary nodes
After the primary node is federated into the cell and the cluster is created, we can expand the capacity of the cluster by adding additional nodes. This is only necessary if you are using horizontal scaling with the cluster.
- Add cluster members
After you have created the cluster, we can add additional cluster members to perform workload management and improve the availability of the applications. We can add horizontal cluster members on different machines or vertical cluster members on the same machine.
- Cluster validation
- Cluster troubleshooting
- Enable LDAP security after cluster creation
We can change the type of security you are using after you have created the cluster. For example, you might want to switch from the database user registry security provided by default when you install IBM WebSphere Portal to security based on an LDAP user registry.
Parent topic:
Clustering and WebSphere Portal