Use this page to view or change the configuration and local topology of a server cluster instance. Provided you saved your administrative configuration after creating the server cluster instance, you can also view run-time information such as the status of the server cluster instance.
To view this administrative console page, click Servers > Clusters > cluster_name.
Configuration tab
Data type | String |
The name is 1-8 characters, alpha-numeric or national language. It cannot start with a number.
Data type | String |
The unique ID property is read only. The system automatically generates the value.
Select the Prefer Local check box to specify routing of requests to the node on which the client resides. By default, the Prefer Local check box is selected, specifying routing of requests to the node.
Data type | Boolean |
Default | true |
Runtime tab
Data type | String |
Select the Prefer Local check box to specify routing of requests to the node on which the client resides. By default, the Prefer Local check box is selected, specifying routing of requests to the node.
Data type | Boolean |
Default | true |
Data type | String |
If all cluster members are stopped, the cluster state is websphere.cluster.stopped. After you request to start a cluster, the cluster state briefly changes to websphere.cluster.starting and each server that is a member of that cluster launches, if it is not already running. When the first member launches, the state changes to websphere.cluster.partial.start. The state remains websphere.cluster.partial.start until all cluster members are running, then the state changes to websphere.cluster.running. Similarly, when stopping a cluster, the state changes to websphere.cluster.partial.stop as the first member stops and changes to websphere.cluster.stopped when all members are not running.
Data type | String |
Range | Valid values are websphere.cluster.starting, websphere.cluster.partial.start, websphere.cluster.running, websphere.cluster.partial.stop, or websphere.cluster.stopped. |