Starting or stopping a node is different than starting or stopping a node agent. This article describes how to stop or start a node agent. Refer to this article to stop or start a node agent. If you are not familiar with what a node is, or what the different between a node and a node agent is, refer to understanding the difference between a node and a node agent in WebSphere.
You can only start or stop a node after the node has been federated into the dmgr. If you attempt to use the startNode.sh (Linux), startNode.bat (Windows), stopNode.sh (Linux), or stopNode.bat (Windows) commands before a node has been federated into the dmgr, you will get the following exception. This exception occurs because the "nodeagents" directory is created after the node has been federated into the dmgr.
ADMU0111E: Program exiting with error: java.io.FileNotFoundException: was_home/profiles/your_profile/config/cells/your_cell/nodes/your_node/servers/nodeagents/server.xml (No such file or directory)
Starting or stopping a node will restart the JVMs and apps in the node. Nodes cannot span multiple computers.
Think of the node as the wrapper that contains the JVMs, and the JVMs contain the app. If a node is stopped, the JVMs and apps in the node will be stopped. Starting a node, using startNode.sh (Linux) or startNode.bat (Windows) will not start the JVMs in the node. After the node is started, you will then need to start the JVMs in the node.
If you want to start or stop a node using a deployment manager, add the node to the deployment manager.
- In the left panel of the WebSphere web console, expand System administration > Nodeagents.
- Check the node agent that you want to restart, and select Restart.
Start a node agent.
~]# /opt/IBM/WebSphere/AppServer/profile/profile_name/bin/startNode.sh . . . ADMU3000I: Server nodeagent open for e-business; process id is 12345
Stop a node agent.
~]# /opt/IBM/WebSphere/AppServer/profiles/profile_name/bin/stopNode.sh . . . ADMU4000I: Server nodeagent stop completed.