5.4.1 Editing a monitoring tree

Use the Monitoring Tree (Editing) window to edit a monitoring tree. You can add, delete, and move nodes in this window, according to how the tree is to be used.

To create or edit a monitoring node, you must set the following attributes in the node. All these attributes have been discussed earlier in this chapter.

Table 5‒7: Monitoring node attributes defined in the Monitoring Tree (Editing) window

Attribute	Description
Monitoring node name	The name of the monitoring node.
Monitoring node type	The monitoring group or monitoring object. There are several types of monitoring objects, including system-monitoring objects such as the AJS Monitoring and SSO Monitoring, and general monitoring objects such as a user monitoring object.
Icon	An icon that represents a monitoring node.
Visual Icon	An icon that represents a monitoring node. Visual Icon are displayed only in map views and in the Visual Monitoring window.
Monitoring status	The monitoring status set for a node. The two statuses are Monitor and Do not monitor.
JP1 resource group	Information set for controlling the monitoring range permitted to individual JP1 users, and for exercising precise control over access to the nodes in a monitoring tree. For details about using resource groups, see 5.4.3 Setting the monitoring range of a monitoring tree.
Basic information	Basic information for identifying a monitoring node. In the case of a monitoring group, this attribute is a name identifying the group. For example, you can assign a group name to a group of tasks or servers, such as Daily accounting routines or Database server group, according to the monitoring objectives. In the case of a monitoring object, this attribute is information for identifying the object. For example, you can define a combination of information for identifying the object within the system, such as the jobnet name and a host name. For a system-monitoring object, the same attribute as the basic information of the object to be monitored is defined as an individual condition in the status change conditions.
Status change condition	Status change condition for a monitoring object A condition that determines which received JP1 events will change the status of the monitoring object. This attribute defines a JP1 event that triggers a status change, and the resulting status. Status change condition for a monitoring group A condition that determines what lower-level node statuses will change the status of the monitoring group. The attribute defines the statuses of the lower-level nodes triggering a status change, the resulting status of the monitoring group, and a comparison condition.
Event generation condition	A condition that specifies the status of a monitoring node that will cause a JP1 event to be issued. The issued JP1 event has event ID 00003FB0.

You can create a monitoring group simply by specifying its name (unless you also need to define a status change condition for the group). However, when you create a monitoring object, you must also carefully consider and define what exactly you need to monitor and how this is to be done.

JP1/IM provides a number of system-monitoring objects to facilitate object definition.

The following types of monitoring objects are provided:

• System-monitoring object

  A monitoring object provided by the JP1/IM system. Each product in the JP1 series has its own monitoring object. The basic settings needed for monitoring are pre-defined, so that you can easily set up the monitoring environment.

  System-monitoring objects include a variety of types, such as an AJS Monitoring, SSO Monitoring, and so on. For details about the program products that are monitored by these objects, and how to set them up, 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.

  A system-monitoring object becomes a general monitoring object when edited as follows:

  • By changing the basic information on the Basic Information page of the Properties window

  • By adding, changing, or deleting a status change condition on the Status-Change Condition page of the Properties window

  • By changing a common condition in the Status-Change Condition Settings window

  • By adding, changing, or deleting an individual condition in the Status-Change Condition Settings window

  When you alter a system- monitoring object in any of these ways, a confirmation dialog box appears with the following message: If this operation is continued, the monitoring node type will become User Monitoring Object. Do you want to continue?

• General monitoring object

  An object for general monitoring purposes, created and customized by the user. This type of object is called a User Monitoring Object.

  A general monitoring object can be customized very flexibly, allowing precise settings to match the type of monitoring required. On the other hand, the system administrator needs to be well versed in the settings that can be performed. This type of object also takes time to create.

For most purposes, we recommend that you use system-monitoring objects to create your monitoring nodes, and customize the parts that need to be changed.

To Page Top