Starting or stopping a WebSphere JVM will restart the JVM and all of the apps in the JVM. Restarting the JVM will not restart the node / node agent, deployment manager, or cell.
If using the web console, you will need to sign into the network deployment manager (dmgr) web console.
- In the left panel of the WebSphere web console, expand Servers > Server Types.
- Select Websphere application servers.
- Check the application server that should be restarted, and select Restart.
Start an application server.
~]# /opt/IBM/WebSphere/AppServer/bin/startServer.sh server_name -profileName profile_name . . . ADMU4000I: Server server_name open for e-business; process id is 12345
The SystemOut.log file will contain "open for e-business" when the application server has started.
ADMU3000I: Server server1 open for e-business; process id is 12345.
The ps command can be used to ensure the application server is running. In this example, the WebSphere application server is using PID 12345.
~]# ps -ef | grep -i WebSphere root 12345 1 0 Dec13 ? 00:45:50 /opt/IBM/WebSphere/AppServer/. . .
Stop an application server.
~]# /opt/IBM/WebSphere/AppServer/bin/stopServer.sh server_name -profileName profile_name . . . ADMU4000I: Server server_name stop completed.
The ps command can be used to ensure there are no WebSphere processes actively running. In this example, the ps command only returns one line, which is not the WebSphere application server, and instead just the ps command itself.
~]# ps -ef | grep -i WebSphere root 12345 1234 0 18:51 pts/2 00:00:00 grep --color=auto WebSphere
A crontab job can be created to ensure the deployment manager is started when the system is rebooted.
@reboot bash /opt/IBM/WebSphere/AppServer/bin/startServer.sh server_name -profileName profile_name