![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[IBM i]](../images/iseries.gif)
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
To set up this function
on a Linux or supported UNIX operating
system, you must have root authority to edit the inittab file.
![[Windows]](../images/windows.gif)
- Act as part of the operating system
- Log on as a service
The Installation wizard grants you the user rights if your user ID is part of the administrator group.
If you are running on a Microsoft Windows Operating
System, the Installation wizard displays a message that states that
although the advanced user rights are now effective, they do not display
as effective until the next time you log on to the Windows machine.
![[Windows]](../images/windows.gif)
- Click Administrative Tools in the Control Panel.
- Click Local Security Policy.
- Click Local Policies.
- Click User Rights Assignments.
- Right-click Act as part of the operating system.
- Click Security.
- Click Add.
- Click your user ID.
- Click Add.
- Click OK.
- Click OK.
- Right-click Log on as a service.
- Click Security.
- Click Add.
- Click OK.
- Click OK.
- Reboot your machine to make the settings effective.
Consult your Windows help system for
more information.
About this task
- 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
![[Windows]](../images/windows.gif)
- The server1 managed node process, defined as a manually started (versus automatic) service
- The server1 stand-alone Application Server process, defined as a manually started service
- The IBM HTTP Server process and the IBM HTTP Administration process, defined as automatically started services when you choose to install the IBM HTTP Server feature
- The dmgr process on a deployment manager node, defined as a manually started service
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.
On a Linux or supported UNIX operating
system, you must manually create a shell script that automatically
starts any of the processes previously mentioned. Each UNIX shell
script controls a single process, such as a stand-alone product instance.
Multiple stand-alone Application Server processes require multiple
UNIX scripts, which you can define.
In a WebSphere® Application Server, Network Deployment environment,
the addNode or startNode command starts a single unmonitored
node agent only, the nodeagent process, and does not start all of
the processes that you might define on the node. While running, the
node agent monitors and restarts Application Server processes on that
node, on either a Windows or a Linux and UNIX-based platform. Each
Application Server process has MonitoringPolicy configuration settings
that the node agent uses when monitoring and restarting the process.
Use a Windows service. You can install the WebSphere Application Server, Network Deployment product as a Windows service during installation, or at a later time.
Use the WASService command. For more information, see the documentation for the WASService command. As an alternative, you can use the rc.was example shell script.
Supported configurations: On the Red Hat Enterprise Linux Version 6 operating system, do not use the rc.was example shell script. Instead, follow the specific steps in this topic that are related to this operating system.sptcfg
Use the rc.was example shell script that is provided with the appropriate version of the product.
Procedure
Results
![[Windows]](../images/windows.gif)
- Use the net start and net stop commands to control the IBM HTTP Server services on a Windows system. For more information about these commands, see the Windows help file. Access these commands from the Start menu, clicking Start > Programs > IBM HTTP Server.
- Use the Start the Server and Stop the Server commands to control the product process. Access these commands from the Start menu, clicking Start > Programs > IBM WebSphere > Application Server.
- Use the Start the Manager and Stop the Manager commands to control the WebSphere Application Server, Network Deployment dmgr process. Access these commands from the Start menu, clicking Start > Programs > IBM WebSphere > Application Server > Deployment Manager.
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
Return to the Defining application server processes administrative console page to continue.