Job Management Partner 1/Performance Management User's Guide

1.2.1 Starting services on the monitoring manager or the monitoring agent

This subsection describes how to start the monitoring manager and monitoring agent services.

Organization of this subsection

(1) Starting services manually

(2) Starting services automatically

(1) Starting services manually

Use the jpcspm start command to manually start services on the monitoring manager or the monitoring agent.

You can use the jpcspm start command to start services only on the host to which you have logged on. You cannot start the Performance Management program services on a remote host. When the health check function is enabled, the health check agent starts when PFM - Manager starts.

To manually start services:
Log on to the host where you want to start services.
Log on to the monitoring manager to start the PFM - Manager services. Log on to the monitoring agent to start the services of PFM-Base and either PFM - Agent or PFM - RM.
Execute the jpcspm start command.
Specify the service key indicating the service that you want to start, and execute the jpcspm start command. Service keys that the jpcspm start command can specify are as follows:

Manager or mgr: PFM - Manager services on the host

AH or act: Action Handler services on the host

For details on the service keys used to start specific PFM - Agent or PFM - RM services on the host, see the appendix describing service naming rules in the manual Job Management Partner 1/Performance Management Planning and Configuration Guide.
For example, to start all of the PFM - Manager, PFM - Base, PFM - Agent, and PFM - RM services on the local host, specify as follows:
 
jpcspm start -key jp1pc
 
Specify the instance name to start, separately instance by instance, a PFM - Agent or PFM - RM that runs in the instance environment.
For example, to start the service that has the instance name oracleA in the PFM - Agent for Oracle, specify as follows:
 
jpcspm start -key Oracle -inst oracleA

(2) Starting services automatically

The following describes procedures for starting services automatically at system startup for each OS.

(a) In Windows

With the default installation settings, services are set to start automatically when the system starts. For this reason, no operation is necessary after starting the system.

Notes:

If services are set to start automatically, the Agent Store service or Remote Monitor Store service might take a longer time to start, and the Agent Collector service or the Remote Monitor Collector service might not start successfully.

The service control manager might output the following message if it takes time to start services of the Performance Management programs when restarting the OS:
Event ID: 7022
Type: Error
Description: <service-name> service hung on starting.
In this case, check if a service start message has been output in the common message log. The service has started normally if a service start message has been output.

Performance Management services are usually operated by using the system account. Changing the settings might cause service operation errors. Do not modify the account settings of a service, unless this manual recommends that you change the settings of that service.
The PFM - Base, PFM - Manager, and PFM - Web Console services are operated by using the all system account.
For details on PFM - Agent, see each of the PFM - Agent manuals.

During OS startup, a factor such as a heavy load might cause the automatic startup of the OS to time out, and Performance Management might fail to start. Therefore, use the jpcspm start command to start the Performance Management system, instead of setting the OS to automatically start services.

(b) In UNIX

To automatically start services at system startup, use the service automatic start script file for the Performance Management system. If you are using AIX, also use the automatic start script file for AIX.

Supplemental information:

By using this script file, you can start services on the physical host only. You cannot start services on the logical host.

If you want only specific services to start automatically, edit the following line in the script file:

Before:

nohup /opt/jp1pc/tools/jpcstart all -nochk 2> /dev/null 1> /dev/null &

After:

nohup /opt/jp1pc/tools/jpcstart act -nochk 2> /dev/null 1> /dev/null

nohup /opt/jp1pc/tools/jpcstart <service-key> -nochk 2> /dev/null 1> /dev/null &

Note: Include the first line only if you need to start the Action Handler service. Do not place an ampersand (&) at the end of the first line. In <service-key> in line 2, specify the service key of the service that you want to start automatically.

To automatically start the PFM - Manager service, edit the following line in the script file:

Before:

nohup /opt/jp1pc/tools/jpcstart all -nochk 2> /dev/null 1> /dev/null &

After:

nohup /opt/jp1pc/tools/jpcstart mgr -nochk 2> /dev/null 1> /dev/null

nohup /opt/jp1pc/tools/jpcstart act -nochk 2> /dev/null 1> /dev/null

nohup /opt/jp1pc/tools/jpcstart <service-key> -nochk 2> /dev/null 1> /dev/null &

Note: Do not place an ampersand (&) at the end of the first and second lines. In <service-key> in line 3, specify the service key of the service that you want to start automatically.

To set automatic start of services:
Log on to the host that you want to set for the automatic start of services.
Log on to the monitoring manager if you are going to operate the PFM - Manager services. Log on to the monitoring agent if you are going to operate the services of PFM-Base and either PFM - Agent or PFM - RM.
Execute the following command to move to the /opt/jp1pc directory:
 
cd /opt/jp1pc
 
Set the service automatic start script file for the Performance Management system.
The names of the .model file of the service automatic start script and the service automatic start script file are as follows:

Name of the .model file of the service automatic start script: jpc_start.model

Name of the service automatic start script file: jpc_start

Copy the .model file of the service automatic start script to the service automatic start script file to add execution permission. Execute the command as follows:
 
cp -p jpc_start.model jpc_start
chmod 555 jpc_start
 
Register the automatic start script file for AIX. (In AIX only)
To execute the automatic service start script file for the Performance Management system specified in step 3, Performance Management provides the automatic start script file for AIX. Register this automatic start script file to the AIX settings file.
Names of the automatic start script file and settings file are as follows:

Name of the automatic start script file: /etc/rc.jp1_pc

Name of the settings file: /etc/inittab

To perform the registration:
1. Use the mkitab command to register the /etc/rc.jp1_pc file to the /etc/inittab settings file.
 
 mkitab "jp1pc:2:wait:/etc/rc.jp1_pc >/dev/console 2>&1"
 
2. Use the lsitab command to confirm that the /etc/rc.jp1_pc file is registered to the /etc/inittab settings file.
 
 lsitab jp1pc
 jp1pc:2:wait:/etc/rc.jp1_pc >/dev/console 2>&1
 
Registering the file by the mkitab command places the file to the bottommost line of the /etc/inittab settings file. If the program that is linked by execution of an action has already been registered to the /etc/initta settings file, it is recommended that you edit the /etc/inittab settings file to place the program after the bottommost line.
Also, the line registered in the /etc/inittab settings file is not deleted upon uninstallation.
To cancel the registration at uninstallation:
1. Use the rmitab command to cancel the registration of the /etc/rc.jp1_pc file from the /etc/inittab settings file.
 rmitab jp1pc
 
2. Use the lsitab command to confirm that the /etc/rc.jp1_pc file is not registered to the /etc/inittab settings file.
 
 lsitab jp1pc

[Contents][Back][Next]

[Trademarks]