Sun Java System Application Server Enterprise Edition 8.1 2005Q2 High Availability Administration Guide

- Previous: Starting the Management Agent as a Service
- Next: Starting the Management Agent in Console Mode

### Ensuring Automatic Restart of the Management Agent

On Windows platforms, once you have started the management agent as a service, use the Windows administrative tools to set the service Startup type to “Automatic,” and the desired Recovery options.

On Solaris and Linux platforms, use the procedures in this section to ensure the availability of the management agent in case the `ma` process fails or the operating system reboots. Doing so is appropriate for a production deployment.

The following procedures ensure the management agent starts only when the system enters:

- Runlevel 3 on Solaris (the default).

- Runlevel 5 on RedHat Linux (the default in graphical mode).

Entering other runlevels stops the management agent.

#### To Configure automatic restart with Java Enterprise System on Solaris or Linux

##### Before You Begin

This section assumes you have a basic understanding of operating system initialization and runlevels. For information on these topics, see your operating system documentation.

1. Ensure that your system has a default runlevel of 3 or 5.

   To check the default runlevel of your system, inspect the file `/etc/inittab` , and look for a line near the top similar to this:

       id:5:initdefault:

   This example shows a default runlevel of 5.

2. Create the following softlinks to the file `/etc/init.d/ma-initd` :

       /etc/rc0.d/K20ma-initd
       /etc/rc1.d/K20ma-initd
       /etc/rc2.d/K20ma-initd
       /etc/rc3.d/S99ma-initd
       /etc/rc5.d/S99ma-initd
       /etc/rcS.d/K20ma-initd

3. Reboot the machine.

##### Next Steps

To deactivate automatic start and stop of the agent, remove the links or change the letters K and S in the link names to lowercase.

#### To Configure automatic restart with Standalone Application Server on Solaris or Linux

1. In a shell, change your current directory to HADB_install_dir `/bin`.

2. Edit the shell script `ma-initd`.

   Make sure the default values of HADB_ROOT and HADB_MA_CFG in the script to reflect your installation:

   - HADB_ROOT is the HADB installation directory, HADB_install_dir.

   - HADB_MA_CFG is the location of the management agent configuration file. For more information, see Customizing Management Agent Configuration

3. Copy `ma-initd` to the directory `/etc/init.d`

4. Create the following soft links to the file `/etc/init.d/ma-initd` :

       /etc/rc0.d/K20ma-initd
       /etc/rc1.d/K20ma-initd
       /etc/rc2.d/K20ma-initd
       /etc/rc3.d/S99ma-initd
       /etc/rc5.d/S99ma-initd
       /etc/rcS.d/K20ma-initd

##### Next Steps

To deactivate automatic start and stop of the agent, remove the links or change the letters K and S in the link names to lowercase.

- Previous: Starting the Management Agent as a Service
- Next: Starting the Management Agent in Console Mode

- © 2010, Oracle Corporation and/or its affiliates