IBM WebSphere Application Server – Start/Stop command line

Starting and stopping IBM WebSphere Application Server (WAS) Network Deployment involves managing the deployment manager, application servers, and node agents. Here are the basic commands for starting and stopping in a command-line environment:

Starting and Stopping Deployment Manager:

  1. Start Deployment Manager:<WAS_HOME>/bin/startManager.sh
  2. Stop Deployment Manager:<WAS_HOME>/bin/stopManager.sh

Starting and Stopping Nodes:

  1. Start Node Agent:<WAS_HOME>/profiles/<NodeProfile>/bin/startNode.sh
  2. Stop Node Agent:<WAS_HOME>/profiles/<NodeProfile>/bin/stopNode.sh
  3. Start Application Servers on a Node:<WAS_HOME>/profiles/<NodeProfile>/bin/startServer.sh serverName
  4. Stop Application Servers on a Node:<WAS_HOME>/profiles/<NodeProfile>/bin/stopServer.sh serverName

Note:

  • Replace <WAS_HOME> with the actual path to your WebSphere Application Server installation directory.
  • <NodeProfile> represents the profile name of the node.

Example Usage:

Assuming your WebSphere Application Server is installed in /opt/IBM/WebSphere/AppServer:

  1. Start Deployment Manager:/opt/IBM/WebSphere/AppServer/bin/startManager.sh
  2. Start Node Agent:/opt/IBM/WebSphere/AppServer/profiles/YourNodeProfile/bin/startNode.sh
  3. Start Application Servers on a Node:/opt/IBM/WebSphere/AppServer/profiles/YourNodeProfile/bin/startServer.sh server1

Additional Considerations:

  • Ensure that the necessary environment variables are set before running the commands.
  • It’s recommended to use the startServer and stopServer scripts from the node’s profile directory.

Always refer to the official IBM documentation specific to your version of WebSphere Application Server for the most accurate and up-to-date information. The commands and paths might vary based on the version of WebSphere Application Server you are using.

Leave a comment