Starting clusters using the job manager

In a flexible management environment, you can submit the Start cluster job to start a cluster that is on a managed node of the job manager.

Before you begin

Start the job manager and the managed nodes. The cluster that you want to start must be a resource managed by the job manager. The target cluster must have at least one cluster member. You cannot start a cluster unless it has a cluster member.

You might need to synchronize the nodes of the deployment manager to start the cluster successfully. You can use the Nodes page of the deployment manager administrative console to synchronize the nodes. Click System administration > Nodes > Synchronize.

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, you can specify a user name and password for authentication and authorization at the target node or nodes. When you submit a job to multiple target nodes, the user name and password or the credentials for the submitter must apply to all the job targets.

About this task

You can use the administrative console of the job manager to start clusters on one or more managed nodes. From the job manager console, choose the Start cluster job, specify job options, review the summary, and submit the job.

When you start a cluster, all the application servers that are members of that cluster start automatically.

Instead of using the job manager console, you can run the startCluster job script in the AdministrativeJobs command group. See the Administrative job types topic.

Procedure

  1. Click Jobs > Submit from the navigation tree of the job manager administrative console.
  2. Choose a job to start a cluster.
    1. Select the Start cluster job type from the list.
    2. Optionally specify a description of the job.
    3. Click Next.
  3. Choose the job targets.
    1. Select a group of nodes from the list, or select Node names.
    2. If you selected Node names, then specify a node on which a cluster resides and click Add, or click Find and specify the chosen nodes on the Find nodes page.
    3. If user authentication is required, specify your user name and password.
    4. Click Next.
  4. Specify parameters for the start cluster job.
    1. For Cluster name, specify the name of cluster to start.

      To see the names of existing clusters on the target nodes, click Find on the Specify job parameters page. On the Find node resources page, specify the target nodes and click Find.

      For example, suppose a managed node, myCellManager01, has a cluster named cluster2 that you want to start. Specify the name:
      cluster2
    2. If you want the cluster start operation to ripple across the cluster one member at a time, specify true for Ripple start.

      Otherwise, leave the field empty. The default is false.

    3. Optionally, specify the maximum amount of time in minutes to wait for the cluster to start before returning the state of the cluster.
    4. Click Next.
  5. Schedule the job.

    The times and dates that you specify are relative to the job manager.

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

      If you specify multiple e-mail 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 target nodes run the job and attempt to start the clusters and the cluster members.

What to do next

On the Job status page, click the ID of the start server job and view the job status. Click the status refresh icon Specifies the refresh view icon for job status to refresh the displayed status.

If the job is not successful, view any error messages that result from running the job. You might need to synchronize the nodes of the deployment manager before you can start the cluster successfully. After you correct the error condition, submit the job again.

If the job is successful, the status on the Node resources page of the cluster is RUNNING. Click Jobs > Node resources > resource_name to see the resource status.

When a cluster starts, its cluster members also start. If the Node resources page shows that the cluster is RUNNING but the status of cluster members is Stopped, submit the Status or Inventory job. Both jobs refresh data on managed resources. If the status of cluster members remains Stopped, submit the Start server job to start a cluster member.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Oct 22, 2010 12:21:29 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-zos&topic=tagt_jobmgr_start_cluster
File name: tagt_jobmgr_start_cluster.html