Create a cluster: Create first cluster member

Use this page to specify settings for the first cluster member.

There are two ways to create the first member of a cluster:

When you create the first cluster member, a copy of that member is stored as part of the cluster data and becomes the template for all additional cluster members that you create.

When adding servers to a cluster, remember that the only way to remove an application server from a cluster is to delete the application server from the list of cluster members.


Member name

Name of the application server created for the cluster.

The member name must be unique on the selected node.


Select node

Node on which the application server resides.


(zos) Short name

Short name for this cluster member. This field only applies to the z/OS platform.

The short name is the default z/OS job name and identifies the cluster member to the native facilities of the operating system, such as Workload Manager (WLM), Automatic Restart Manager, SAF (for example, RACF ), started task control, and others.

If we specify a short name for a cluster member, the name:

If we do not specify a short name, the system assigns a default short name that is automatically unique within the cell. We can change the generated short name to conform with the naming conventions.


Weight

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. The value can range from 0 to 20. Enter zero to indicate that we do not want requests to route to this application server unless this server is the only server that is available to receive requests.

(zos) On z/OS, weight is used to balance some of the workload types, but others are balanced by the z/OS system.


Core group

Core group in which the application server resides. This field displays only if you have multiple core groups configured. We can change this value only for the first cluster member.


Generate unique HTTP ports

Specifies that a unique HTTP port is generated for the application server. By generating unique HTTP ports for the application server, you avoid potential port collisions and configurations that are not valid.


Select how the server resources are promoted in the cluster

How resources such as data sources and schedulers are initially created in the cluster. Create settings at the cluster scope if the settings can be used across the entire cluster. Otherwise, create settings at the cluster member (server) level. Creating settings at the cluster scope reduces the amount of configuration that you maintain.

When creating a cluster, this setting is disabled if you select None. Create an empty cluster for the Select basis for first cluster member setting. Otherwise, this setting is enabled.

The list has the following options.

Cluster

Moves the resources of the first cluster member to the cluster level. The resources of the first cluster member replace the resources of the cluster. Move resources of the first cluster member when to promote the resources of a server to the cluster. Promoting resources is the recommended option.

The Cluster option is the default behavior in the console.

Server

Maintains the server resources at the new cluster member level and does not change the cluster level resources.

The Server option is most useful in the following situations:

  • When you want different configuration settings for resources defined on each cluster member.

  • When you have deleted all of the cluster members and want to create new cluster members. However, we do not want to replace the cluster scoped resources when creating the cluster members.

Both

Copies the resources of the cluster member (server) to the cluster level. The resources of the first cluster member replace the resources of the cluster. The same resources exist at both the cluster and cluster member scopes.

Important: These options are available only for the first cluster member. All other members of a cluster are based on the cluster member template which is created from the first cluster member.


Select basis for first cluster member

Basis to use for the first cluster member.

Important: The basis options are available only for the first cluster member. All other members of a cluster are based on the cluster member template which is created from the first cluster member.


Related concepts

  • Clusters and workload management

    Create a cluster: Basic cluster settings

    Create a cluster: Create additional cluster members

    Create a cluster: Summary settings

  • Commands (AdminTask)