3.2.2 Information that is handled as IM management nodes
The following table lists and describes the types of information that are handled as IM management nodes.
|
No. |
Information handled as an IM management node |
Description |
|---|---|---|
|
1 |
System name |
The system name defined in the system node definition file#. A system has a hierarchical structure and can have subsystems. Up to 10 levels can be defined. |
|
2 |
Object root name |
The name of the host, storage, or other item located under a root node or system node. Host names in FQDN format are also supported. |
|
3 |
Category name |
A category name that groups objects to be managed. For details, see Table 3-3 List of categories. |
|
4 |
Sub category name |
The product name. |
|
5 |
Scheduler service name/job group name |
The scheduler service name that are obtained from JP1/AJS - Manager. |
|
6 |
Job group name |
The job group name that are obtained from JP1/AJS - Manager. |
|
7 |
Root jobnet name |
The root jobnet name that exists in the job group obtained from JP1/AJS - Manager. |
|
8 |
Service name for the monitoring agent of JP1/PFM |
The service name of the monitoring agent obtained from JP1/PFM - Manager. It is a management object located at the end of the management nodes under categories No. 2 to 8 in Table 3-3 List of categories. |
|
9 |
Name of the installed product |
The name of an installed product. For a JP1 product, the displayed name can be JP1/Base, JP1/AJS, JP1/PFM, JP1/IM - Manager, or others. |
- #
-
For details about the system node definition file, see System node definition file (imdd_systemnode.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
- Note
-
The Intelligent Integrated Management Base uses actual host names to manage the structure of IM management nodes. Therefore, if you add a product whose host name can have an alias name to the structure of your IM management nodes, you need to map the alias name to the actual host name. When you map the alias name to the actual name, the actual name is displayed as the host name on the tree. As a result, you can group it into the same host on the tree if alias names vary depending on the management tools.
You can map an alias name to an actual host name by defining the alias name corresponding to the actual name in the host name definition file. For details about the host name definition file, see Host name definition file (imdd_host_name.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
The following table lists and describes the categories defined by default.
|
No. |
Category name |
Description |
|---|---|---|
|
1 |
Job |
A category that groups job-related management nodes together. It is created when a host has JP1/AJS - Manager. |
|
2 |
Service Response |
A category that groups together management nodes that monitor the performance of Internet services. It is created when the host monitors JP1/PFM - Agent for Service Response. |
|
3 |
Enterprise |
A category that groups together management nodes that are related to the performance of enterprise systems, such as a SAP system. It is created when the host monitors one of the following products:
|
|
4 |
Transaction Processing |
A category that groups together management nodes for products that monitor transaction processing. It is created when the host monitors one of the following products:
|
|
5 |
Application Server |
A category that groups together management nodes related to performance of application servers. It is created when the host monitors one of the following products:
|
|
6 |
Database |
A category that groups together management nodes related to performance of databases. It is created when the host monitors one of the following products:
|
|
7 |
Platform |
A category that groups together management nodes that monitor performance information of OSs. It is created when the host monitors one of the following products:
|
|
8 |
Virtual Machine |
A category that groups together management nodes that monitor performance information of virtual environments. It is created when the host monitors one of the following products:
|
|
9 |
Management Applications |
A category that groups operations management products together. It is created when JP1/PFM - Manager monitors services for monitoring agents or when the host has JP1/AJS, JP1/PFM - Manager, JP1/PFM - Base, JP1/IM, or JP1/Base. |
|
10 |
Other Applications |
A category that groups together management nodes that are not related to the above categories or user-added categories. It is created when the host is part of an agent configuration or remote monitoring configuration of JP1/IM. |
The following table shows management objects name that underlie the category.
|
No. |
Category name |
Name of the installed product |
Name of the management object underlying the category |
|---|---|---|---|
|
1 |
Job |
JP1/AJS - Manager |
Scheduler service name/job group name |
|
2 |
Service Response |
JP1/PFM - Agent for Service Response |
Abbreviated name of the product |
|
3 |
Enterprise |
JP1/PFM - Agent for Enterprise Applications |
|
|
4 |
JP1/PFM - Agent for Exchange Server |
||
|
5 |
JP1/PFM - Agent for Domino |
||
|
6 |
JP1/PFM - Agent for JP1/AJS3 |
||
|
7 |
Transaction Processing |
JP1/PFM - Agent for OpenTP1 |
|
|
8 |
JP1/PFM - Agent for IBM WebSphereMQ |
||
|
9 |
Application Server |
JP1/PFM - Agent for IIS |
|
|
10 |
JP1/PFM - Agent for WebSphere Application Server |
||
|
11 |
JP1/PFM - Agent for WebLogic Server |
||
|
12 |
JP1/PFM - Agent for Cosminexus |
||
|
13 |
Database |
JP1/PFM - Agent for Oracle |
|
|
14 |
JP1/PFM - RM for Oracle |
||
|
15 |
JP1/PFM-AO for IBM DB2 |
||
|
16 |
JP1/PFM - Agent for Microsoft SQL Server |
||
|
17 |
JP1/PFM - RM for Microsoft SQL Server |
||
|
18 |
JP1/PFM - Agent for HiRDB |
||
|
19 |
Platform |
JP1/PFM - Agent for Platform |
|
|
20 |
JP1/PFM - RM for Platform |
||
|
21 |
Virtual Machine |
JP1/PFM - Agent for VM |
|
|
22 |
JP1/PFM - RM for VM |
||
|
23 |
Management Applications |
Agent products for JP1/PFM |
Abbreviated product name of the monitoring agent |
|
24 |
JP1/PFM - Manager |
JP1/PFM - Manager |
|
|
25 |
JP1/PFM - Base |
JP1/PFM - Base |
|
|
26 |
JP1/AJS - Manager |
JP1/AJS - Manager |
|
|
27 |
JP1/IM - Manager |
JP1/IM - Manager |
|
|
28 |
JP1/Base |
JP1/Base |
|
|
29 |
Other Applications |
JP1/IM - Manager (if it performs remote monitoring) |
JP1/IM - Manager |
|
30 |
JP1/Base |
JP1/Base |
|
|
31 |
-- |
Other |
Users can create categories as they want. For details, see 3.3 Customizing categories.
Note that if a category is defined but has no underlying IM management node at all, it is not shown. Also, if an IM management node cannot be classified into any of the defined categories, it is displayed under the Other Applications category.
- Important
-
When the Integrated Operation Viewer window has not been set up, nothing is displayed in the Operating status area and the Details area of the integrated operation viewer. For details about how to setup the Intelligent Integrated Management Base, see Chapter 4. Setting Up the Intelligent Integrated Management Base in the JP1/Integrated Management 2 - Manager Configuration Guide.