There are various installation and configuration
tasks
that require you to start and stop IBM® WebSphere® Application Server and the IBM WebSphere Portal application servers,
deployment managers, and node agents. If you are not familiar with
how to start and stop these servers, deployment managers, or node
agents, you can refer to this file for the necessary steps.
About this task
Complete
the following
steps to start and stop servers, deployment
managers, and node agents:Procedure
- Open a command
prompt and change to the following directory:
Note: In
a clustered environment, use the
dmgr_profile_root directory
and not the
wp_profile_root directory.
- Complete the following steps
to start the servers, deployment
managers, and node agents
Table 1. Steps to start
the servers, deployment managers, and node agents.Server |
Steps |
Deployment
manager |
Enter the following command:- UNIX: ./startManager.sh
- Windows: startManager.bat
- IBM i: startManager
- z/OS: ./startManager.sh
|
Node agent |
Enter
the following command:- UNIX: ./startNode.sh
- Windows: startNode.bat
- IBM i: startNode.sh
- z/OS: ./startNode.sh
|
WebSphere Portal server |
Enter the following command: Note: If you have
a clustered environment or you renamed your WebSphere Portal server, WebSphere_Portal will
be the name you defined for your WebSphere Portal server.
- UNIX: ./startServer.sh WebSphere_Portal
- Windows: startServer.bat WebSphere_Portal
- IBM i: startServer WebSphere_Portal
- z/OS: ./startServer.sh WebSphere_Portal
|
- Complete the following steps to stop the servers,
deployment
managers, and node agents:
Table 2. Steps to stop
the servers, deployment managers, and node agentsServer |
Steps |
WebSphere Portal server |
Enter the following command: Note: If you have
a clustered environment or you renamed your WebSphere Portal server, WebSphere_Portal will
be the name you define for your WebSphere Portal server.
- UNIX: ./stopServer.sh WebSphere_Portal
- Windows: stopServer.bat WebSphere_Portal
- IBM i: stopServer WebSphere_Portal
- z/OS: ./stopServer.sh WebSphere_Portal
|
Node agent |
Enter the following command:- UNIX: ./stopNode.sh
- Windows: stopNode.bat
- IBM i: stopNode.sh
- z/OS: ./stopNode.sh
|
Deployment manager |
Enter the following command:- UNIX: ./stopManager.sh
- Windows: stopManager.bat
- IBM i: stopManager
- z/OS: ./stopManager.sh
|
- In a clustered environment, you can
use the deployment
manager WebSphere Integrated Solutions Console to stop
and start the application servers that are managed by the deployment
manager:
Table 3. Using the deployment manager WebSphere Integrated Solutions Console to stop and start
the application servers that are managed by the deployment manager.Option |
Steps |
Start a specific application server in a
cell |
Complete the following steps
to start a specific
application server in a cell:- Open the deployment manager WebSphere Integrated Solutions Console.
- Click .
- Select the required server
and click Start.
|
Start the entire cluster |
Complete the following steps to start the entire
cluster:- Open the deployment manager WebSphere Integrated Solutions Console.
- Click .
- Select the cluster and click Start or Ripple
Start.
|
Stop a specific server in a cell |
Complete the following steps to stop a specific
application server in a cell:- Open the deployment manager WebSphere Integrated Solutions Console.
- Click .
- Select the required server
and click Stop or Immediate
Stop.
|
Stop the entire cluster |
Complete
the following steps to stop the entire
cluster:- Open the deployment manager WebSphere Integrated Solutions Console.
- Click .
- Select the cluster and click Stop or Immediate
Stop.
|