In a flexible management
environment, you can submit the Stop
server job to stop an application server on a managed
target. 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 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 or targets. When you submit a job to multiple targets,
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
or the deployment manager to stop application servers on one or more
managed targets. From the console, choose the Stop server job,
specify server and job options, review the summary, and submit the
job.
Instead of using a 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 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 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.
- 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.
- If user authentication
is required, specify a user name,
password, or any other authentication values as needed.
- 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 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 target, 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 target name for a base (stand-alone) target.
For
example, suppose the managed target, 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 email addresses where
notifications are sent when the job finishes.
If you
specify multiple email 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 targets 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 Target 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