Search Tips   |   Advanced Search

Starting servers using the job manager

In a flexible management environment, we can submit the Start server job to start an application server on a managed target. The job can start a stand-alone server or a server on a federated node of a deployment manager.

Start the job manager and the targets. If a target is a stand-alone application server, also start the administrative agent.

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

We can use the administrative console of the job manager or the deployment manager to start application servers on one or more managed targets. From the console, choose the Start server job, specify server and job options, review the summary, and submit the job.

We cannot start or stop the deployment manager or any node agent by using the job manager console with the submit jobs option. Performing such a start/stop job submission for the deployment manager or any node agent results in an error message similar to the following.

CWWSY0334E: Unable to locate node agent MBean when processing
 job startServer for server dmgr on node CellManager
The deployment manager or any node agent is unaffected by this action.gotcha

This topic describes how to run the Start server job using the job manager console or the deployment manager console. Instead of using a console, we can run the startServer job script in the AdministrativeJobs command group. See the Administrative job types topic.


  1. Click Jobs > Submit from the navigation tree of the administrative console.
  2. Choose a job to start a server.

    1. Select the Start server 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 targets from the list, or select Target names.

      Only groups of targets that are valid for the job type that you selected are displayed in the list of target groups.

    2. If you 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 start server job.

    1. For Server name, specify the name of server to start.

      To see the names of existing servers 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 node, nodeA, has a server named server2 that you want to start. Specify the name:

    2. If the target node is in a WebSphere Application Server, Network Deployment cell, specify the node name in the cell.

      You do not have to specify the node name for a base (stand-alone) node.

      For example, suppose the managed node, nodeA, is a federated node in a WAS, Network Deployment cell. Specify the node name:

    3. 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 you 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.

The targets run the job and attempt to start the application server.

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, correct the error condition, and submit the job again.

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

After starting the server, we can run the following jobs:

  • Set up a job manager environment
  • Starting and stopping the job manager
  • Starting and stopping the administrative agent
  • Create application servers using the job manager
  • Stopping servers using the job manager
  • Checking job status
  • Administrative job types
  • Find targets
  • Find target resources
  • Target resources collection