Use this page to view or change the configuration of a server cluster instance, and to view the local topology of a server cluster instance.
To change the configuration and local topology of a server cluster, in the administrative console click Servers > Clusters > cluster_name.
To view runtime information, such as the state of the server cluster, click Servers > Clusters > cluster_name, and then click the Runtime tab.
Specifies a logical name for the cluster. The name must be unique among clusters within the containing cell.
Data type | String |
Specifies the node group that bounds this cluster. All application servers that are members of a cluster must be on nodes that are members of the same node group.
A node group is a collection of WebSphere Application Server nodes. A node is a logical grouping of managed servers, usually on a computer system that has a distinct IP host address. All application servers that are members of a cluster must be on nodes that are members of the same node group. Nodes that are organized into a node group need enough capabilities in common to ensure that clusters formed across the nodes in the node group can host the same application in each cluster member. A node must be a member of at least one node group and can be a member of more than one node group.
Create and manage node groups by clicking System administration > Node groups in the administrative console.
Specifies that the node scoped routing optimization is enabled or disabled. The default is enabled, which means that enterprise bean requests are routed to the client node when possible. Enabling this setting improves performance because client requests are sent to local enterprise beans.
Data type | Boolean |
Default | true |
Specifies that the recovery of a failed transaction is allowed to failover from one cluster member to another. Transaction log recovery requires several configuration steps, and this is one of the steps in that process.
See the IBM WebSphere Developer Technical Journal articleTransactional high availability and deployment considerations in WebSphere Application Server V6 for more information.
Specifies a logical name for the cluster. The name must be unique among clusters within the containing cell.
Data type | String |
Specifies that the node scoped routing optimization is enabled or disabled. The default is enabled, which means that enterprise bean requests are routed to the client node when possible. Enabling this setting improves performance because client requests are sent to local enterprise beans.
Data type | Boolean |
Default | true |
Specifies the currently registered workload controller (WLC) identifier for the cluster. This setting might not display for all configurations.
Data type | String |
Specifies whether the cluster is stopped, starting, or running.
If all cluster members are stopped, the cluster state is stopped. After you request to start a cluster, the cluster state briefly changes to 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 partially started until all cluster members are running, then the state changes to running. Similarly, when stopping a cluster, the state changes to partially stopped as the first member stops and changes to stopped when all members are not running.
Data type | String |
Range | Valid values are starting, partially started, running, partially stopped, or stopped. |