Install and federate the primary node
Overview
The primary node machine is the first node configured in a cluster and serves as the basis for the Portal apps shared by cluster members. We can install WebSphere Portal to a node that is already managed by the deployment manager, or we can install Portal to an unmanaged node.
If you are installing IBM WebSphere Process Server (WPS) along with WebSphere Portal, install Portal into a managed node. WPS does not support installing on an unmanaged node and then federating the node to a cell.
Installation of Portal to a managed node is not supported in an i5/OS environment. Install WebSphere Portal first to an unmanaged node, and then federate the node.
Next Steps
- Install WebSphere Portal on a managed node (primary)
Install IBM WebSphere Portal on the primary node. In this scenario, first install IBM WAS Network Deployment and IBM WPS, and then federate the primary node to the deployment manager before installing WebSphere Portal on the managed node.
- Install WebSphere Portal on an unmanaged node (primary)
Install IBM WebSphere Portal on the primary 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
Installing WAS Network Deployment on the deployment manager machine
Next topic
Creating the cluster