Dynamic cluster member settings

Use this page to manage the members of a dynamic cluster.

To view this administrative console page, click Servers > Dynamic clusters > dynamic_cluster_name > Dynamic cluster members > dynamic_cluster_member_name .

You must have operator privileges to manage the members of a dynamic cluster. For more information on administrative roles and privileges for managing dynamic clusters, see the Reference section of the Infocenter.

Member name

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

Data type: String

Weight

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 that are assigned to other servers in the cluster, then the server receives a larger share of the server workload.

The weight that is displayed depends on the tab in which you are viewing the information. If you are viewing the Runtime tab, the runtime weight displays. If you view the Configuration tab, the configured weight displays.
Important: If enabled, the dynamic workload manager (DWLM) overrides any values that you enter. DWLM is enabled by default. To disable DWLM, click Servers > Dynamic clusters > dynamic_cluster_name > Dynamic workload management (DWLM)
On the z/OS platform, weight is used to balance some of the workload types, but others are balanced by the z/OS system.
  • For HTTP requests, weights are used to distribute HTTP traffic between the Web server plug-in and the controller handling the clustered application server. Assign a higher weight value to the application server that is receiving the HTTP traffic.
  • For Web services calls, information is transferred from a servant in one application server to a controller in another application server. The application server that receives the call has the highest weight value.
  • Weight has no affect on Internet Inter-ORB Protocol (IIOP) requests. IIOP requests are distributed to the correct application server using the sysplex distributor.

Data type: Integer

Range: 0 to 20

Unique ID

Specifies a numerical identifier for the application server that is unique within the cluster. The ID is used for affinity. After a session is established in a particular cluster member, subsequent requests that belong to the same session are assigned to the cluster member that has the established session affinity.

Data type: Integer

Data type: Hexadecimal




WebSphere Virtual Enterprise information center (online)

Related information
Dynamic cluster collection
Dynamic cluster settings
Membership policy builder
Step 1: Select the dynamic cluster server type
Step 2: Select a membership method
Step 3: Define the dynamic cluster members
Step 4: Select a server template
Step 5: Configure the dynamic cluster properties
Step 6: Summary
Dynamic cluster member collection

dc_member_settings