Job Management Partner 1/Performance Management User's Guide

1.8.1 When starting PFM - Agent or PFM - RM in a large-scale system

When starting Performance Management, normally you start PFM - Manager first, and then PFM - Base and either PFM - Agent or PFM - RM. In a large-scale system consisting of multiple servers, normally you start the system by controlling the sequence in which services are started among these servers.

You can still collect the performance data by starting PFM - Base and either PFM - Agent or PFM - RM first even when the Master Manager service and the Name Server service of PFM - Manager are not running.

The stand-alone mode refers to when PFM - Agent and PFM - Base or PFM - RM and PFM - Base operate separately.

The modes of the system are designated depending on the state of each program as follows:

Only PFM - Agent, PFM - RM, or PFM - Base is running.
This is called stand-alone mode.

Initially PFM - Manager is running together with PFM - Agent, PFM -RM, or PFM - Base. Then PFM - Manager is stopped, so that only PFM - Base, PFM - Agent, or PFM - RM is running.
This is called non stand-alone mode.

PFM - Manager, PFM - Base, and either PFM - Agent or PFM - RM have started in this sequence and are all running.
This is called normal mode.

Note:

PFM - Agent or PFM - RM cannot start by itself when PFM - Agent or PFM - RM is installed on the same host as PFM - Manager.

Organization of this subsection

(1) Overview of stand-alone mode

(2) Functions available in stand-alone mode

(3) Commands available in stand-alone mode

(4) Overview of non stand-alone mode

(5) Functions available in non stand-alone mode

(6) Commands available in non stand-alone mode

(1) Overview of stand-alone mode

If the Master Manager services and Name Server services of PFM - Manager have not been started, PFM - Agent, PFM - RM, or PFM - Base start in stand-alone mode to collect the performance data.

The system checks the connection to PFM - Manager once every 5 minutes in stand-alone mode. If PFM - Manager starts after PFM - Agent, PFM - RM, or PFM - Base have already started in stand-alone mode, and PFM-Manager performs a successful connection check with one of those programs, that program switches from stand-alone mode to normal mode connected to PFM - Manager. At this time, you can consult history reports to check the performance data stored in PFM - Agent or PFM - RM during stand-alone mode.

However, there are partial restrictions on the functionality and executable commands of Performance Management when PFM - Agent and PFM - Base or PFM - RM and PFM - Base run in stand-alone mode.

(2) Functions available in stand-alone mode

The following table describes the availability of functions in stand-alone mode operation.

Table 1-3 Functions available in stand-alone mode

Function Availability Service name

Starting and stopping services, and checking operation status Y

In PFM-Agent host
Agent Store, Agent Collector, and Action Handler

In PFM-RM host
Remote Monitor Store, Remote Monitor Collector, and Action Handler

Collecting history data Y

In PFM-Agent host
Agent Store and Agent Collector

In PFM-RM host
Remote Monitor Store and Remote Monitor Collector

Displaying reports and connecting from ODBC-compliant application programs N Agent Store and Remote Monitor Store

Issuing alarms that indicate agent start Y Agent Collector and Remote Monitor Collector

Monitoring the performance data by alarms N Agent Collector and Remote Monitor Collector

Executing actions in response to alarm events N Action Handler

Service status management Y Status Server

Legend:

Y: Available

N: Not available

Function	Availability	Service name
Starting and stopping services, and checking operation status	Y	In PFM-Agent host Agent Store, Agent Collector, and Action Handler In PFM-RM host Remote Monitor Store, Remote Monitor Collector, and Action Handler
Collecting history data	Y	In PFM-Agent host Agent Store and Agent Collector In PFM-RM host Remote Monitor Store and Remote Monitor Collector
Displaying reports and connecting from ODBC-compliant application programs	N	Agent Store and Remote Monitor Store
Issuing alarms that indicate agent start	Y	Agent Collector and Remote Monitor Collector
Monitoring the performance data by alarms	N	Agent Collector and Remote Monitor Collector
Executing actions in response to alarm events	N	Action Handler
Service status management	Y	Status Server

(3) Commands available in stand-alone mode

The following table describes the availability of commands in stand-alone mode operation.

Table 1-4 Commands available in stand-alone mode

Command Function Availability

jpcconf db define Changing the directory settings of the Agent Store service and the Remote Monitor Store service Y

jpcconf db display Displaying information about the Agent Store service, the Remote Monitor Store service, or backup data Y

jpcconf db vrset Changing the version of the Store database Y

jpcconf hc Enabling or disabling the health check function Y

jpcconf stat Enabling or disabling the status management function Y

jpcras Collecting troubleshooting data of PFM - Manager, PFM - Agent, or PFM - RM Y

jpcspm start Starting services Y

jpcspm stop Stopping services Y

jpctool db backup Creating backup files of the data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service Y^#

jpctool db clear Deleting data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service N

jpctool db dmconvert Converting the data model of backup data Y

jpctool db dump Exporting data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service Y^#

jpctool db import Importing backup data Y

jpctool service delete Deleting service information of the agents registered in Performance Management N

jpctool service list (when other host is specified by the -host option) Displaying the structure and status of the Performance Management program services N

jpctool service list (when the -host option is not used) Checking the status of service operations on the local host Y

jpctool service register Re-registering service information of the Performance Management program N

Legend:

Y: Available

N: Not available

#

You can execute commands only when specifying the -alone option.

Command	Function	Availability
jpcconf db define	Changing the directory settings of the Agent Store service and the Remote Monitor Store service	Y
jpcconf db display	Displaying information about the Agent Store service, the Remote Monitor Store service, or backup data	Y
jpcconf db vrset	Changing the version of the Store database	Y
jpcconf hc	Enabling or disabling the health check function	Y
jpcconf stat	Enabling or disabling the status management function	Y
jpcras	Collecting troubleshooting data of PFM - Manager, PFM - Agent, or PFM - RM	Y
jpcspm start	Starting services	Y
jpcspm stop	Stopping services	Y
jpctool db backup	Creating backup files of the data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service	Y^#
jpctool db clear	Deleting data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service	N
jpctool db dmconvert	Converting the data model of backup data	Y
jpctool db dump	Exporting data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service	Y^#
jpctool db import	Importing backup data	Y
jpctool service delete	Deleting service information of the agents registered in Performance Management	N
jpctool service list (when other host is specified by the -host option)	Displaying the structure and status of the Performance Management program services	N
jpctool service list (when the -host option is not used)	Checking the status of service operations on the local host	Y
jpctool service register	Re-registering service information of the Performance Management program	N

(4) Overview of non stand-alone mode

Initially PFM - Manager runs together with PFM - Agent, PFM - RM or PFM - Base. Then PFM - Manager is stopped, so that only PFM - Base, PFM - Agent or PFM - RM is running. This is called non stand-alone mode.

Unlike stand-alone mode, the system does not check the connection to PFM - Manager once every 5 minutes in non stand-alone mode. When PFM - Manager starts and communicates with PFM - Agent or PFM - RM (for example, to display a report), the system reconnects and switches to normal mode. At this time, you can consult history reports to check the performance data stored in PFM - Agent or PFM - RM during non stand-alone mode.

Figure 1-4 Overview of non stand-alone mode

Notes:

Alarm events cannot be reported to PFM - Manager when PFM - Agent or PFM - RM runs in non stand-alone mode. In such cases, the system holds alarm events by each alarm definition, and continues to attempt to report the alarm event until PFM - Manager starts. The oldest alarm event is overwritten when more than three alarm events are retained. All the retained alarm events are deleted when PFM - Agent or PFM - RM stops.

The system resets the alarm events reported to the PFM - Manager when PFM - Manager starts. After that, the status of the alarm events is checked with PFM - Agent or PFM - RM, and the alarm events are reported to the PFM - Manager again.

An alarm flashing in red in the browser display returns to green immediately after PFM - Manager starts, and then returns to flashing red.

(5) Functions available in non stand-alone mode

The following table describes the availability of functions in non stand-alone mode operation.

Table 1-5 Functions available in non stand-alone mode

Function Availability Service name

Starting and stopping services, and checking operation status Y

In PFM-Agent host
Agent Store, Agent Collector, and Action Handler

In PFM-RM host
Remote Monitor Store, Remote Monitor Collector, and Action Handler

Collecting history data Y

In PFM-Agent host
Agent Store and Agent Collector

In PFM-RM host
Remote Monitor Store and Remote Monitor Collector

Displaying reports and connecting from ODBC-compliant application programs N Agent Store and Remote Monitor Store

Monitoring the performance data by alarms Y Agent Collector and Remote Monitor Collector

Executing actions in response to alarm events N^# Action Handler

Service status management Y Status Server

Legend:

Y: Available

N: Not available

#

The system operates differently according to the following conditions:

If you specify LOCAL for the Action Handler services and no action has been executed.
No action is executed while PFM - Manager is stopped.
Even when PFM - Manager restarts, any action that was generated while PFM - Manager was stopped is not executed.

If you specify LOCAL for the Action Handler services, at least one action has been executed, but the Action Handler service executing the action has not restarted.
The action is executed even while PFM - Manager is stopped.

If you specify something other than LOCAL for the Action Handler services.
No actions are executed while PFM - Manager is stopped.
After PFM - Manager starts, any actions that were generated while PFM - Manager was stopped are executed. Actions cannot be executed correctly if the Action Handler service of the PFM - Manager host is specified.

Function	Availability	Service name
Starting and stopping services, and checking operation status	Y	In PFM-Agent host Agent Store, Agent Collector, and Action Handler In PFM-RM host Remote Monitor Store, Remote Monitor Collector, and Action Handler
Collecting history data	Y	In PFM-Agent host Agent Store and Agent Collector In PFM-RM host Remote Monitor Store and Remote Monitor Collector
Displaying reports and connecting from ODBC-compliant application programs	N	Agent Store and Remote Monitor Store
Monitoring the performance data by alarms	Y	Agent Collector and Remote Monitor Collector
Executing actions in response to alarm events	N^#	Action Handler
Service status management	Y	Status Server

(6) Commands available in non stand-alone mode

The following table describes the availability of commands in non stand-alone mode operation.

Table 1-6 Commands available in non stand-alone mode

Command Function Availability

jpcconf db define Changing the directory settings of the Agent Store service or the Remote Monitor Store service Y

jpcconf db display Displaying information about the Agent Store service, the Remote Monitor Store service, or backup data Y

jpcconf db vrset Changing the version of the Store database Y

jpcconf hc Enabling or disabling the health check function Y

jpcconf stat Enabling or disabling the status management function Y

jpcras Collecting troubleshooting data of PFM - Manager, PFM - Agent, or PFM - RM Y

jpcspm start Starting services Y

jpcspm stop Stopping services Y

jpctool db backup Creating backup files of the data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service Y^#

jpctool db clear Deleting data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service N

jpctool db dmconvert Converting the data model of backup data Y

jpctool db dump Exporting data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service Y^#

jpctool db import Importing backup data Y

jpctool service delete Deleting service information of the agents registered in Performance Management N

jpctool service list (when other host is specified by the -host option) Displaying the structure and status of the Performance Management program services N

jpctool service list (when the -host option is not used) Checking the status of service operations on the local host Y

jpctool service register Re-registering service information of the Performance Management program N

Legend:

Y: Available

N: Not available

#

You can execute commands only when specifying the -alone option.

Command	Function	Availability
jpcconf db define	Changing the directory settings of the Agent Store service or the Remote Monitor Store service	Y
jpcconf db display	Displaying information about the Agent Store service, the Remote Monitor Store service, or backup data	Y
jpcconf db vrset	Changing the version of the Store database	Y
jpcconf hc	Enabling or disabling the health check function	Y
jpcconf stat	Enabling or disabling the status management function	Y
jpcras	Collecting troubleshooting data of PFM - Manager, PFM - Agent, or PFM - RM	Y
jpcspm start	Starting services	Y
jpcspm stop	Stopping services	Y
jpctool db backup	Creating backup files of the data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service	Y^#
jpctool db clear	Deleting data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service	N
jpctool db dmconvert	Converting the data model of backup data	Y
jpctool db dump	Exporting data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service	Y^#
jpctool db import	Importing backup data	Y
jpctool service delete	Deleting service information of the agents registered in Performance Management	N
jpctool service list (when other host is specified by the -host option)	Displaying the structure and status of the Performance Management program services	N
jpctool service list (when the -host option is not used)	Checking the status of service operations on the local host	Y
jpctool service register	Re-registering service information of the Performance Management program	N

[Contents][Back][Next]

[Trademarks]