Server cluster settings

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.

To display the topology of a specific cluster, click Servers > Clusters > cluster_name, and then click the Local Topology tab.

If the high availability infrastructure is disabled and you require IIOP routing capabilities, follow the instructions contained in the topic Enabling static routing for a cluster to create a static route table. This table will enable the cluster to handle IIOP requests.

Important:

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

Bounding node group name

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.

Prefer local

Specifies that the host scoped routing optimization is enabled or disabled. The default is enabled, which means that, when possible, enterprise bean requests are routed to the client host. Enabling this setting improves performance because client requests are sent to local enterprise beans.

Data type Boolean
Default true
Supported configurations Supported configurations: If you enable the preferLocal optimization, the deployment manager must be running to affect the configuration. If the deployment manager is shut down, preferLocal optimization is not performed and requests might be dispersed across all the members of the cluster.sptcfg

Enable failover of transaction log recovery

Specifies that for the transaction service component, failover of the transaction log for recovery purposes is enabled or disabled. The default is disabled.

When this setting is enabled, and the transaction service properties required for peer recovery of failed application servers in a cluster are properly configured, failover recovery of the transaction log occurs if the server processing the transaction log fails. If the transaction services properties required for peer recovery of failed application servers in a cluster are not properly configured, this setting is ignored.

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 that the host scoped routing optimization is enabled or disabled. The default is enabled, which means that, when possible, enterprise bean requests are routed to the client host. Enabling this setting improves performance because client requests are sent to local enterprise beans.

Data type Boolean
Default true
Supported configurations Supported configurations: If you enable the preferLocal optimization, the deployment manager must be running to affect the configuration. If the deployment manager is shut down, preferLocal optimization is not performed and requests might be dispersed across all the members of the cluster.sptcfg

State

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.



Related concepts
Clusters and workload management
Transactional high availability
Related tasks
Creating clusters
Configuring transaction properties for peer recovery
Enabling static routing for a cluster
Disabling static routing for a cluster
Related reference
Backup cluster settings
Cluster topology
Server cluster collection
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 10:47:11 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-iseries&topic=urun_rwlm_cluster_svr
File name: urun_rwlm_cluster_svr.html