Create cluster members using the job manager

In a flexible management environment, we can submit the Create cluster member job to create a server to add to a cluster. A cluster is a set of servers that you manage together to balance workload. The cluster can group application servers, proxy servers, or on-demand routers. Each server in the cluster is a cluster member. The job creates a cluster member that runs on a deployment manager node. The cluster member becomes a managed resource of the job manager.

Start the job manager, the deployment manager on which the cluster resides, and federated nodes of the deployment manager. A cluster must exist on a deployment manager node.

Determine how to configure the cluster member:

Your ID at the job manager must be authorized for the administrator role or the operator role to submit jobs. When you submit a job, we can specify a user name and password for authentication and authorization at the target or targets. When you submit a job to multiple targets, the user name and password or the credentials for the submitter must apply to all the job targets.

We can use the console of the job manager or the deployment manager to create a cluster member for one or more managed clusters. From the console, choose the Create cluster member job, select the clusters to which to add members, specify job options, review the summary, and submit the job.

Instead of using a console, we can run the createClusterMember job script in the AdministrativeJobs command group. See the Administrative job types topic.

  1. Click Jobs > Submit from the navigation tree of the console.

  2. Choose a job to create a cluster member.

    1. Select the Create cluster member job type from the list.

    2. Optionally specify a description of the job.

    3. Click Next.

  3. Choose the job targets on which to add the cluster member.

    Select one or more managed deployment manager nodes that have the target cluster.

    1. Select a group of targets from the list, or select Target names.

    2. If we selected Target names, then specify a target name and click Add, or click Find and specify the chosen targets on the Find targets page.

    3. If user authentication is required, specify a user name, password, or any other authentication values as needed.

    4. Click Next.

  4. Specify parameters for the create cluster member job.

    1. For Cluster name, specify the name of the cluster to which to add a member. For example, suppose a managed deployment manager cell, myCellmanager01, has a managed cluster, cluster2. Specify the name of the cluster that is managed by the job manager:

        cluster2

    2. For Member node, specify the name of the node on which the target cluster resides. For example, suppose the Target resources page shows that the deployment manager node on which cluster2 resides is named myNode01. Specify the member node name:

        myNode01

    3. For Member name, specify a cluster member name that is unique on the target cluster. For example, suppose a target cluster, cluster2, has one cluster member, cluster_member_1. Specify a name that is unique to cluster2:

        cluster_member_2

    4. The new cluster member to have a Member weight value other than 2, the default, specify a different weight value.

      A valid weight value is a number between 0 and 100. The weight controls the amount of work directed to the server. If the weight is greater than the weight assigned to other cluster members, the server receives a larger share of the workload.

    5. Optionally, specify a universally unique identifier (UUID) for the cluster member.

      If we do not specify a value, the product generates a UUID.

    6. If we do not want the product to generate unique port numbers for the cluster member, clear Generate unique ports.

      By default, the product generates unique port numbers for HTTP transports defined in the server. The default value is selected (true).

    7. If the cluster has a replication domain and to create a replicator entry for the new cluster member in the cluster replication domain, select Replicator entry (true).

      The product uses a replication domain for HTTP session data replication. By default, the product does not create a replicator entry for a cluster member in the cluster replication domain. The default value is clear (false).

    8. For a cluster on a z/OS target, optionally specify a cluster member short name.

      If we do not specify a value, the product generates a unique short name.

    9. Optionally, expand Additional job parameters and specify values that further define the cluster member.

      Parameter name Description
      Template name To use a specific cluster member template, specify the name of the template.
      Template node name To use an existing cluster member as a template, specify the name of the node that has a cluster member to use as a template for the new cluster member.
      Template server name To use a specific server as a template for the new cluster member, specify the server name.
      Node group The cluster member to belong to a node group, specify the name of the node group.
      Core group The cluster member to belong to a core group, specify the name of the core group.

    10. Click Next.

  5. Schedule the job.

    The times and dates specified are relative to the job manager.

    1. Optionally specify one or more email addresses where notifications are sent when the job finishes.

      If we specify multiple email addresses, separate them with commas.

    2. Select when the job is available for submission.

    3. Select the job expiration.

    4. Optionally specify a recurring interval for the job, a start date and time for the interval, and an end date and time for the interval.

    5. Click Next.

  6. Review the summary, and click Finish to submit the job.


Results

The targets run the job and attempt to create a cluster member of the target cluster.


What to do next

On the Job status page, click the ID of the create cluster member job and view the job status. If the job is not successful, view any error messages that result from running the job, correct the error condition, and submit the job again.

If the job is successful, click Jobs > Target resources to see the new cluster member in the list of resources. The status of the member is Stopped.

After creating the cluster member, we can run a job that starts the cluster. Starting the cluster also starts the cluster member.


Related concepts

  • Clusters and workload management


    Related tasks

  • Create clusters
  • Start and stop the job manager
  • Start and stop the deployment manager
  • Start and stop a node
  • Set up a job manager environment
  • Create clusters using the job manager
  • Start clusters using the job manager

  • Administrative job types
  • Find targets
  • Find target resources
  • Target resources collection
  • Create a cluster: Create first cluster member