Server cluster settings

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.

Servers > Clusters > cluster_name.

 

Configuration tab

 

Cluster name

Specifies a logical name for the cluster. The name must be unique among clusters within the containing cell.

Data type	String

 

Prefer local

Specifies whether enterprise bean requests are routed to the node on which the client resides, if it is possible to do so.

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

 

Cluster name

Specifies a logical name for the cluster. The name must be unique among clusters within the containing cell.

Data type	String

 

Prefer local

Specifies whether enterprise bean requests are routed to the node on which the client resides, if it is possible to do so.

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

 

wlcID

Specifies the currently registered workload controller (WLC) identifier for the cluster. This setting might not display for all configurations.

Data type	String

 

State

Specifies whether cluster members are stopped, starting, or running.

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.

---

Clusters
Creating clusters
Administrative console buttons
Administrative console page features
Cluster member collection