Hitachi

JP1 Version 12 JP1/Performance Management User's Guide


12.3.2 Setup for linking with JP1/IM (settings for using JP1/IM to monitor events that occurred in Performance Management)

If the name of the Performance Management monitoring host differs from its actual host name, the monitoring host name must be added to the JP1/IM host information file (jcs_hosts). After editing the file, use the following procedure to apply the changes:

  1. Import the host information.

    jcshostsimport -o (host-information-file)

  2. Reload JP1/IM.

    jco_spmd_reload

For details on the host information file and JP1/IM commands, see the JP1/Integrated Management 2 - Manager Overview and System Design Guide or the manual JP1/Integrated Management 2 - Manager Command and Definition File Reference.

The table below shows the procedure for specifying the settings required for using JP1/IM to monitor events that occurred in Performance Management. The required settings depend on the JP1 event type used and the extent of linkage between Performance Management and JP1/IM.

Table 12‒9: Procedure for specifying the settings required for using JP1/IM to monitor events that occurred in Performance Management

No.

Procedure

Refer to:

Necessity for setting

JP1 system event

JP1 user event

1

Configuration for issuing JP1 events

In the PFM - Web Console, set up the configuration so that JP1 events are issued when a monitored event occurs in JP1/IM.

12.3.2(1)

Required

Required

12.3.2(2)

Optional (set if necessary)

Optional (set if necessary)

2

Defining alarm events and reports

Define alarm events to be monitored in JP1/IM and operation reports in the PFM - Web Console.

12.3.2(3)

Required

Required

3

Setting for linking with JP1/IM Central Console

Edit the definition files required in JP1/IM - Manager, and then store them under a directory for JP1/IM.

12.3.2(4)(a)

None required#1

Required

4

Setting for linking with the Tool Launcher window of JP1/IM#2

Edit the definition files required in JP1/IM - View, and then store them under a directory for JP1/IM.

12.3.2(4)(b)

Required if linking

Required if linking

5

Setting for linking with the JP1/IM Central Scope#3

Execute the command for linkage with the monitored object (jpcconf im command).

12.3.2(5)

Required if linking

Required if linking

6

Specifying whether the messages of JP1 user events are enclosed in quotes

In UNIX, specify whether JP1 user event messages are enclosed in quotes.

12.3.2(6)

Unavailable

Optional (Set if not using quotation mark)

7

Setting for linking with JP1/IM2

Execute the command for linkage with the JP1/IM2 (jpcconf im2 command).

12.3.2(7)

Required if linking

--

Legend:

--: Not applicable

#1

For a JP1 system event, you do not need to edit or copy the definition file, even when linking with JP1/IM Central Console.

#2

You must complete no. 3 in the table (setting for linking with JP1/IM Central Console) before you can configure Performance Management to link with the JP1/IM Tool Launcher.

#3

You must complete no. 3 in the table (setting for linking with JP1/IM Central Console) before you can configure Performance Management to link with the JP1/IM Central Scope.

Note:

Linkage with the system-monitored object for Performance Management in JP1/IM is required in order to enable monitoring with the Central Scope. For details on settings and operations of JP1/IM, see the JP1/Integrated Management 2 - Manager Overview and System Design Guide and JP1/Integrated Management 2 - Manager Configuration Guide.

This subsection describes the setup procedures for linking with JP1/IM.

Organization of this subsection

(1) Configuring so that JP1 events are issued

To configure the setting:

  1. From the monitoring console Web browser, log on to PFM - Web Console.

    Log on to a user account that has administrator user permissions.

    You must have administrator user permissions to use the Services window.

  2. In the navigation frame of the main window, select the Services tab.

  3. In the navigation frame of the Services window, choose the service to be set.

    The selected service is marked with a checkmark.

    The following table lists the events that trigger JP1 system events and the properties to be set for each target service.

  4. Set the property values appropriate for the JP1 event you want to issue.

    The following table lists the JP1 events to be issued and the properties to be set for each target service.

    Table 12‒10: JP1 events to be issued and properties to be set for each target service

    Event to be issued

    Services that trigger events

    Properties to be set

    Setting procedure location

    Events related to the operation of, or a change in the status of, PFM services

    (Event IDs of JP1 system events: 00004800 to 00004830)

    PFM - Manager services

    • Name Server

    • Master Manager

    • Master Store

    • Correlator

    • Trap Generator

    • View Server

    JP1 Event Configurations node for Master Manager

    12.3.2(1)(a)

    PFM - Agent and PFM - RM services

    • Agent Collector and Remote Monitor Collector

    • Agent Store or Remote Monitor Store

      These services are used instance by instance (for multi-instance agents).

    JP1 Event Configurations node for Agent Collector or Remote Monitor Collector

    Status Server service#2

    • Status Server

    JP1 Event Configurations node for Master Manager, Agent Collector, Remote Monitor Collector, or Action Handler#1

    Action Handler service

    • Action Handler

    Event related to a change in agent status

    (Event ID of JP1 system event: 00004850)#3

    PFM - Agent and PFM - RM services

    • Agent Collector or Remote Monitor Collector

    • Agent Store or Remote Monitor Store

      These services are used instance by instance (for multi-instance agents).

    JP1 Event Configurations node for Agent Collector or Remote Monitor Collector

    Alarm event (JP1 system event issued for alarms)

    (Event ID of JP1 system event: 00004840)

    --

    Alarm node under JP1 Event Configurations for Master Manager, Agent Collector, Remote Monitor Collector, or Action Handler on the host that has the Action Handler service specified for executing actions in response to alarms

    12.3.2(1)(b)

    Events related to suspending or resuming monitoring

    (Event IDs of JP1 system events: 00004870, 00004871, 00004880, 00004881)

    --

    System node under JP1 Event Configurations for Master Manager

    12.3.2(1)(c)

    Events related to a change in the health check status

    (Event ID of JP1 system event: 00004860)

    --

    Health Check Configurations node of Health check Agent Collector

    12.3.2(1)(d)

    Legend:

    --: Not applicable

    #1

    Use the same value for the listed services on the same host.

    #2

    The Status Server service does not appear as a service on a logical host.

    #3

    If you want to link with JP1/IM2 in an environment where JP1/Base has not been installed on the PFM - Agent host or the PFM - RM host, execute the JP1/IM2 linkage command (jpcconf im2 command) with the function for batch-issuing events that change agent status enabled so that JP1 system events can be issued.

    If JP1/Base has been installed on the PFM - Agent host and the PFM - RM host, you can enable the issuance of JP1 system events by following step 4. If you perform step 4, do not perform the step described here.

    The following table describes the recommended setting for (whether to enable or disable) the function for batch-issuing events that change agent status based on whether JP1/Base has been installed on the PFM - Agent host and the PFM - RM host.

    Table 12‒11: Recommended setting for the function for batch-issuing events that change agent status

    JP1 event issuance setting for Agent Collector services and Remote Monitor Collector services

    Recommended setting for the function for batch-issuing events that change agent status

    None of services issue JP1 events.

    Enabled

    All services issue JP1 events.

    Disabled

    Note:

    Enabling both the JP1 event issuance setting for Agent Collector services and Remote Monitor Collector services and the function for batch-issuing events that change agent status causes two JP1 events to be issued to notify when the status of an agent changes. To avoid this, if some Agent Collector services or Remote Monitor Collector services have the JP1 event issuance setting enabled, you must change the services so that all services in the system have the same setting (either of the settings described in the table above).

  5. When linking with JP1/IM2, execute the JP1/IM2 linkage command (jpcconf im2 command) to enable JP1/IM2 linkage.

    For details on how to execute the JP1/IM2 linkage command, see 12.3.2(7) Setting for linking with JP1/IM2.

(a) Configuring the issuing of JP1 system events by individual PFM services

  1. Select the JP1 Event Configurations node.

    At the bottom of the information frame, the properties of the JP1 Event Configurations node are displayed.

  2. Select the service for which you want JP1 system events to be issued, and then set the following property value:

    Service for which events are issued: Yes

(b) Configuring the issuing of JP1 system events by alarms

  1. Select the Alarm node under the JP1 Event Configurations node.

    At the bottom of the information frame, the properties of the Alarm node are displayed.

  2. Set the properties to the following:

    Specify a JP1 event type to be associated if an alarm event occurs.

    JP1 Event Mode

    To use a JP1 system event: JP1 System Event

    To use a JP1 user event: JP1 User Event

(c) Configuring the issuing of JP1 system events for suspending or resuming monitoring

  1. Select the System node under the JP1 Event Configurations node.

    At the bottom of the information frame, the properties of the System node are displayed.

  2. Set the properties to the following:

    Monitoring Suspend

    Specify whether to issue a JP1 system event when monitoring is suspended or resumed. The default value is No.

    To issue a JP1 system event: Yes

    To issue a JP1 system event only in the primary system in a multiple monitoring environment: Yes(Primary)

    To issue no JP1 system event: NO

(d) Configuring events related to a change in health check status

  1. Select the Health Check Configurations node.

    The bottom of the information frame displays the properties of the Health Check Configurations node.

  2. Set the properties to the following:

    JP1 Event: Yes

(2) Configuring options for JP1 system events

  1. From the Web browser of the monitoring console, log on to PFM - Web Console.

    Log on with a user account that has administrator user permissions.

    You must have administrator user permissions to use the Services window.

  2. In the navigation frame of the Main window, select the Services tab.

  3. For Master Manager, Agent Collector, Remote Monitor Collector, or Action Handler, select the JP1 Event Configurations node.

    Master Manager, Agent Collector, Remote Monitor Collector, and Action Handler use the same property value for the services on the same host.

    JP1 Event Send Host

    Specify the name of an event server connected to JP1/Base using 255 or less alphanumeric characters. You can only specify an event server running on the same logical or physical host as the Performance Management service that issues the JP1 events. You cannot specify an IP address. Any preceding or trailing spaces in the specified value are ignored.

    If you specify an out-of-range value or if no value is specified, a physical host is used as the event-issuing host.

    The default value is blank.

    If a logical host is configured and the event related to the change of health check status (JP1 system event with event ID 00004860) is set, select the Health Check Configurations node for the health check Agent Collector service. Then, set the following property:

    JP1 Event - Send Host Mode: JP1 Event Send Host Value

    Monitoring Console Host

    To start the PFM - Web Console, specify the name of the PFM - Web Console host in the JP1/IM - Manager monitor startup function. In addition, to link to JP1/IM2, this property of the PFM - Manager host must be specified.

    Specify the name with 255 or less alphanumeric characters. You cannot specify an IP address. Any preceding or trailing spaces in the specified value are ignored.

    If an out-of-range value is specified or if no value is specified, the name of the PFM - Manager for the connection destination of PFM - Agent Console is assumed.

    The default value is blank.

    Monitoring Console Port

    Specify the port number (http request port number) for the PFM - Web Console to be started. In addition, to link to JP1/IM2, this property of the PFM - Manager host must be specified.

    If no value is specified, the value 20358 is assumed.

    The default value is blank.

    Monitoring Console Https

    If JP1/IM - Manager's monitor startup feature is used to start PFM - Web Console, specify whether encrypted communication using https is to be used to connect to PFM - Web Console. In addition, to link to JP1/IM2, this property of the PFM - Manager host must be specified.

    The default value is No.

(3) Associating alarms with JP1 events and reports

In the Alarms window of PFM - Web Console, set up the following items:

For details on the definition of alarms, see 6. Monitoring Operations with Alarms.

The following procedure mainly describes operations for setting up JP1 events to be issued and for associating alarms with reports.

  1. Log on to PFM - Web Console as a user with administrator user permissions.

  2. In the navigation frame of the Main window, select the Alarms tab.

  3. In the navigation frame of the Alarms window, select the alarm definition for which you want to issue JP1 events.

    The selected alarm is marked with a checkmark.

  4. Choose the Edit method in the method frame.

  5. In the Edit > Main Information window in the information frame, click the Next button.

  6. In the Edit > Action window, enter settings in the Actions to be executed area.

    In Command, select conditions (Abnormal, Warning, or Normal) of the alarm for which you want to issue JP1 events.

  7. In Report to be displayed, click the Browse button to select the report to be associated with the alarm.

    The selected report is marked with a checkmark.

  8. Click the Finish button.

  9. Click the Next button.

  10. In the Command definition area of the Edit > Action Definitions window, click the JP1 Event button.

  11. In the New Alarm > Action Definitions > JP1 Event Settings window, set the event ID and other information.

    For example, suppose you want to send the JP1 event under the following conditions:

    Conditions:

    • Set the event ID to 001.

    • Set the message text to the content of the message text (%MTS), which you set in the Message of the New Alarm Table > Main Information dialog box.

    • Convert the alarm status to a severity-level JP1 event.

    Set as follows:

    Event ID: 001

    Message: %MTS

    Convert the alarm level to the severity level: Selected

    Note:

    Do not modify the attributes of the JP1 event if you want to link with the JP1/IM monitoring objects.

    For a JP1 system event, the information set for Event ID is output as an event ID (JPC_USER_EVENTID) identifying an extended JP1 event attribute. For a JP1 user event, the information is output as an event ID for a basic JP1 event attribute.

    For details on JP1 event types, see 12.2 JP1 events issued from Performance Management to JP1/IM.

  12. Click the OK button.

    The issuing of the JP1 event is defined as an alarm action, and the selected report is associated. For details on the issued JP1 events, see 12.6 List of attributes of JP1 events issued when linking with JP1/IM.

  13. Select the Action Handler service of the host that issues the JP1 event.

    When you enter settings in the JP1 Event Settings window, the setting in Action handler changes automatically. By default, the Action Handler service on the PFM - Manager host is selected. If you want to issue the JP1 event on a host other than the PFM - Manager host, you must modify the setting in Action handler.

    Note 1

    To issue a JP1 event, JP1/Base must be installed on the same host as the Action Handler that issues the event.

    Note 2

    To issue a JP1 event during Performance Management monitoring using the JP1/IM Central Scope, you must select an Action Handler service running on the same host as PFM - Manager.

    Note 3

    You can change which host's Action Handler service is selected by setting the selectAHModeForJP1Event parameter in the initialization file (config.xml). For details on how to enter settings in the initialization file (config.xml), see the section describing the file in the appendixes of the manual JP1/Performance Management Reference.

    If you want to issue the JP1 event on a host other than the automatically selected host, you must modify the setting in Action handler manually.

  14. When you want to issue a JP1 event to a logical host in a logical host environment, add the -r logical-host-name option to Command arguments.

    If you do not specify this option, JP1 events are registered in the physical host.

  15. Click the Finish button.

(4) Editing and copying the definition files for linkage

In order to enable monitoring of JP1 events by using JP1/IM, you need to edit the JP1/IM definition files that are provided by Performance Management according to the environment and to copy the files to each of the corresponding JP1/IM directories.

Tip
  • You might need to restart JP1/IM to enable the editing of definition files in JP1/IM. For details on restart timings of the definition files and timing when the definition files take effect, see the JP1/Integrated Management 2 - Manager Overview and System Design Guide, JP1/Integrated Management 2 - Manager Configuration Guide, and the manual JP1/Integrated Management 2 - Manager Command and Definition File Reference.

  • If the source and destination hosts for the copied JP1/IM definition files are running different operating systems and one of those operating systems is Linux, change the encoding of the target definition files by using, for example, a text editor or the nkf command. The resulting encoding must be as follows:

    If the operating system to which JP1/IM definition files are copied is Linux:

    UTF-8

    If the operating system from which JP1/IM definition files are copied is Linux:

    Shift JIS or EUC

The JP1/IM definition file provided by Performance Management is stored in the following folder:

(a) Definition files required in JP1/IM - Manager

When you use monitoring with the Central Console to issue a JP1 user event, you must edit and copy the definition file required by JP1/IM - Manager. This is not necessary when you use monitoring with the integrated console to issue a JP1 system event.

  • Definition file for the extended event attributes

This file defines the extended event attributes of JP1 events.

File name:

hitachi_jp1_pfmwebcon_attr_language-codes.conf

Items to edit:

Change the order id value to the event ID set by the JP1 event-issuing command. To display reports from JP1/IM, you also need to set the specified event ID in the definition file for opening monitor windows.

For example, specify the following when the event ID is 00001234:

[Figure]

Copy destination

Copy the edited definition file for the extended event attributes to the directory on the host that has JP1/IM - Manager installed as listed below:

For physical hosts:
  • In Windows:

    installation-folder-for-jp1/im-manager\JP1Cons\conf\console\attribute\

  • In UNIX:

    /etc/opt/jp1cons/conf/console/attribute/

For logical hosts:
  • In Windows:

    shared-folder\jp1cons\conf\console\attribute\

  • In UNIX:

    shared-directory/jp1cons/conf/console/attribute/

For details, see the JP1/Integrated Management 2 - Manager Overview and System Design Guide, JP1/Integrated Management 2 - Manager Configuration Guide, and the manual JP1/Integrated Management 2 - Manager Command and Definition File Reference.

  • Definition file for opening monitor windows

    This file defines settings for opening monitor windows. The definition file for opening monitor windows is used to open a monitor window, such as one for the event-issuing source, from the event console window of JP1/IM - View. You need to enter settings in this file if you want to display a View Report window in PFM - Web Console when a JP1 event occurs.

File name:

hitachi_jp1_pfmwebcon_mon_language-codes.conf

Items to edit:

Change the value of the EVENT_ID to the event ID set with the JP1 event-issuing command. Also, change the communication protocol, host name, and port number in PATH to those of PFM - Web Console. Note that the specified event ID needs to be set in the definition file for the extended event attributes.

For example, if 00001234, http, PFM-WebCon, and 20358 are assigned to the event ID, communication protocol, host name, and port number, respectively, specify as follow:

[Figure]

Copy destination

Copy the edited definition file for opening monitor windows to the directory on the host that has JP1/IM - Manager installed as listed below:

For physical hosts:
  • In Windows:

    installation-folder-for-jp1/im-manager\JP1Cons\conf\console\monitor\

  • In UNIX:

    /etc/opt/jp1cons/conf/console/monitor/

For logical hosts:
  • In Windows:

    shared-folder\jp1cons\conf\console\monitor\

  • In UNIX:

    shared-directory/jp1cons/conf/console/monitor/

For details, see the JP1/Integrated Management 2 - Manager Overview and System Design Guide, JP1/Integrated Management 2 - Manager Configuration Guide, and the manual JP1/Integrated Management 2 - Manager Command and Definition File Reference.

  • Example of displaying View Report windows in PFM - Web Console for several instances of PFM - Manager

    Note

    A PFM - Web Console instance is required for each PFM - Manager instance. For example, if there are two PFM - Manager instances, there must be two PFM - Web Console instances.

You need to use different event IDs to display View Report windows in PFM - Web Console for multiple PFM - Managers.

For example, if 00000000 and 00001111 are assigned to the event IDs, specify the definition file for the extended event attributes and the definition file for opening monitor windows as follows:

Definition file for the extended event attributes:

[Figure]

Definition file for opening monitor windows:

[Figure]

In the example above, the event ID 00000000 corresponds to PFM - Web Console host name PFM-Webcon1 and port number 8080. Similarly, the event ID 00001111 corresponds to PFM - Web Console host name PFM-Webcon2 and port number 20358.

(b) Definition files required in JP1/IM - View

  • Definition file for the tool launcher

The definition file for the tool launcher defines the tree structure and display items to be displayed in the Tool Launcher window in JP1/IM - View. You need to set the definition file for the tool launcher to enable the window of PFM - Web Console to be displayed from the Tool Launcher window.

File name

hitachi_jp1_pfmwebcon_tree.conf

Items to edit

Also, change the communication protocol, host name, and port number in arguments to those of PFM - Web Console.

For example, if http, PFM-WebCon, and 20358 are assigned to the communication protocol, host name, and port number, respectively, specify as follow:

[Figure]

Copy destination

Copy the edited definition file for the tool launcher to the folder on the host that has JP1/IM - View installed, as follows:

installation-folder-for-JP1/IM - View\conf\function\language-codes\

  • Example: Windows of PFM - Web Console are started respectively by differing hosts

    You need to define blocks within the definition file for the tool launcher corresponding to respective PFM - Web Console to enable differing hosts to start windows of PFM - Web Console respectively. For details, see the JP1/Integrated Management 2 - Manager Overview and System Design Guide, JP1/Integrated Management 2 - Manager Configuration Guide, and the manual JP1/Integrated Management 2 - Manager Command and Definition File Reference.

    The following provides an example of setting the definition file for the tool launcher and an example of the Tool Launcher window display.

    [Figure]

    In the examples above, double-clicking Server Availability Management 1 in the Tool Launcher window connects the program to PFM - Web Console with the host name of PFM - WebCon1 and port number 20358, and then starts the corresponding window of PFM - Web Console. Similarly, double-clicking Server Availability Management 2 in the Tool Launcher window connects the program to PFM - Web Console with the host name of PFM - WebCon2 and port number 32222, and then starts the corresponding window of PFM - Web Console.

(5) Using icons to monitor the system operating status by linking with the JP1/IM monitored object function

If you want to use icons to monitor the operating status of the system in Performance Management by linking with the monitored object function of JP1/IM, you need to execute the jpcconf im command on the PFM - Manager host and then automatically generate the monitoring tree. This step is required for JP1/IM to collect definition information from Performance Management. In a cluster environment, the logical host names of PFM - Manager and JP1/Base must be the same.

  1. Execute the jpcconf im command on the PFM - Manager host.

    Execute the jpcconf im command on the PFM - Manager host as shown below to start linkage with JP1/IM:

    jpcconf im enable

    Execute the command as shown below to stop linkage with JP1/IM:

    jpcconf im disable

    If PFM - Manager is in a logical host environment, execute the command one time on both the active and standby nodes.

  2. In the JP1/IM Central Scope, automatically generate the monitoring tree.

    For details on how to do so, see the JP1/Integrated Management 2 - Manager Overview and System Design Guide, the JP1/Integrated Management 2 - Manager Configuration Guide, and the manual JP1/Integrated Management 2 - Manager Command and Definition File Reference.

(6) Setting quotation marks enclosing a JP1 user event message

For UNIX, a JP1 user event message can be enclosed in double quotation marks ("). To enclose such a message in double quotation marks, directly edit the jpccomm.ini file, which is located on the host running the Action Handler server that executes the action. To specify whether the messages of JP1 user events are enclosed in quotes:

  1. Stop the Action Handler service to be configured.

    For the logical host environment, stop the Action Handler services of the logical host.

  2. Edit the jpccomm.ini file.

    The jpccomm.ini file is stored in the following locations:

    On physical hosts:

    /opt/jp1pc/

    On logical hosts:

    environment-directory/jp1pc/

    The following table describes the section name, label name, and range of setting values that you can edit in the jpccomm.ini file.

    Table 12‒12: Setting item for specifying whether the messages of JP1 user events are enclosed in quotes

    Section

    Label name

    Value range

    Default value

    Description

    [Common Section]

    JP1 Event Double Quote

    0 | 1

    1

    Specify whether the messages of JP1 user events are enclosed in quotes.

    0: Do not enclose in quotes

    1: Enclose in quotes

    This label is available only for UNIX. In Windows, the setting of the label is ignored.

  3. Start the Action Handler service that has been configured.

(7) Setting for linking with JP1/IM2

You can set linkage with JP1/IM2 as follows:

  1. Specify the following settings so that the JP1/IM2 can communicate with PFM - Web Console.

    • Set up the firewall so that the JP1/IM - Manager host can access the PFM - Web Console host through the PFM - Web Console port number (20358 by default).

    • Expand the memory space occupied by PFM - Web Console.

      Expand the maximum memory size used by the PFM - Web Console services from 1,024 MB to 1,536 MB. For details, see the section in Appendix that describes how to expand the PFM - Web Console memory in the JP1/Performance Management Planning and Configuration Guide.

  2. Execute the following command to enable the JP1/IM2 linkage function:

    jpcconf im2 enable

    To disable the function for batch-issuing events that change agent status, specify the -eventcompat option.

    If you are using this function in a cluster environment, execute the command in both the executing and standby nodes.

    In a multiple-monitoring configuration, execute this command in both the primary and secondary systems.

  3. Start the Performance Management services.

  4. On PFM - Web Console, enable the issuance of JP1 events by health check agents.

    Upon the reception of JP1 events from Performance Management, the JP1/IM2 updates the status of configuration information for the sources that issued the JP1 events.

    If the PFM - Web Console host is different from the PFM - Manager host, set the name of the PFM - Web Console host# in the following property.

    Services window->Master Manager->JP1 Event Configurations->Monitoring Console Host

    #

    Set the host name that can be resolved by the JP1/IM - Manager host.

    If the port number to be used by PFM - Web Console has been set to a value other than the default 20358, set the new port number in the following property.

    Services window->Master Manager->JP1 Event Configurations->Monitoring Console Port

    If encrypted communication is enabled for the PFM - Web Console, specify Yes for the following property.

    Services window->Master Manager->JP1 Event Configurations->Monitoring Console Https

  5. Enable PFM - RM polling.

    In the PFM - RM property in the Services tree, set Yes for the Health Check for Target Hosts property of Health Check Configurations.

  6. On PFM - Web Console, enable the issuance of agent events for all Agent Collector services within the Performance Management system.

    This setting is not necessary if you are enabling the function for batch-issuing events that change agent status.#

    #

    Note the following when the function for batch-issuing events that change agent status is enabled:

    - The connection-target PFM - Manager's host name and IP address are set as the source event server name and source IP address attributes, respectively, of a JP1 event. This means that you can check information regarding a monitored host whose status has changed by referring to the source host name attribute of the JP1 event.

    - No message is output to Performance Management's common message log if a JP1 event was sent successfully to notify of the status change of an agent. The KAVE00577-E message is output if such a JP1 event could not be sent.

    - After PFM - Manager restarts, only when an alarm event occurs for the first time since the restart, the alarm event occurrence causes a JP1 event to be issued to notify of the status change of the agent regardless of whether the status of the agent is changed.

  7. If you want to edit, delete, or add a new one to default metrics that you can display or acquire through the trend information display function or the metric list acquisition API provided by JP1/IM2, you have to edit the metric definition file. (This is applicable when linkage is established with JP1/IM2 12-10 or later.)

    For details on the metric definition file, see the chapter describing the metric definition file in the manual JP1/Performance Management Reference.

  8. If you want to change the default operation of the JP1/PFM plug-in, you have to edit the JP1/PFM plug-in configuration file. (This is applicable when linkage is established with JP1/IM2 12-10 or later.)

    For details on the JP1/PFM plug-in configuration file, see the chapter describing the JP1/PFM plug-in configuration file in the manual JP1/Performance Management Reference.

  9. To acquire performance data of Performance Management by the getting performance information API of JP1/IM2, enable the accumulation of performance data for applicable records.

  10. If you want to display or acquire performance data of Performance Management through either the trend information display function or the time-series data acquisition API provided by JP1/IM2, you have to enable the accumulation of performance data for the applicable records. (This is applicable when linkage is established with JP1/IM2 12-10 or later.)