12.5.6 Monitoring objects from the Integrated Operation Viewer of JP1/IM2

Suppose that you enable the JP1/IM2 linkage function and display the PFM - Web Console window in the Integrated Operation Viewer of JP1/IM2 or acquire trend information through the REST APIs provided by JP1/IM2. If, under this situation, you perform any of the following operations in a Performance Management environment, you have to apply the IM management node-related information by using the functionality provided by JP1/IM2. For details on how to apply the IM management node-related information, see the JP1/IM2 manual.

• When a connection is made for the first time from PFM - Agent or PFM - RM to PFM - Manager

• When a PFM - Agent, PFM - RM, or remote agent service is deleted

• When PFM - Agent or PFM - RM is upgraded

• When business group information (business group name, resource group name, and the names of the hosts belonging to the business group) is modified

• When a switchover from primary to secondary, or vice versa, is performed (applicable in a multiple-monitoring configuration)

• When the host name, port number, or communication protocol of PFM - Web Console is changed

  This means changing the following properties:

  • JP1 Event Configuration->Monitoring Console Host

  • JP1 Event Configuration->Monitoring Console Port

  • JP1 Event Configuration->Monitoring Console Https

• When the name of the host on which PFM - Manager, PFM - Agent, or PFM - RM has been installed or the name of a monitored host is changed

Note:

• The host from which the Integrated Operation Viewer (Web browser) is being operated must be able to resolve the PFM - Web Console host name set in PFM - Manager.

• If, under a situation where one of the following conditions is satisfied, you attempt to log in to PFM - Web Console, a confirmation message appears, asking if you want to make a forced login:

  - false is set for the enableDuplicateLogin parameter in the configuration that prohibits multiple logins to PFM- Web Console by the same user (initialization file (config.xml)), and you are already logged in to PFM - Web Console.

  - true is set for the informOfSharedSession parameter in the configuration that enables the display of the forced login confirmation window (initialization file (config.xml)), and there is a user on the session who is logged in to PFM - Web Console via the Web browser.

• If you upgrade JP1/IM2, you need to apply the IM management node-related information again by using the functionality provided by JP1/IM2. For details on how to apply the IM management node-related information, see the JP1/IM2 manual.

• The communication protocol set for PFM - Web Console (https or http) must be the same between JP1/IM2 and PFM - Manager. If this setting is different between JP1/IM2 and PFM - Manager, when you select a component of Performance Management in the Operating status area of the Integrated Operation Viewer window of JP1/IM2, the Details area becomes stuck in the loading state, and a PFM - Web Console window never appears.

• If your PFM - Web Console is upgraded from a version earlier than 12-50, it works like when the dispReportsSameTime parameter in the initialization file (config.xml) has the false value as this parameter is undefined. If you want to show the View Report windows opened via monitor startup from a JP1/IM2 event or by the suggestion function of JP1/IM2 together in the same session of your web browser, change the value of the dispReportsSameTime parameter to true as necessary.

• Notes when the dispReportsSameTime parameter in the initialization file (config.xml) is set to true are as follows:

  - When a session for a login user times out, the user is logged out in all web-browser windows that are using the same session according to the specification of the web browser.

  - If you open a View Report window via monitor startup from a JP1/IM2 event or by the suggestion function of JP1/IM2 while you are logged in to PFM - Web Console from the Integrated Operation Viewer of JP1/IM2, additional memory is consumed. Because of this, the system might run out of memory if you open multiple View Report windows via monitor startup or by the suggestion function. For details about the memory space occupied when you open View Report windows via monitor startup or by the suggestion function of JP1/IM2, see the topic describing the amount of memory required per login user for displaying reports via monitor startup of JP1/IM2 in the appendix of the manual JP1/Performance Management Planning and Configuration Guide.

To Page Top