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.
Procedure
On a Windows
operating system, Use the installation wizard to set up a Windows
service to automatically monitor and restart processes related to
the product.
Perform the following procedure from the installation wizard
to select services that the installation wizard can set up:
- Click Run WebSphere® Application Server as
a service.
If you select this option, the installation wizard
creates the following service during the installation:
IBMWAS6Service - node_name
The IBMWAS6Service
- node_name service controls the node_name process.
After
you complete and verify the installation, use the Windows Services
panel to change the
IBMWAS6Service - node_name service
to an automatic startup type.
- Right click IBMWAS6Service - node_name and click Properties.
- Click Automatic from the Startup type list box and
click OK.
- Click Run IBM HTTP Server as a service.
Select this option
on the machine where you are installing the IBM HTTP Server.
If
you select this option, the installation wizard creates the following
services during the installation:
- IBM HTTP Server 2.0.x
- IBM HTTP Administration 2.0.x
The installation wizard defines the startup type of these services
as
automatic. It is not necessary for you to change the type
from manual to automatic.
- Enter your user ID and password and click Next.
In a coexistence environment, you can change the default
service names to make them unique. In a same version coexistence scenario
for IBM HTTP Server 2.0.x on a Windows platform, you cannot use the
default service names created by the installer because they are common.
To
work around this problem:
- Install the first copy of IBM HTTP Server, either by itself or
with the product and select to install the services.
- Customize the service names for the first install by running the
following commands from the first install location:
apache -k install -n "IHS 2.0(1)"
apache -k install -f conf\admin.conf -n "IHS 2.0 Administration (1)"
- Edit the AdminAlias directive in the installLocation 1\conf\admin.conf file
to point to the new service name, such as IHS 2.0(1).
- Remove the default service names installed by the first install
by running the following commands:
apache -k uninstall -n "IBM HTTP Server 2.0"
apache -k uninstall -n "IBM HTTP Administration 2.0"
- Install the second copy of IBM HTTP Server, either by itself or
with the product. The default service names correspond to the second
install.
Note: Customized service names must be unique
on your system.
On a Linux or supported
UNIX operating system, after you install the product, set up a shell
script to automatically monitor and restart any related server processes.
- Locate the rc.was example shell
script, which is in the app_server_root/bin directory.
- Create a new shell script for each process that the
operating system is to monitor and restart.
- Edit each shell script according to comments in its
header, which provide instructions for identifying a product process.
- Edit the inittab file of the operating system, to add
an entry for each shell script you have created.
Comments
in the header of the rc.was file include a sample
inittab entry line for adding this script to the inittab table. Each
inittab entry causes the operating system to call the specified shell
script whenever the system initializes. As each shell script runs,
it monitors and starts the server process you specified.
For
example, if you create the following inittab entry for a process,
the rc.was shell script is run whenever the system initializes, and
if the process goes down while the system is initializing into a machine
that is operating at a runlevel of 2, 3, or 5:
was:235:respawn:/usr/WebSphere/AppServer/bin/rc.was >/dev/console 2>&1
If
you create the following inittab entry, the rc.was shell script only
runs once when you initialize into a machine that is operating at
a runlevel of 2,3, or 5:
was:235:once:/usr/WebSphere/AppServer/bin/rc.was >/dev/console 2>&1
Following
is a list of the runlevels that can be specified. Runlevels usually
default to either 3 or 5.
- 0-halt
- 1-Single user mode
- 2-Multiuser, without NFS (The same as 3, if you don't have networking)
- 3-Full multiuser mode
- 4-unused
- 5-X11
- 6-Reboot
If you don't know the runlevel into which your machine
is booting, look at the following line in the inittab file:
id:x:initdefault
where x is
the runlevel that the machine is booting into.
For example,
if your machine is booting into a runlevel of 5, then all of the processes
that are declared to run with a runlevel of 5 are started.
Avoid trouble: Everything that is ran from the inittab
file runs under the root user. Therefore, if you need the server to
automatically start the process under a non-root user ID when the
machine starts, you must also add the following line to the inittab
file:
su user -c values
where values is
the file path and arguments that are used to call the rc scripts you
created, and user is the non-root user that you have configured
the product to run as.
gotcha
Each shell script monitors and
restarts an WebSphere Application Server, Express server
process.
On a Windows operating
system, after installing the product, you can use the WASService.exe
command in the app_server_root\bin directory
to manually define a Windows service for another installation instance
or for another configuration instance of the server1 process.
- Click and
then click to
save the change directly to the master configuration.
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.
Processes started by a startServercommand
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.