Hitachi

JP1 Version 12 JP1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference


4.1.10 Using commands to set up monitoring targets

To use commands to set up monitoring targets:

  1. Create an application definition file.

  2. Create an application.

  3. Bind an alarm table to the monitoring agent.

To collect operation status information on a per-process or per-service basis, specify only a single process or service when creating the application. To collect operation status information on a per-application basis, specify multiple processes or services when creating the application.

The subsections below provide a detailed description of how to set up a monitoring target.

For details about the jpcmkkey, jpcprocdef create, jpcprocdef output, and jpctool alarm bind commands, see the chapter that describes commands in the manual JP1/Performance Management Reference.

The service ID differs depending on various conditions such as the instance name, monitoring target name, and PFM - RM host name. For example, if the instance name is inst1, the monitoring target is targethost1, and the PFM - RM host name is lhost1, the service ID becomes 7A1inst1[targethost1@lhost1]. For details about service IDs, see the section that describes service-naming rules in the appendix of the JP1/Performance Management Planning and Configuration Guide.

Organization of this subsection

(1) Creating an authentication key file

On the host on which PFM - Web Console is installed, create an authentication key file by executing the jpcmkkey command.

This step is not necessary if an authentication key file has already been created.

The following is an example of command execution that creates an authentication key file when ADMINISTRATOR is the user name to be used for login authentication and xxxxx is the password used during execution:

jpcmkkey -user "ADMINISTRATOR" -password "xxxxx"

(2) Creating an application definition file

Describe the conditions necessary for collecting the process operation status information in an application definition file (XML format). The application definition file is used as the parameter file for the jpcprocdef create command during application creation.

Execute this command by logging in to the host on which PFM - Web Console is installed.

If you are creating a new application definition file, you can use the sample shown below as a template.

When PFM - Web Console is running under Windows

PFM - Web-Console-installation-folder\sample\processmonitoringcommand\jpcprocdef-parameters-windows.xml

When PFM - Web Console is running under UNIX

/opt/jp1pcwebcon/sample/processmonitoringcommand/jpcprocdef-parameters-unix.xml

If an application definition already exists and you want to edit its content to create a new application definition, output it by executing the jpcprocdef output command.

Execute this command by logging in to the host on which PFM - Web Console is installed.

Examples of how to specify the jpcprocdef output command are shown below.

To output the application definition to c:\sample.xml when PFM - Web Console is running under Windows:

jpcprocdef output -agent service-ID -name application1 -f c:\sample.xml

To output the application definition to /tmp/sample.xml when PFM - Web Console is running under UNIX:

jpcprocdef output -agent service-ID -name application1 -f /tmp/sample.xml

(3) Creating an application

Specify an application definition file for the -f option and execute the jpcprocdef create command to create an application.

Execute the jpcprocdef create command by logging in to the host on which PFM - Web Console is installed. The jpcprocdef create command creates an application for a single agent. To create an application for multiple agents, repeatedly execute the command using a batch process. Examples of how to specify the jpcprocdef create command are shown below.

When PFM - Web Console is running under Windows and the application definition setting information file is c:\sample.xml

jpcprocdef create -agent service-ID -f c:\sample.xml

When PFM - Web Console is running under UNIX and the application definition setting information file is /tmp/sample.xml

jpcprocdef create -agent service-ID -f /tmp/sample.xml

(4) Binding an alarm table to the monitoring agent

Bind an alarm table for monitoring the operation status information to the monitoring agent by executing the jpctool alarm bind command.

Execute this command by logging in to the host on which PFM - Manager is installed.

The alarm for monitoring the operation status information is called the Application Status alarm. Edit it as needed. For details about this alarm, see Application Status in 6. Monitoring Template.

If an alarm table has already been bound, there is no need to bind it every time you set up a monitoring target.

You can use one of the following two methods to bind an alarm table:

An example of specifying the jpctool alarm bind command for binding the alarm table PFM RM Platform Template Alarms [APP] 09.10 follows:

jpctool alarm bind -key RMPlatform -table "PFM RM Platform Template Alarms [APP] 09.10" -id service-ID -add

An example of specifying the jpctool alarm bind command for binding for binding a user-created alarm table follows:

jpctool alarm bind -key RMPlatform -table user-created-alarm-table-name# -id service-ID -add
#

For user-created-alarm-table-name, you can specify the name of any user-created alarm table.

If you want to monitor the status of a specific process only, you can create an alarm based on conditional expressions. For details about the conditional expression for monitoring only one specific process, see Table 4-2 Conditional expression for monitoring a specific process only in 4.1.2(2) Binding an alarm table to the monitoring agent.