Here are the instructions to get the servers in a WebSphere cluster to recover automatically. We set these up on a Lotus Connections cluster and now system restarts go much smoother.
Setting up the WebSphere Node Manager as a Windows service
First, you need to set up the Node Manager on each physical server to run as a service and restart after a reboot:
- Open a Command Window and go to the ..\IBM\WebSphere\AppServer\bin directory
- Type in the following command (adjusted for your install paths):
WASService -add "IBM WebSphere Node Agent" -servername nodeagent -profilePath D:\IBM\WebSphere\AppServer\profiles\AppSrv01 -wasHome D:\IBM\Websphere\Appserver -logFile D:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\nodeagent\startNode.log -logRoot D:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\nodeagent -restart true -startType automaticSetting up the member servers to automatically restart
Once the Node Manager is running as a service, you need to set the individual WebSphere servers to automatically restart using the following steps:
- Log in to the Integrated Solutions Console
- Navigate to Servers > Application servers > servername
- Expand Java and Process Management and click on Monitoring Policy
- Change the Node restart state to RUNNING
- Click Apply
- Click Save to save the master configuration
- Repeat for each server in the cluster
WebSphere InfoCenter: WASService Command
WebSphere InfoCenter: Monitoring Policy Settings
WebSphere World forum post on using WASService