Use this page to manage the members of a cluster. A cluster of application servers are managed together and participate in workload management.
To view this administrative console page, click Servers > Clusters > cluster_name > Cluster members > cluster_member_name.
Configuration tab
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.
Data type | String |
Specifies 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, then the server receives a larger share of the server workload.
Data type | Integer |
Range | 0 to 20 |
Specifies a numerical identifier for the application server that is unique within the cluster. The ID is used for affinity.
Data type | Integer |
Enabling this option may reduce the startup time of an application server. This may include JVM settings such as disabling bytecode verification and reducing JIT compilation costs. Do not enable this setting on production servers. This setting is only available on application servers running WebSphere Application Server Version 6.0 and later.
Specifies that you want to use the JVM settings -Xverify and -Xquickstart on startup. After selecting this option, save the configuration and restart the server to activate development mode.
The default setting for this option is false, which indicates that the server will not be started in development mode. Setting this option to true specifies that the server will be started in development mode (with settings that will speed server startup time).
Data type | Boolean |
Default | false |
Specifies whether to start the server on multiple threads. Starting the server on multiple threads might shorten the startup time.
Specifies that you want the server components, services, and applications to start in parallel rather than sequentially.
The default setting for this option is true, which indicates that the server be started using multiple threads. Setting this option to false specifies that the server will not be started in using multiple threads (which may lengthen startup time).
Note that the order in which the applications start depends on the weights you assigned to each of them. Applications that have the same weight are started in parallel. You set an application's weight with the Starting weight option on the Applications > Enterprise Applications > application_name page of the Administrative Console. For more information about the Starting weight option, see Enterprise application settings.
Data type | Boolean |
Default | true |
Specifies whether there is a single class loader to load all applications or a different class loader for each application.
Specifies whether the class loader should search in the parent class loader or in the application class loader first to load a class. The standard for Developer Kit class loaders and WebSphere Application Server class loaders is Parent first.
This field only applies if you set the Class loader policy field to single.
If you select Parent last, your application can override classes contained in the parent class loader, but this action can potentially result in ClassCastException or linkage errors if you have mixed use of overridden classes and non-overridden classes.
Runtime tab
The native operating system's process ID for this server.
The process ID property is read only. The system automatically generates the value.
The name of the cell in which this server is running.
The Cell name property is read only.
The name of the node in which this server is running.
The Node name property is read only.
The run-time execution state for this server.
The State property is read only.
Related concepts
Clusters and workload management
Related tasks
Adding members to a cluster
Related reference
Cluster member collection