Set up multiple clusters on Solaris
The majority of the steps to build another cluster are the same as when building the first cluster in the same cell, with a few exceptions. Basically, the new profile will be designated as the primary profile, using WebSphere Portal clustering terminology, and will then be used as the basis for the new cluster definition. This duplicates the build process of the first cluster in the cell. During the federation process, if any applications on this new node already exist in the cell (because they are in use by the first cluster), then Deployment Manager will not allow them to be added. After federation, the applications that already exist in the cell are not mapped to the WebSphere_Portal server on the newly federated node, and thus the existing applications must be remapped to this newly federated server to restore its application list. Therefore, depending on the configuration of the new profile, there will likely be some combination of applications shared with the other existing cluster, and some applications unique to this new profile.
Before attempting alternative approaches for building multiple portal-based clusters within a single cell, please contact IBM.
Prerequisites
Prepare the Solaris OS
Prepare the primary node on Solaris
Tune the servers
Parent
Set up a cluster on Solaris
Related tasks
Prepare the WAS Deployment Manager on Solaris
Prepare to create the cluster on Solaris
Prepare a remote Web server when portal is installed on Solaris in a clustered environment
Configure WebSphere Portal to use a user registry on Solaris in a clustered environment
Prepare additional nodes on Solaris
Configure search in a cluster on Solaris
Share database domains between clusters on Solaris