Starting servers using the job manager

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

Before you begin

Start the job manager and the target nodes. If a target node 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 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 be applicable to all of the job targets.

About this task

You can use the administrative console of the job manager to start application servers on one or more managed nodes. From the job manager console, choose the Start server job, specify server and job options, review the summary, and submit the job.
Avoid trouble: [oct2010] You cannot start or stop the Deployment Manager or any node agent by using the Job Manager console with the submit job 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 on for server server dmgr on node CellManager
The Deployment Manager or any node agent is unaffected by this action. [oct2010]
oct2010
gotcha

This topic describes how to run the Start server job using the job manager console. Instead of using the job manager console, you can run the startServer 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 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 nodes from the list, or select Node names.

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

    2. If you selected Node names, then specify a node name 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 server job.
    1. For Server name, specify the name of server to start.

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

      For example, suppose the managed node, nodeA, is a federated node in a WebSphere Application Server, Network Deployment cell. Specify the node name:
      nodeA
    3. 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 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 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, correct the error condition, and submit the job again.

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

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




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_server
File name: tagt_jobmgr_start_server.html