WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

Cluster member collection

Use this page to view and manage application servers that belong to a cluster.

You can also use this page to change the weight or unique ID of any of the listed application servers.

To view this administrative console page, click Servers > Clusters > cluster_name > Cluster members.

Member name

Specifies the name of the server in the cluster. On most platforms, the name of the server is the process name. The name must match the (object) name of the application server.

Node

Specifies the name of the node for the cluster member.

Version

Specifies the version of the WebSphere Application Server product on which the cluster member runs.

Configured weight

Specifies the weight that is currently configured for the cluster member. The weight determines the amount of work that is directed to the application server. If the weight value for the server is greater than the weight values assigned to other servers in the cluster, the server receives a larger share of the cluster workload.

To change the configured weight for a cluster member you can either specify a new weight in the Configured weight field and click the Update button for the Configured weight column, or click on the name of the cluster member. Clicking the name of the cluster member navigates you to the page where you can change any of the configuration settings for that cluster member.

Runtime weight

Specifies the proportionate workload that is currently directed to the cluster member in comparison to the configured weight for that cluster member. To change the proportion, specify a new weight in the Runtime weight field and click the Update button for the Runtime weight column.

Status

Specifies whether a cluster member is running, stopped, or unavailable.

If a cluster member is stopped, its status is Stopped. After you request to start a cluster member by clicking Start, the status becomes Started. After you click Stop, its status changes to Stopped when it stops running.

Note that if the status is unavailable, the node agent is not running in that node and you must restart the node agent before you can start the cluster member.




Sub-topics
Related concepts
Clusters and workload management
Related tasks
Balancing workloads with clusters
Adding members to a cluster
Related reference
Node agent collection
Reference topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/urun_rwlm_member.html

© Copyright IBM Corporation 2002, 2006. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)