Cluster member settings
Use this page to manage the members of a cluster. A cluster of appservers are managed together and participate in workload management.
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 > cluster_member_name.
Configuration tab
- 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.
Data type String
- Weight
Specify 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, then the server receives a larger share of the server workload.
Data type Integer Range 0 to 20
- Unique ID
Specify a numerical identifier for the appserver that is unique within the cluster. The ID is used for affinity.
Data type Integer
- Run in development mode
Enabling this option may reduce the startup time of an appserver. 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 appservers running WebSphere Application Server V6.0 and later.
Specify 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
- Parallel start
Specify whether to start the server on multiple threads. Starting the server on multiple threads might shorten the startup time.
Specify 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).
The order in which applications start depends on the weight you assign to each application. The application with the lowest starting weight starts first. Applications with the same starting weight start in parallel. You use the Start weight field on the Applications > Enterprise Applications > application page of the console to set the starting weight for an application.
Data type Boolean Default true
- Class loader policy
Specify whether there is a single class loader to load all applications or a different class loader for each application.
- Class loading mode
Specify 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 WAS 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
- 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.
Data type String
- Weight
Specify 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, then the server receives a larger share of the server workload.
Data type Integer Range 0 to 20
- Process Id
- Native operating system process ID for this server.
The process ID property is read only. The system automatically generates the value.
- Cell name
- Name of the cell in which this server is running.
The Cell name property is read only.
- Node name
- Name of the node in which this server is running.
The Node name property is read only.
- State
- 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
Configure application startup
Modifying cluster member templates using scripting
Related Reference
Cluster member collection
Reference topic