1.2.1 Starting services on the monitoring manager or the monitoring agent

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.

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
```

To Page Top

(2) Starting services automatically

(a) In Windows

With the default installation settings, most services start automatically when the system starts. Note that, however, some services of PFM - Agent for Service Response cannot be set to start automatically. For details, see the chapter that describes starting and stopping services in the manual Job Management Partner 1/Performance Management - Agent Option for Service Response.

If automatic startup processing is affected by high load and times out when the system starts, the Performance Management services might fail to start. In this case, block automatic startup and execute the jpcspm start command to start the services.

Reference note

How to block and reset automatic startup

Log on to the monitoring manager or monitoring agent.
Choose Services in Windows.
In the Services dialog box, choose the Performance Management program service and click Properties from the pull-down menu.
In the service properties dialog box, specify Startup type.

To block automatic startup: Manual

To reset automatic startup: Automatic
Click the OK button.
The service properties dialog box closes.
For details about Performance Management program services, see the explanation of the correspondence between the Performance Management service name and the Windows service name in the Appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Important note

Performance Management services are usually controlled from a system account. Changing the settings might cause service operation errors.

Do not modify the account settings of a service unless recommended to do so by this manual.

All the PFM - Base, PFM - Manager, and PFM - Web Console services are operated by using a system account.

For details on PFM - Agent or PFM - RM, see the respective PFM - Agent or PFM - RM manual.

(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.
In the default settings of the service automatic start script file (jpc_start), all the PFM services on the physical host are set to start up. Therefore, if an instance is not created in a physical environment that has an agent that creates an instance, the KAVE06017-W message is output. 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.

At startup, Performance Management is subject to the LANG environment variable set in the environment where it operates. In an environment where the LC_ALL environment variable is set to a different value from the LANG environment variable, either unset the LC_ALL environment variable or change its value to match the LANG environment variable. Use the following example as a reference when setting the LANG environment variable for Performance Management:

Example settings:

## Set Environment-variables

PATH=/sbin:/bin:/usr/bin:/opt/jp1pc/bin

SHLIB_PATH=/opt/hitachi/common/lib

LD_LIBRARY_PATH=/opt/hitachi/common/lib

LIBPATH=/opt/hitachi/common/lib

HCCLIBCNF=/opt/jp1/hcclibcnf

LANG=LANG-environment-variable-to-set^#1

export PATH SHLIB_PATH LD_LIBRARY_PATH LIBPATH HCCLIBCNF LANG^#1

unset LC_ALL^#2

#1: A line to be added to the script file. For details on the LANG environment variable values you can use with Performance Management, see the chapters on installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide and the manuals for PFM - Agent or PFM - RM.

#2: An example of coding that unsets the LC_ALL environment variable.

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.
- 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.
- Name of the automatic start script file: /etc/rc.jp1_pc
- Name of the settings file: /etc/inittab
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 a program linked by execution of an action is already registered in the /etc/inittab settings file, edit the /etc/inittab settings file so that the reference to the automatic start script file appears below it in the file.

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
```

To Page Top