Stopping IBM WebSphere Application Server (Linux, UNIX)

Follow this procedure to shut down WebSphere® Application Server services in a Linux® or UNIX installation.

Procedure

Do either of the following tasks, depending on whether you have a stand-alone or clustered configuration:
Stopping a WebSphere Application Server Liberty Profile or Network Deployment stand-alone configuration:
  1. Log in to the computer that hosts the services tier. Use the following credentials:
    • In release 11.3.1 Fix Pack 2 and beyond, if you have configured WebSphere Application Server for non-root administration, use the credentials for the non-root user that is configured to administer WebSphere Application Server.
    • For all other configurations, log in as root.
  2. Run the following commands:
    cd /opt/IBM/InformationServer/ASBServer/bin
./MetadataServer.sh stop
  3. Verify that WebSphere Application Server processes have stopped. See Checking the status of IBM WebSphere Application Server (Liberty Profile installation) or Checking the status of IBM WebSphere Application Server Network Deployment (stand-alone installation).
Stopping a clustered WebSphere Application Server Network Deployment configuration:
  1. Log in to the node that hosts the Deployment Manager. Use the WebSphere Application Server administrator credentials.
  2. In the console navigation tree, click Servers > Clusters to access the Server Cluster page.
    Note: Depending on your WebSphere Application Server version, you might have to click Servers > Clusters > WebSphere Application Server clusters to access the Server Cluster page.
  3. Select the cluster.
  4. Click Stop. This command allows each application server to finish existing requests and allows failover to another member of the cluster. When the stop operation begins, the cluster status changes to partially stopped. After all application servers stop, the cluster status becomes Stopped.
  5. On each node, log in by using WebSphere Application Server administrator credentials.
  6. On the node, run the stopNode command to stop the node agent. Specify the correct profile:
    /opt/IBM/WebSphere/AppServer/profiles/Custom01/bin/stopNode.sh 
   -user wasadmin -password mypassword
    Custom01 is the WebSphere Application Server custom profile that hosts a node of the IBM® InfoSphere® Information Server cluster. wasadmin is the user name of the WebSphere Application Server administrator. password is the password.
  7. Verify that all cluster members and node agents are stopped. See Checking the status of IBM WebSphere Application Server cluster members and Checking the status of IBM WebSphere Application Server node agents.
  8. Stop the Deployment Manager. See Stopping the IBM WebSphere Application Server Deployment Manager (Linux, UNIX).