Use this page to view and manage application servers that belong to a cluster.
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 administrative console page, click Servers > Clusters > cluster_name > Cluster members.
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.
Specifies the name of the node for the cluster member.
Specifies the version of the WebSphere Application Server product on which the cluster member runs.
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.
Specifies the proportionate workload that is currently directed to the cluster member in comparison to the runtime weights of the rest of the cluster members.
The runtime weight only applies for Remote Method Invocation over Internet Inter-ORB Protocol (RMI-IIOP) requests, Enterprise JavaBeans (EJB) requests, and HTTP requests received through a WebSphere Application Server proxy server.
You can use the Runtime weight property to dynamically adjust the weight that is given to a particular cluster member without having to stop and then restart that cluster member. To change the proportion, specify a new weight for the Runtime weight property, and then click the Update button for the Runtime weight column. The runtime weight change takes effect immediately.
This field indicates whether the cluster member is started, stopped, partially stopped, or unavailable. 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 server.
![]() |
Started | The cluster member is running. |
![]() |
Partially stopped | The cluster member is in the process of changing from a started state to a stopped state. |
![]() |
Stopped | The cluster member is not running. |
![]() |
Unavailable | Status cannot be determined. A cluster member with an unavailable status might, in fact, be running but has an unavailable status because the cluster member that is running the administrative console cannot communicate with this cluster member. |