Limitations for setting up a cluster



Search Tips   |   Advanced Search


Starting with WebSphere Portal v6.1.0, install WebSphere Portal as a standalone node before creating a cluster; you can no longer install WebSphere Portal into a managed node.

Except for the temporary state during the initial setup of the cluster, WebSphere Portal is not supported when running on a managed node that is not part of a clustered environment.

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.

In a clustered environment, it is not possible to change settings through the Global Settings portlet or the XML configuration interface.

These changes must be made by modifying the respective properties in the administrative console.

To support search in a clustered environment, install search for remote search service on an appserver node that is not part of the cluster.

Administrative actions for WebSphere Portal are immediately visible for the user who performs 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.

i5/OS limitations:

Installation in a mixed node environment is not supported in an i5/OS environment.

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 will fail.

Parent topic: