Use this page to specify settings for the first cluster member.
There are two ways to create the first member of a cluster:
To create a new cluster, in the administrative console, click
.To create a cluster member for an existing cluster, in the administrative console, click
cluster_name .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.
Specifies the name of the application server that is created for the cluster.
The member name must be unique on the selected node.
Specifies the node on which the application server resides.
Specifies the 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 you do not specify a short name, the system assigns a default short name that is automatically unique within the cell. You can change the generated short name to conform with your naming conventions.
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, the server receives a larger share of the cluster workload. The value can range from 0 to 20. Enter zero to indicate that you do not want requests to route to this application server unless this server is the only server that is available to receive requests.
Specifies the core group in which the application server resides. This field displays only if you have multiple core groups configured. You can change this value only for the first cluster member.
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.
Specifies the basis you want to use for the first cluster member.
If you select the defaultZOS template, which is the only one that is listed unless you used the createApplicationServerTemplate command for the AdminTask object to create additional templates, the first cluster member uses the default port assignments for the z/OS platform. If some of these ports are already defined for use elsewhere in your z/OS system, your newly created cluster member might not start, might function incorrectly, or might generate unexpected error messages. Therefore, you must resolve any port conflicts before you start this server.