Limitations for setting up a cluster

Install WebSphere Portal as a stand-alone node before creating a cluster. We cannot install WebSphere Portal into a managed node.

Except for the initial setup of the cluster, WebSphere Portal is not supported on a managed node that is not part of a cluster.

A cluster can be created which contains only one WebSphere Portal server, enabling a single WebSphere Portal server to be operational in a managed cell.

We cannot use the Derby database. The WebSphere Portal databases must be transferred to a supported external database, for example: DB2, Oracle, or SQL Server .

In a clustered environment, it is not possible to change settings through the Global Settings portlet or xmlaccess.sh. These changes must be made by modifying the respective properties in the WAS console.

To support search, install and configure a remote search service on an application server node that is not part of the cluster.

Administrative actions for WebSphere Portal are immediately visible for the user who completes them. However, another user can be assured of seeing the changes only if the user logs out of WebSphere Portal and then logs back in. This limitation applies to both cluster and non-cluster environments.

When creating a cluster or a cluster member, do not use spaces in the cluster name or the cluster member name.

For the deployment manager and each WebSphere Portal node to be in the cluster, verify that each system clock is set to within 5 minutes of the others or the addNode command fails.

Parent Cluster considerations