In a flexible management environment, you can submit the Stop
server job to stop an application server on a managed
node. The job can stop a stand-alone server or a federated node of
a deployment manager.
Before you begin
Start the job manager if it is not already running. The
target application server must also be running. 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 the job targets.
About this task
You can use the administrative console of the job manager
to stop application servers on one or more managed nodes. From the
job manager console, choose the Stop server job,
specify server and job options, review the summary, and submit the
job.
Instead of using the job manager console, you can run the
stopServer job script in the AdministrativeJobs command group. See
the Administrative job types topic.
Procedure
- Click from the navigation tree of the job manager administrative
console.
- Choose a job to stop a server.
- Select the Stop server job type
from the list.
- Optionally specify a description of the job.
- Click Next.
- Choose the job targets.
- 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.
- 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.
- If user authentication is required, specify your user
name and password.
- Click Next.
- Specify parameters for the stop server job.
- For Server name, specify the
name of server to stop.
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 stop.
Specify the name:server2
- 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 WebSphere Application Server, Network Deployment cell. Specify the node name:nodeA
- Click Next.
- Schedule the job.
The times and dates that
you specify are relative to the job manager.
- 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.
- 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.
Results
The target nodes run the job and attempt to stop the application
server.
What to do next
On the Job status page, click the ID of the stop 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 Node resources page of the
server is Stoppped. Click to see the resource status.
After stopping the
server, you can run the following jobs:
- Start server
- Delete application server