3.6.1 Introduction
In operation using JP1/IM - Agent, the performance data of various systems collected by JP1/IM - Agent can be managed as trend data of JP1/IM - Manager, and integrated agent host can be understood as an IM managed node.
JP1/IM - Manager of Intelligent Integrated Management Database maintains and manages the following:
-
IM management node Tree Info
-
Integrated agent information (information about integrated agent host and available add-on program)
-
Trend data
-
Response action executions
You can view and manage them from integrated operation viewer (WebGUI). The following tables describe the actions that can be taken during normal configuration and during lower manager configuration.
|
Target of operation |
IM management node Info |
Integrated agent Info |
Operational information |
Suggestions & response action |
|---|---|---|---|---|
|
JP1/Base |
You can view IM management node, and related lines. |
-- |
-- |
It can be set to the target host for executing response action configured in the Integration Manager. |
|
JP1/IM - Agent |
You can view IM management node, and related lines. |
Allows you to view and remove integrated agent info. |
You can view metric list and performance data. |
It can be set to the target host for executing response action configured in the Integration Manager. |
|
Lower manager |
You can view IM management node, and related lines. |
-- |
-- |
It can be specified as the target host for executing response action set in the Integration Manager. Response action and suggestions set for lower manager cannot be operated. |
|
JP1/Base under lower manager |
You can view IM management node, and related lines. |
-- |
-- |
It can be set to the target host for executing response action configured in the Integration Manager. |
|
JP1/IM - Agent under lower manager |
You can view IM management node, and related lines. |
Allows you to view and remove integrated agent info. |
You can view metric list and performance data. |
It can be set to the target host for executing response action configured in the Integration Manager. |
|
Miscellaneous under lower manager |
The file for which the configuration of the Integration Manager is to be acquired must be included. |
-- |
You can view metric list and performance data. |
It can be set to the target host for executing response action configured in the Integration Manager. |
|
Other |
The file for which the configuration of the Integration Manager is to be acquired must be included. |
-- |
You can view metric list and performance data. |
It can be set to the target host for executing response action configured in the Integration Manager. |
- Legend
-
--: Not applicable
It also provides the ability to download/upload manager and agent definition files from integrated operation viewer to change settings, and to generate and reflect IM management node tree data.
- ■Prerequisites
-
To perform the above operations or operation using functions from integrated operation viewer, Intelligent Integrated Management Database must be set up.
- ■Flow and Description of Operations Before Starting Operation Using JP1/IM - Agent
-
During the initial build, WebGUI (integrated operation viewer) registers the required data, sets the definition file, and executes commands.
The following actions create an IM management node and allow integrated operation viewer to initiate integrated administration:
-
Installing and Setting Up JP1/IM - Manager
See 1. Installation and Setup procedures (for Windows) and 2. Installation and Setup (for UNIX) in the JP1/Integrated Management 3 - Manager Configuration Guide.
After running the install and set up commands, you must configure the settings to use JP1/IM - Agent from step 2 onwards.
-
Publish/Get initial secret
Issue and retrieve initial secret. Because initial secret can be acquired only when it is issued, be sure to copy and save initial secret that was issued.
Set initial secret to lower manager status when installing a JP1/IM - Agent, linking with an external system, or configuring multiple stages.
For details, see 3.7 Initial secret and client secret, 1.3.1(3)(a) Information required before installation and 2.3.1(2)(a) Information required before installation in the JP1/Integrated Management 3 - Manager Configuration Guide.
Early communications in JP1/IM agent base use initial secret for Basic authentication, but do not use it after integrated agent has requested a public key download or issued a licensing request. After issuing the request, use agent client secret instead of initial secret.
-
Configuring client secret
Set this option to make the manager host (Intelligent Integrated Management Base) interact with your own OSS.
For details, see 3.7 Initial secret and client secret and see 2.2.4 List of IM Clients window in the JP1/Integrated Management 3 - Manager GUI Reference.
-
Setting lower manager Info (for lower manager configurations)
After installing and setting up lower manager and configuring IM configuration, check lower manager's initial secret and configure lower manager settings.
For details, see 3.7 Initial secret and client secret.
-
Manager definition-file settings (for lower manager configurations)
You can also set the definition file of a host under lower manager from integrated operation viewer if you have access privileges.
-
Setting up integrated agent definition files
-
Use JP1/IM - Agent definition-file manipulation function to configure the settings required for JP1/IM - Agent. The screen used is the same as the settings in the manager's definition file. After the configuration, trend data is collected and RemoteWrite is issued to the Integration Manager.
-
For details, see 3.6.5 Definition file manipulation function.
-
Generating Tree Information
-
Use IM management node creation function.
-
Reflecting Tree Information
-
Use IM management node creation function.
-
IM management node is created, and you can initiate integrated administration in integrated operation viewer.
The following describes how integrated operation viewer operates in the steps above.
Step
Operation screen
User operations
Step 2: Publish and retrieve initial secret
[View initial secret] window
-
Publish initial secret
-
Check the on-screen initial secret
-
Saving an initial secret
Step 3: Configure client secret
[Client Application List] window
-
Checking the stored secret
-
Registering or deleting a secret
Step 4: Configure lower manager Info
[Manage lower manager] window
-
Registering lower manager Info
Step 5: Configure the Manager Definition File
[Manage Definition File] window
-
Checking the manager definition file list
-
You want to check the definition, or download the definition file you want to set or change.
-
Uploading a modified definition file
-
If there is an unnecessary definition file, select the target file in the list and delete it.
Step 6: Configure integrated agent Definition Files
[Manage Definition File] window
-
Checking the list of integrated agent definition files
-
You want to check the definition, or download the definition file you want to set or change.
-
Uploading a modified definition file
-
If there is an unnecessary definition file, select the target file in the list and delete it.
Step 7: Generate Tree Information
[Generate Tree Information] dialog box
-
Performing Tree Information Generation
Step 8: Reflect Tree Information
[Tree Tree Information] Dialog Box
-
Executing Reflection of Tree Information
-
- ■Addition/deletion of agent after operation starts
-
If you add, remove, or change agent settings after starting operation management after initial construction and configuration, you can operate from WebGUI (integrated operation viewer) in the same way as during initial construction. For lower manager configurations, we recommend that you configure lower manager to forward JP1 events of the following event ID to allow the Integration Manager to detect agent additions, deletions, or configuration changes: For details on the settings for forwarding events, see the chapter describing the forwarding JP1 event in the JP1/Base User's Guide.
-
00007630(Add agent)
-
00007631(Removing agent)
-
00007632(Updating agent)
It also provides the ability to remove records about agent from WebGUI from the manager's databases, even if agent is no longer needed to be managed by the manager.
-
- ■Change of operation definition
-
You can use the definition file manipulation function to reconfigure the definition file if the definition needs to be changed even after operation and administration is started.