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

- Previous: Customizing Management Agent Configuration
- Next: Using the hadbm Management Command

## Starting the Management Agent

You can start the management agent two ways:

- As a service, for production use. See Starting the Management Agent as a Service To ensure availability of the management agent, make sure it is restarted automatically when the system reboots. See Ensuring Automatic Restart of the Management Agent.

- As a regular process (in console mode), for evaluation, testing, or development. See Starting the Management Agent in Console Mode.

  In each case, the procedures are different depending on whether you are using Java Enterprise System or the standalone Application Server.

### Starting the Management Agent as a Service

Starting the management agent as a service ensures that it will continue to run until the system shuts down or you explicitly stop it.

#### Starting the Management Agent as a Service with Java Enterprise System on Solaris or Linux

To start the management agent as a service, use this command:

    /etc/init.d/ma-initd start

To stop the service, use this command:

    /etc/init.d/ma-initd stop

#### Starting the Management Agent as a Service with Java Enterprise System on Windows

To start the management agent as a Windows service, use this command: `HADB_install_dir\bin\ma -i [config-file ]`

The optional argument config-file specifies the management agent configuration file. Use a configuration file only if you want to change the default management agent configuration.

To stop the management agent and remove (deregister) it as a service, use the command: `HADB_install_dir\bin\ma -r [config-file ]`

To perform administration, choose Administrative Tools | Services, which enables you to start and stop the service, disable automatic startup, and so on.

#### Starting the Management Agent as a Service with Standalone Application Server on Solaris or Linux

To start the management agent as a service, use this command:

    HADB_install_dir/bin/ma-initd start

To stop the service, use this command:

    HADB_install_dir/bin/ma-initd stop

#### Starting the Management Agent as a Service with Standalone Application Server on Windows

To start the management agent as a Windows service, use this command: `HADB_install_dir\bin\ma -i [config-file ]`

The optional argument config-file specifies the management agent configuration file. Use a configuration file only if you want to change the default management agent configuration.

To stop the management agent and remove (deregister) it as a service, use the command: `HADB_install_dir\bin\ma -r [config-file ]`

To perform administration, choose Administrative Tools | Services, which enables you to start and stop the service, disable automatic startup, and so on.

### 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.

### Starting the Management Agent in Console Mode

You may wish to start the management agent manually in console mode for evaluation or testing. Do not start the management agent this way in a production environment, because the `ma` process will not restart after a system or process failure and will terminate when the command window is closed.

#### Starting management agent in Console Mode with Java Enterprise System on Solaris or Linux

To start the HADB management agent in console mode, use the command:

    opt/SUNWhadb/bin/ma [config-file]

The default management agent configuration file is `/etc/opt/SUNWhadb/mgt.cfg`

To stop the management agent, kill the process or close the shell window.

#### Starting management agent in Console Mode with Java Enterprise System on Windows

To start the management agent in console mode, use the command:

    HADB_install_dir\bin\ma [config-file]

The optional argument config-file is the name of the management agent configuration file. For more information on the configuration file, see Customizing Management Agent Configuration.

To stop the agent, kill the process.

#### Starting management agent in Console mode with Standalone Application Server on Windows

To start the management agent in console mode, use the command:

    HADB_install_dir\bin\ma [config-file]

The optional argument config-file is the name of the management agent configuration file; for more information, see Customizing Management Agent Configuration

To stop the management agent, kill the process.

#### Starting management agent in Console Mode with Standalone Application Server on Solaris or Linux

To start the HADB management agent in console mode, use the command:

    HADB_install_dir/bin/ma [config-file]

The default management agent configuration file is HADB_install_dir `/bin/ma.cfg`

To stop the management agent, kill the process or close the shell window.

- Previous: Customizing Management Agent Configuration
- Next: Using the hadbm Management Command

- © 2010, Oracle Corporation and/or its affiliates