12.3.1 Prerequisites for installation when linking with JP1/IM
- Organization of this subsection
(1) When linking with JP1/IM
The following prerequisite conditions for linking with JP1/IM must be satisfied:.
-
The PFM - Manager host must have JP1/Base installed in order to log on to Performance Management as a JP1 user. Use JP1/Base to manage users.
-
JP1/Base on the PFM - Manager host must be configured as an object to be managed by JP1/IM - Manager.
-
To start PFM - Web Console from JP1/IM View, the JP1/IM - View host must have a Web browser installed.
-
Performance Management 08-00 or later and an earlier version of Performance Management cannot be set up at the same time when establishing linkage with JP1/IM.
-
The JP1 authentication mode must be used to display reports from the JP1/IM Central Console.
- Note:
-
If Performance Management earlier than 08-00 is used for setting up the JP1/IM linkage function, you need to perform unsetup of the JP1/IM linkage function of the earlier version (previous to 08-00) and then set up the JP1/IM linkage function using version 08-00 or later again.
-
To display a report about the host on which the problem occurred from a JP1 event displayed in the JP1/IM Central Console, the following conditions must be satisfied:
-
If the OS of a monitored host is UNIX, the actual host name is used as the monitoring host name in Performance Management. The result of the uname -n command must match the result of the hostname command. If it does not, take either of the following actions:
Change the method for acquiring the host name to hostname.
Configure the environment of the monitored host so that the hostname command and the uname -n command produce the same output.
-
The name of the event server that issues a JP1 event must match the name of the monitoring host in Performance Management. Names are case sensitive.
-
When a JP1 event is issued, JP1/PFM - Agent or JP1/PFM - RM must be monitoring the host on which the problem occurred.
To display an OS performance report about a job execution host, PFM - Agent for Platform or PFM - RM for Platform must be monitoring the host.
-
The following product versions are required.
No.
Product name
Version
1
JP1/Integrated Management or JP1/ Integrated Management 2
JP1/IM - Manager
11-10 or later
2
JP1/IM -View
11-10 or later
3
JP1/Base
JP1/Base
11-00 or later#
4
JP1/Performance Management
PFM - Web Console
11-10 or later#
-
The following figure shows the installation configuration:
(2) When linking with JP1/IM2
The following conditions must be satisfied to establish a link with JP1/IM2.
-
The following table describes the prerequisite versions of PFM - Manager, PFM - Web Console, and JP1/IM2 for each JP1/IM2 linkage function.
Table 12‒8: Prerequisite versions for each JP1/IM2 linkage function Function
Prerequisite version
PFM - Manager
PFM - Web Console
JP1/IM2
-
JP1/IM2 linkage command (jpcconf im2 command)
-
Synchronization of configuration information
-
Mapping of JP1 events with IM management nodes
-
REST APIs provided by JP1/IM2
- The getting performance information API
12-00 or later
12-00 or later
-
Display of related nodes
-
Display of trend information
-
Display of properties
-
REST APIs provided by JP1/IM2
- Metric list acquisition API
- Time-series data acquisition API
12-10 or later
Display of the operating status of the objects monitored by Performance Management through the PFM - Web Console window integrated with the Integrated Operation Viewer
12-00 or later
12-10 or later
12-10 or later
-
Display of suggestion information and execution of response actions
-
REST APIs provided by JP1/IM2
- Response action retrieval API
- Response action execution API
12-50 or later#
12-10 or later
12-50 or later
JP1/PFM plugin functions available in the suggestion definition file
-
jp1pfmSuggestionCreateReportURL
-
jp1pfmSuggestionGetAgentAllInformation
-
jp1pfmSuggestionGetAgentInformation
-
jp1pfmSuggestionGetHostName
-
jp1pfmSuggestionGetPerformanceEvents
-
jp1pfmSuggestionSetStatusOfEventsToProcessed
12-00 or later
12-00 or later
12-50 or later
-
jp1pfmSuggestionExecManagerCmd
-
jp1pfmSuggestionGetAlarmStatus
-
jp1pfmSuggestionGetAllAlarmStatuses
-
jp1pfmSuggestionGetCurrentlyNormalEvents
12-50 or later#
Display of Performance Management reports in the PFM - Web Console window opened by monitor startup from an event on JP1/IM2 or by the suggestion function of JP1/IM2
12-50 or later
- #
-
The PFM - Manager host requires JP1/Base version 12-10 or later.
If you use the suggestion function of JP1/IM2 in use case 1 of Performance Management, the monitored host requires PFM - Agent for Platform (of any version).
-
-
Any versions of PFM - Base and the agent product may be used.
-
JP1/Base 10-10 or later is required in the PFM - Manager host. If PFM - Manager is on a logical host, the logical host name of PFM - Manager and that of JP1/Base must be the same.
-
To install JP1/Base on the PFM - Agent host and the PFM - RM host, you need to use a version of JP1/Base that can issue JP1 events.
-
If you are not installing JP1/Base on the PFM - Agent host or the PFM - RM host, you have to enable the issuance of JP1 system events (event ID: 00004850) that notify changes in agent status by executing the JP1/IM2 linkage command (jpcconf im2 command) with the function for batch-issuing events that change agent status enabled.
Note that, if you want to disable the function for batch-issuing events that change agent status in your environment, you have to install JP1/Base on the PFM - Agent host and the PFM - RM host.
-
The JP1/IM2 is necessary as the manager hosts of JP1/IM.
-
The JP1 authentication mode must be used.
-
The following functions must be enabled for Performance Management:
-
Status management function
-
Health check function
-
-
If the system configuration includes PFM - RM, the following function must be enabled:
-
Settings for PFM - RM polling#
- #
-
Under the Health Check Configurations folder of PFM - RM, specify Yes for the Health Check for Target Hosts property.
-
-
To link multiple PFM - Manager instances to one JP1/IM2 instance, the host names of the monitoring managers, monitoring agents, and monitoring targets must be unique. To ensure the uniqueness, you can set aliases for un-unique host names, except for monitoring managers. Ensure that monitoring managers have unique real host names, instead of setting aliases.
Before you can set aliases, you must configure JP1/IM2 so that it can accept aliases.
For details about the installation configuration to be used when linking with JP1/IM2 and how to configure JP1/IM2 to accept aliases, see the JP1/IM2 manual.