5.3.2 Conditions for automatically generating a monitoring tree
You can automatically generate a monitoring tree for JP1 products (JP1/AJS, JP1/Cm2/SSO version 8 or earlier, JP1/PFM, JP1/IM, and JP1/ServerConductor), Cosminexus, and HiRDB. If you wish to monitor any other products in your system, you must set the definition information manually.
The following conditions apply when automatically generating a monitoring tree:
-
JP1/Base (version 7 or later) is required on each agent.
Definition information is collected using JP1/Base functionality.
-
The products to be monitored must support the JP1/Base functionality for collecting definitions.
You must execute the setup command for enabling this functionality in the relevant products on each agent.
-
The service for each linked product must be active during auto-generation.
Definition information cannot be collected from products whose service is inactive.
For the procedures to link these products with JP1/IM, see 6.8 Setting up for linked products in the JP1/Integrated Management 2 - Manager Configuration Guide and the documentation for the relevant linked product.
The following table describes the monitoring objects created by the auto-generation function.
|
Product |
Monitoring node type |
Description |
|---|---|---|
|
JP1/IM - Manager |
IM Monitoring |
Monitors the status of JP1/IM - Manager. Defined so that its status changes conditional on a JP1 event indicating an error in JP1/IM - Manager. |
|
JP1/AJS - Manager |
AJS Monitoring |
Monitors the status of JP1/AJS - Manager and the jobnets executed under its control. Defined so that its status changes conditional on a JP1 event indicating an error in JP1/AJS - Manager or a change in the status of a jobnet. |
|
Jobnet Monitoring (AJS) |
Monitors job execution status. Defined so that its status changes conditional on a JP1 event indicating a change in the status of the job. |
|
|
JP1/Cm2/SSO# |
SSO Monitoring |
Monitoring object that monitors the status of JP1/Cm2/SSO. Defined so that its status changes conditional on a JP1 event indicating an error in JP1/Cm2/SSO. |
|
Category Monitoring (SSO) |
Monitoring object that monitors the status of resource information collected by the SNMP agents managed by JP1/Cm2/SSO. The statuses are collected for all SNMP agents managed by JP1/Cm2/SSO. Defined so that its status changes conditional on a JP1 event indicating a status change in the resources. |
|
|
JP1/PFM - Manager |
Agent Monitoring (PFM) |
Monitors the status of performance data monitored by an agent that is managed by JP1/PFM - Manager. The auto-generation function creates the same number of Agent Monitoring (PFM) objects as the JP1/PFM - Agents managed by JP1/PFM - Manager. Defined so that its status changes conditional on a JP1 event indicating a change in the status of the performance data. |
|
Cosminexus |
Logical Server Monitoring (Cosminexus) |
Monitors the status of a Cosminexus logical server (J2EE server, Web server, naming service, CTM, and so on). Defined so that its status changes conditional on a JP1 event indicating that the Cosminexus logical server has started or stopped, or a JP1 event indicating an execution error. |
|
J2EE Application Monitoring (Cosminexus) |
Monitors the status of a Cosminexus J2EE application. Defined so that its status changes conditional on a JP1 event indicating that the J2EE application has started or stopped, or a JP1 event indicating an execution error. |
|
|
Cosminexus + JP1/Cm2/SSO# |
J2EE Server Resource Monitoring (SSO) |
General monitoring object that monitors the resource status of the Cosminexus J2EE server. Defined so that its status changes conditional on a JP1 event indicating a change in the resource status of the J2EE server. |
|
CTM Resource Monitoring (SSO) |
General monitoring object that monitors the resource status of Cosminexus CTM. Defined so that its status changes conditional on a JP1 event indicating a change in the resource status of CTM. |
|
|
SFO Resource Monitoring (SSO) |
General monitoring object that monitors the resource status of Cosminexus SFO. Defined so that its status changes conditional on a JP1 event indicating a change in the resource status of SFO. |
|
|
J2EE Application Resource Monitoring (Cosminexus) |
General monitoring object that monitors the resource status of the Cosminexus J2EE application. Defined so that its status changes conditional on a JP1 event indicating a change in the resource status of the J2EE application. |
#: JP1/Cm2/SSO version 8 or earlier is required.
- Important
-
Before you begin operation, you should customize the automatically generated monitoring tree to suit the methods you will be using to monitor your system.
A monitoring tree created by the auto-generation function incorporates the collected information in its entirety. It represents the system configuration information as completely as possible, so that the system administrator can delete whatever is unnecessary for monitoring purposes.
For further details about the contents of the automatically generated nodes in a monitoring tree, see Chapter 4. Lists of System-Monitoring Objects (for Central Scope) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.