Starting clusters using the job manager
In a flexible management environment, we can submit the Start cluster job to start a cluster that is on a managed target of the job manager.
Start the job manager and the managed targets. The cluster to start must be a resource managed by the job manager. The target cluster must have at least one cluster member. We 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. We 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, 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 administrative console of the job manager or the deployment manager to start clusters on one or more managed targets. From the 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 a console, we can run the startCluster job script in the AdministrativeJobs command group. See the Administrative job types topic.
- Click Jobs > Submit from the navigation tree of the administrative console.
- Choose a job to start a cluster.
- Select the Start cluster job type from the list.
- Optionally specify a description of the job.
- Click Next.
- Choose the job targets.
- Select a group of targets from the list, or select Target names.
- If we selected Target names, then specify a target on which a cluster resides and click Add, or click Find and specify the chosen targets on the Find targets page.
- If user authentication is required, specify a user name, password, or any other authentication values as needed.
- Click Next.
- Specify parameters for the start cluster job.
- For Cluster name, specify the name of cluster to start.
To see the names of existing clusters on the targets, click Find on the Specify job parameters page. On the Find target resources page, specify the targets and click Find. For example, suppose a managed target, myCellManager01, has a cluster named cluster2 to start. Specify the name:
- The cluster start operation to ripple across the cluster one member at a time, select Ripple start (true).
Otherwise, leave the field empty. The default is clear (false).
- Optionally, for Timeout in minutes specify the maximum amount of time in minutes to wait for the cluster to start before returning the state of the cluster.
- Click Next.
- Schedule the job.
The times and dates that specified are relative to the job manager.
- 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.
- Select when the job is available for submission.
- Select the job expiration.
- 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.
- Click Next.
- Review the summary, and click Finish to submit the job.
The targets 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
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 we can start the cluster successfully. After you correct the error condition, submit the job again.
If the job is successful, the status on the Target resources page of the cluster is RUNNING. Click Jobs > Target resources > resource_name to see the resource status.
When a cluster starts, its cluster members also start. If the Target 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.
Set up a job manager environment
Start and stop the job manager
Create clusters using the job manager
Create cluster members using the job manager
Stopping clusters using the job manager
Checking job status
Administrative job types
Find target resources
Target resources collection