Starting Management Agents

The management agent must be configured and started on all hosts where HADB is deployed. The management agent can be started as :

Use the following procedure to start the management agent on each machine that hosts the HADB:

  1. Edit the management agent configuration file (optional).
  2. A sample management agent configuration file, called mgt.cfg, is installed in HADB_install_dir/lib/ directory. If you have not installed HADB in the default location, edit the mgt.cfg file to enter appropriate values that match your environment.


    Note

    When specifying paths for the Windows platform as property values (in the mgt.cfg file or on the command line), ensure that:

    • Paths containing spaces are escaped with double quotes (").
    • The drive and directory separators, : and \, are escaped with double quotes and a backslash: "\:" and "\\".

    The configuration file, mgt.cfg, is useful for custom deployments, and can be re-used on all hosts within the same domain. The following table provides the entries available in the management agent configuration file.

    Table 0-2  Sample Configuration File Entries

    Variable

    Type

    Default

    Values

    console.loglevel

    String

    WARNING

    SEVERE, ERROR, WARNING, INFO

    logfile.loglevel

    String

    INFO

    SEVERE, ERROR, WARNING, INFO

    logfile.name

    String

    C:\Sun\SUNWhadb\ma\ma.log

    Agent log file location: A valid path with read/write access.

    ma.server.type

    String

    jmxmp

    Client protocol. Currently, only JMXMP supported.

    ma.server.jmxmp.port

    int

    1862

    Port number for internal (UDP) + external (TCP) communication. Range: 1024-63000.

    ma.server.mainternal.interfaces

    String

    None

    Select interface(s) for internal communication. Needed when running on machines with multiple interfaces.

    ma.server.dbdevicepath

    String

    C:\Sun\SUNWhadb

    Path to store HADB device information.

    ma.server.dbhistorypath

    String

    C:\Sun\SUNWhadb

    Path to store HADB history (textual log) files.

    ma.server.dbconfigpath

    String

    C:\Sun\SUNWhadbbdef

    Path where node configuration data is stored,

  3. Start the management agent.
  4. On Unix platform:
  5. ma [-i|-r|-s] [-n name] [COMMON-OPTIONS] [AGENT-CONFIG]
  6. On Windows platform:
  7. ma.exe [-i|-r|-s] [-n name] [COMMON-OPTIONS] [AGENT-CONFIG]

The ma command takes the options described in the following table.

  1. Optionally, start the management agent as a service.
  2. On Unix platform:
    1. Use the ma-initd script.
    2. Hardlink the ma-initd script located in the HADB_install_dir/bin directory to /etc/init.d. This allows the management agent to be started or stopped manually.
    1. The management agents can now be start/stopped with the following command:
  3. On Windows platform:

The following table identifies the options available with the management agent.

Table 0-3   Management Agent Options

Option

Description

Type/Value-ranges

Default

--version
-V

Prints the version details of the management agent and exit

boolean

FALSE

--javahome
-j

Path to Java Runtime Environment to use for the agent (Version 1.4 or later).

Pathname

None

--define
-D

Property value assignment for an agent property defined in "". Can be repeated.

String

None

--systemroot
-y

Path to the operating system root as normally set in %SystemRoot%.

 

 

--service
-s

Runs the agent in Windows service manger compliant mode.

boolean

FALSE

--name
-n

Use this name for the service (when running multiple agents on a host).

String

HADBMgmtAgent

--install
-i

Installs the agent as a Windows service and starts the service.

boolean

FALSE

--remove
-r

Stops the service and deletes the agent from the Windows service manger.

boolean

FALSE

--help
-?

Prints brief description about the management agent.

boolean

FALSE


Legal Notices