Cluster member collection
Use this page to view and manage appservers that belong to a cluster.
You can also use this page to change the weight of any of the listed appservers.
A copy of the first cluster member that you create is stored as part of the cluster data and becomes the template for all additional cluster members that you create.
Any individual configuration change that you make to a cluster member does not affect the configuration settings of the cluster member template. You must use wsadmin commands to modify this template. Similarly, any changes that you make to the template does not affect existing cluster members.
To view this console page, click Servers > Clusters > cluster > Cluster members.
- Member name
- 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 appserver.
- Node
- Name of the node for the cluster member.
- V
Specify the version of the WAS product on which the cluster member runs.
- Configured weight
Specify the weight that is currently configured for the cluster member. The weight determines the amount of work that is directed to the appserver. 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
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
Specify 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 restart the node agent before you can start the cluster member.
Sub-topics
Cluster member settings
Related concepts
Clusters and workload management
Related tasks
Balancing workloads with clusters
Modifying cluster member templates using scripting
Adding members to a cluster
Related Reference
Node agent collection
Reference topic