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.
When installing a secondary node, the node is federated without including any of its applications. This is because the cell can contain only one set of these applications, and the applications have already been included when the primary node was federated.
If you intend to install IBM WebSphereProcess Server along with IBM WebSphere Portal to use business process integration, install to a managed node. WebSphere Process Server does not support installing on an unmanaged node and then federating the node to a cell. If you are installing WebSphere Portal without WebSphere Process Server, follow the instructions for installing WebSphere Portal on an unmanaged node (it is possible to install WebSphere Portal without WebSphere Process Server into a managed node, but detailed procedures for this scenario are not included in this documentation). If you choose to install WebSphere Portal without WebSphere Process Server on an unmanaged node and then federate the node, you will not be able to use the business process integration capabilities of WebSphere Process Server.
- i5/OS users:
Installation to a managed node is not supported in an i5/OS environment. If you are building a cluster on i5/OS, install WebSphere Portal first and then federate the node, as described in Installing WebSphere Portal on an unmanaged node (secondary).
- Vertical scaling:
If you intend to use WebSphere Portal in a vertical scaling topology, we can disregard the steps for installing a secondary node and proceed to Adding vertical cluster members.
- Installing WebSphere Portal on a managed node (secondary)
Install IBM WebSphere Portal on the secondary node. In this scenario, first install IBM WAS Network Deployment and IBM WebSphere Process Server, and then federate the secondary node to the deployment manager before installing WebSphere Portal on the managed node.
- Installing WebSphere Portal on an unmanaged node (secondary)
Install IBM WebSphere Portal on a secondary node in the cell. In this scenario, you install WebSphere Portal and then federate the node to bring it under deployment manager control.
Parent topic:
Setting up a cluster
Previous topic
Creating the cluster
Next topic
Adding cluster members