Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Install and federating secondary nodes
After the primary node is federated into the cell and the cluster is created, you can expand the capacity of the cluster by adding additional nodes. This is only necessary if you are using horizontal scaling with your 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.
- 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 Express first and then federate the node, as described in Installing WebSphere Portal Express on an unmanaged node (secondary).
- Vertical scaling: If you intend to use WebSphere Portal Express in a vertical scaling topology, you can disregard the steps for installing a secondary node and proceed to Adding vertical cluster members.
- Installing WebSphere Portal Express on a managed node (secondary)
Install IBM WebSphere Portal Express on the secondary node. In this scenario, first install IBM WebSphere Application Server Network Deployment, and then federate the secondary node to the deployment manager before installing WebSphere Portal Express on the managed node. - Installing WebSphere Portal Express on an unmanaged node (secondary)
Install IBM WebSphere Portal Express on a secondary node in the cell. In this scenario, you install WebSphere Portal Express and then federate the node to bring it under deployment manager control.
Parent topic:
Setting up a cluster
Previous topic
Creating the cluster