Stopping the WebSphere Application Server

In a clustered environment, you must stop all the components of WebSphere Application Server (WAS) in a specific order.
In a standalone environment, stop WAS with a single command. For example, in the command prompt, issue the following command:
WAS_ROOT\bin\stopServer server1

To stop WAS in a clustered environment:

  1. Stop application servers or server clusters.

    For example, in the command prompt, from the WAS_ROOT\profiles\profile\bin\directory, issue the stopServer serverName command.

    You can stop several servers simultaneously by using the WebSphere Application Server Administrative Console. In the administrative console, click Servers > Clusters > WebSphere application server clusters. Select the servers or clusters whose members you want started and click Stop.

  2. Stop MQ servers or server clusters.
    For example, in the command prompt, from the WAS_ROOT\profiles\profile\bin\directory, issue the stopServer serverName command.
  3. Stop the node agents.
    For example, in the command prompt, from the WAS_ROOT\profiles\profile\bin\directory, issue the stopNode command. You can also issue the following command: 
    WAS_ROOT\bin\stopNode -profileName profile
  4. Stop the deployment manager.
    For example, in the command prompt, from the WAS_ROOT\bin\directory, issue the stopManager command.
After these steps have been completed, WAS is no longer running.
Note:
When stopping a server, node agent, or deployment manager from the command line, you may be prompted for the administrative user name and password. To avoid this, issue the command in the following format:
WAS_ROOT\bin\stopServer server -username adminUser
        -password adminPassword