Create appservers using the job manager

In a flexible management environment, we can submit the Create appserver job to create a server. The job can create an appserver on a stand-alone node or on a federated node of a dmgr.

Start the job manager and the target nodes. If a target node is a stand-alone appserver node, 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, we 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 the job targets.

Use the admin console of the job manager to create an appserver on one or more managed nodes. From the job manager console, choose the Create application server job, specify server and job options, review the summary, and submit the job.

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

 

  1. Click Jobs > Submit from the navigation tree of the job manager administrative console.

  2. Choose a job to create a server.

    1. Select the Create appserver job type from the list.

    2. Optionally specify a description of the job.

    3. Click Next.

  3. Choose the job targets on which to add the server.

    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 the user name and password.

    4. Click Next.

  4. Specify parameters for the create server job.

    1. For Server name, specify a server name that is unique on the target nodes. 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 one server, server1. Specify a name that is unique to nodeA:
      server2
      

    2. If the target node is in a WAS, ND cell, specify the node name in the cell on which to create the server.

      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, ND cell. Specify the node name:

      nodeA
      

    3. To use a template other than the default server template, specify the name and location of the template to use.

    4. To use a specific port number and not use the unique port number generated by WAS ND, specify false for Generate unique ports.

    5. If creating a server on a z/OS node, optionally specify short names and bit mode.

      If you do not specify values, WAS generates unique short names and uses the default bit mode.

    6. 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 create the appserver.

 

Next steps

On the Job status page, click the ID of the create application server job and view the job status. Click the status refresh icon

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, click Jobs > Node resources to see the new appserver in the list of resources.

After creating the server, we can run a job that starts the server.



Related tasks
Set up a job manager environment
Starting and stopping the job manager
Starting and stopping the admin agent
Starting and stopping the dmgr
Starting and stopping a node
Check job status
Starting servers using the job manager

Related reference
Administrative job types using wsadmin scripting
Find nodes
Find node resources
Node resources collection

Last updated Nov 10, 2010 8:23:07 PM CST