Before clustering WebSphere Portal you should consider following limitations:
- You must install WebSphere Portal as stand-alone node before creating the cluster, you can’t install it on an existing managed node.
- WebSphere Portal is not supported on a managed node that is not part of the clustered environment.
- It’s not possible to change the settings through Global Settings portlet or the XML configuration interface in a clustered environment. These changes must be made by changing respective properties in the the deployment manager console i.e Integrated Solutions Console (ISC) > Resources> Resource Environment> Resource environment.
- In order to support the search in a clustered environment you must install and configure search as a remote search service on an application server node that’s not part of the cluster.
- Do not use spaces in cluster or it’s member name when creating a cluster or adding a member into cluster.
- When creating the cluster verify that system time clock of Deployment Manager node and each future WebSphere Portal cluster member node is synchronized. If the time difference would be more than 5 minutes then during federating the portal node to dmgr it will fail.
- When creating dmgr profile for cluster make sure it’s cell and node name are different from portal profile cell and node name.