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]](../../windows.gif)
To set up this function on a Microsoft
® Windows
® operating system, you must belong
to the Administrator group and have the following advanced user rights:
- 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]](../../windows.gif)
You can also add the advanced user rights manually
if you are performing a silent installation on a Windows operating
system. For example, to grant the user rights to your administrator
group user ID on a Windows operating system, perform the following
procedure:
- 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
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
![[Windows]](../../windows.gif)
On
a Windows operating system, you can create Windows services during
installation, using the installation wizard. Each Windows service
controls a single process, such as a stand-alone product instance.
Multiple stand-alone Application Server processes require multiple
Windows services, which you can define. The wizard lets you create
services for these servers:
- 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.
Results
![[Windows]](../../windows.gif)
On a Windows operating system, you can
- 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 V6.
- 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 V6 > 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
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.