6.6.6 Command-based settings for collecting information about the operating status of processes

This section describes how to execute commands in order to specify settings for collecting information about the operating status of processes.

Settings for collecting information about the operating status of processes can also be specified through the Agents tree of PFM - Web Console, but using commands enables you to use batch processing to automate maintenance and configuration.

Organization of this subsection

(1) Setting user-defined records (monitoring targets)
(2) Deleting a user-defined record (monitoring target)

(1) Setting user-defined records (monitoring targets)

To set a monitoring target:

Create an application definition file.
Create an application.
Bind an alarm table to the monitoring agent.

To collect information about operating status on a per-process or per-service basis, you set only one process or service for the application when you create the application definition file. To collect information about operating status on a per-application basis, you can set more than one process or service for the application when you create the application definition file.

The subsections below provide a more detailed description of how to set monitoring targets.

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 is based on the PFM - Agent host name. For example, if the PFM - Agent host name is pfmhost1, the service ID will be TA1pfmhost1. For details about the service IDs, see the chapter that explains the Performance Management functions in the JP1/Performance Management Planning and Configuration Guide.

(a) Creating a key file for authentication

Create a key file for authentication by executing the jpcmkkey command on the host where PFM - Web Console is installed. This step is not necessary if you have already created a key file.

The following example executes the command to create a key file for authentication, using ADMINISTRATOR as the user name and xxxxx as the password for login authentication:

jpcmkkey -user "ADMINISTRATOR" -password "xxxxx"

(b) Creating an application definition file

The application definition file describes (in XML format) the applicable conditions for collecting information about the operating status of processes. When you create an application, the application definition file is used for the parameters for the jpcprocdef create command.

Log in to the host where PFM - Web Console is installed to execute the jpcprocdef create command. Use one of the following sample files as a starting point for creating a new application definition file.

If PFM - Web Console on Windows: PFM-Web-Console-installation-folder\sample\processmonitoringcommand\jpcprocdef-parameters-windows.xml
If PFM - Web Console on UNIX: /opt/jp1pcwebcon/sample/processmonitoringcommand/jpcprocdef-parameters-unix.xml

To create a new application definition by editing an existing application definition, output it using the jpcprocdef output command.

Log into the host on which PFM - Web Console is installed to execute the jpcprocdef output command. The following are examples of specifying the jpcprocdef output command.

PFM - Web Console on Windows (output to c:\sample.xml): jpcprocdef output -agent service-ID -name application1 -f c:\sample.xml
PFM - Web Console on UNIX (output to /tmp/sample.xml): jpcprocdef output -agent service-ID -name application1 -f /tmp/sample.xml

(c) Creating an application

Execute the jpcprocdef create command with the application definition file specified in the -f option to create the application.

The jpcprocdef create command enables you to create an application for a single agent. To create applications for multiple agents, execute the command repeatedly in a batch process. The following are examples of specifying the jpcprocdef create command.

PFM - Web Console on Windows (application definition settings information file: c:\sample.xml): jpcprocdef create -agent service-ID -f c:\sample.xml
PFM - Web Console on UNIX (application definition settings information file: /tmp/sample.xml): jpcprocdef create -agent service-ID -f /tmp/sample.xml

(d) Binding an alarm table to the monitoring agent

Execute the jpctool alarm bind command to bind an alarm table to the monitoring agent in order to monitor information about operating status.

The alarm for monitoring information about operating status is the Application Status alarm. Edit it as necessary. For details about the Application Status alarm, see Application Status in 7. Monitoring Templates.

If you have already bound the alarm table, you do not need to bind it every time you set a monitoring target.

Binding an alarm table can be done in the following ways:

Bind the alarm table in PFM Windows Template Alarms [APP] 10.00
Bind an alarm table created by the user

The following examples execute the jpctool alarm bind command to bind the alarm table in PFM Windows Template Alarms [APP] 10.00.

PFM - Manager on Windows: jpctool alarm bind -key Windows -table "PFM Windows Template Alarms [APP] 10.00" -id service-ID -add
PFM - Manager on UNIX: jpctool alarm bind -key Windows -table "PFM Windows Template Alarms [APP] 10.00" -id service-ID -add

The following examples execute the jpctool alarm bind command to bind an alarm table created by the user.

PFM - Manager on Windows: jpctool alarm bind -key Windows -table user-created-alarm-table-name^# -id service-ID -add
PFM - Manager on UNIX: jpctool alarm bind -key Windows -table user-created-alarm-table-name^# -id service-ID -add
#: Specify for user-created-alarm-table-name the name of the user-created alarm table.

To monitor the status of a particular process only, you can create an alarm with the condition expressions listed in Table 5-6 Condition expressions for monitoring the status of a particular process only.

To Page Top

(2) Deleting a user-defined record (monitoring target)

To delete a monitoring target:

Check the name of the application definition you want to delete.
Unbind the alarm table.
Delete the application definition.

For details about the commands jpcmkkey, jpcprocdef list, jpctool alarm unbind, and jpcprocdef delete, see the chapter that describes commands in the manual JP1/Performance Management Reference.

The service ID is based on the PFM - Agent host name. For example, if the PFM - Agent host name is pfmhost3, the service ID will be TA1pfmhost3. For details about service IDs, see the chapter that explains the Performance Management functions in the JP1/Performance Management Planning and Configuration Guide.

(a) Creating a key file for authentication

Create a key file for authentication by executing the jpcmkkey command on the host where PFM - Web Console is installed. This step is not necessary if you have already created a key file.

The following example executes the command to create a key file for authentication, using ADMINISTRATOR as the user name and xxxxx as the password for login authentication:

jpcmkkey -user "ADMINISTRATOR" -password "xxxxx"

(b) Checking the name of the application definition you want to delete

Execute the jpcprocdef list command to check the name of the application definition you want to delete from the list of application definitions defined in the monitoring agent.

Log in to the host where PFM - Web Console is installed to execute the jpcprocdef list command. The following is an example of specifying the jpcprocdef list command:

jpcprocdef list -agent service-ID

(c) Unbinding the alarm table

Execute the jpctool alarm unbind command to unbind the alarm table where the monitoring agent is bound and stop monitoring.

Log in to the host where PFM - Manager is installed to execute the jpctool alarm unbind command. For details about the jpctool alarm unbind command, see the chapter that describes commands in the manual JP1/Performance Management Reference.

If the alarm table is already unbound, you do not need to unbind it every time you delete a monitoring target.

The following is an example of specifying the jpctool alarm unbind command to unbind the alarm table in PFM Windows Template Alarms [APP] 10.00:

jpctool alarm unbind -key Windows -table "PFM Windows Template Alarms [APP] 10.00" -id service-ID

(d) Deleting the application definition

Execute the jpcprocdef delete command to delete an application definition.

The jpcprocdef delete command enables you to delete the application definition for a single agent. To delete the application definition for multiple agents, execute the command repeatedly in a batch process.

The following example uses the jpcprocdef delete command to delete the application definition application5:

jpcprocdef delete -agent service-ID -name "application5"

To Page Top