Automatically restarting server processes

There are several server processes that the operating system can monitor and automatically restart when the server processes stop abnormally.

Before you begin

The Installation wizard grants you the user rights if your user ID is part of the administrator group.

About this task

There are several environments where you might use this function of automatically restarting servers. You can restart the server1 managed node process, for example. Here is a list of processes you might consider restarting:
  • The server1 managed node process
  • The server1 process on a stand-alone Application Server
  • The dmgr process on a deployment manager node
  • The nodeagent server process on any managed node
  • The IBM® HTTP Server process
  • The IBM HTTP Administration process

The installation wizard does not provide a way to create a service for a node agent because the deployment manager instantiates each node agent after installation when you add an Application Server node to the deployment manager cell. For this reason, you must manually create a function that automatically starts a failed node agent server process.

It is recommended that you manually set up a monitored process for the deployment manager dmgr server and for any node agent defined for your system. To set up a monitored process:

Procedure

  1. In the administrative console, click Servers > Server Types > WebSphere application servers > server_name > Process. Start the administrative console. In the topology tree, expand Servers and click Application Servers. Click the name of the application server that you want to start automatically. Click Process Definition. Click Monitoring Policy. Change the Node Restart state to RUNNING. Click Apply. Save the configuration.
  2. Select the application server that you want to automatically restart and then, under Server Infrastructure , click Java and process management > Monitoring Policy.
  3. Select Automatic restart.
  4. Click Apply and then click Save to save the change directly to the master configuration.

Results

Processes started by a startServer command, a startNode command, or a startManagercommand are not running as monitored processes, regardless of how they are configured.

For example, you can configure a server1 process as a monitored process. However, if you start the server1 process using the startServer command, the operating system does not monitor or restart the server1 process because the operating system did not originally start the process as a monitored process.

What to do next

After the process is set up, the operating system can monitor each server process and restart the process if it stops.

Return to the Defining application server processes administrative console page to continue.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 5:30:17 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=trunprocessrestart
File name: trun_processrestart.html