In a flexible management environment, you 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 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
.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 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.
You 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, you can run the startCluster job script in the AdministrativeJobs command group. See the Administrative job types topic.
The targets run the job and attempt to start the clusters and the cluster members.
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 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 Target resources page of the cluster is RUNNING. Click
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.