Starting the Management Agent
You can start the management agent:
-
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.
-
With the service management facility (SMF) on Solaris 10. See Running the Management Agent with the Solaris 10 Service Management Facility.
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. The command depends on your installation and platform:
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
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. For more information, see Customizing 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.
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
To change the default values, edit the shell script HADB_install_dir/bin/ma-initd . Copy ma-initd to the directory /etc/init.d. Replace 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
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
In a production deployment, configure the management agent to restart automatically. Doing so ensures the availability of the management agent in case the ma process fails or the operating system reboots.
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 then set desired Recovery options.
On Solaris and Linux platforms, use the procedures in this section, to configure automatic restart of the management agent. These 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.
-
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.
-
Create soft links to the file /etc/init.d/ma-initd, as described in Creating soft links.
-
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
-
In a shell, change your current directory to HADB_install_dir /bin.
-
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
-
-
Copy ma-initd to the directory /etc/init.d
-
Create soft links to the file /etc/init.d/ma-initd, as described in Creating soft links.
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.
Creating soft links
On Solaris, create the following softlinks:
/etc/rc0.d/K20ma-initd /etc/rc1.d/K20ma-initd /etc/rc2.d/K20ma-initd /etc/rc3.d/S99ma-initd /etc/rc5.d/K20ma-initd (only for Sun 4m and 4u architecture) /etc/rc6.d/K20ma-initd /etc/rcS.d/K20ma-initd
On Linux, create the following softlinks:
/etc/rc0.d/K20ma-initd /etc/rc1.d/K20ma-initd /etc/rc3.d/S99ma-initd /etc/rc5.d/S99ma-initd /etc/rc6.d/K20ma-initd
Starting the Management Agent in Console Mode
You may wish to start the management agent 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. The command depends on your platform and installation:
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.
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.
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.
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.
Running the Management Agent with the Solaris 10 Service Management Facility
Service Management Facility (SMF) provides mechanisms to restart, view, and manage services on Solaris 10. You can use SMF to start, restart, and manage the HADB management agent.
The fault management resource identifier (FMRI) for the management agent is svc:/application/hadb-ma.
- © 2010, Oracle Corporation and/or its affiliates