5.1 Overview of Central Scope functions

The Central Scope supports objective-oriented system monitoring based on tree views, map views, and action guidance. You can easily build a Central Scope environment using the auto-generation and editing functions of the Monitoring Tree window.

Important

The Central Scope is disabled (does not run) by default. To use this functionality, you must create a monitoring object database with the jcsdbsetup command, and then enable the Central Scope in the jcoimdef command options.

For details, see the following subsection in the JP1/Integrated Management 3 - Manager Configuration Guide:

• For Windows:

  1.19.5 Specifying settings for using the functions of Central Scope (for Windows)

• For UNIX:

  2.18.7 Specifying settings for using the functions of Central Scope (for UNIX)

Important

The central scope function will be unavailable on January 19, 2038, after which the function will not be available. Therefore, it is necessary to migrate to using the integrated operation viewer before January 19, 2038.

Figure 5‒1: Display examples of the Monitoring Tree window and Visual Monitoring window

The functions of the Central Scope are summarized as follows.

• Monitoring Tree window

  Displays the resources managed by JP1/IM according to the monitoring objectives.

  The monitoring tree shows the monitoring objects monitored by the Central Scope, indicated by icons and arranged in monitoring groups in a tree structure.

  The icons are designed so that you can see, from the inter-relationship of jobs and servers in the tree, which jobs will be affected by a server failure, for example. In the detailed view area, you can view information in map format, like the Visual Monitoring window.

  By using JP1 resource groups, you can control the monitoring range permitted to individual JP1 users, and exercise precise control over access to the nodes in a monitoring tree.

• Auto-generation and editing of a monitoring tree

  A monitoring tree can be easily generated using the auto-generation and editing functions.

  To generate a monitoring tree, you simply select a purpose-built template from the Generation Tree list in the Auto-generation - Select Configuration window. The Central Scope automatically collects definition information from the JP1/IM agents, and creates a monitoring tree based on the template.

  A template consists of model definition information for producing a monitoring tree. Supported monitoring trees include work-oriented trees and server-oriented trees.

  You can edit an automatically generated monitoring tree in the Monitoring Tree (Editing) window to suit your system operation and its requirements. Alternatively, you can output the monitoring tree definitions to a CSV file and then edit them.

• Visual monitoring

  The icons in a monitoring tree can be mapped on a corporate organizational chart or other image in a Visual Monitoring window.

  In addition to the icons provided as standard, you can register images of any size as Visual Icon. Key objects and groups that you particularly want to monitor can be placed on the map. This allows you to easily monitor even a large-scale system from the viewpoints you require.

• Guide information

  You can view guide information relevant to the monitoring nodes and generated JP1 events. Action flows and troubleshooting procedures can be registered as advice for handling problems that might arise during system monitoring, lessening the system administrator's workload at the initial response stage.

  Guide information can be preset by the user. As conditions for determining what information to display, you can specify information about a particular monitoring node or about a JP1 event that triggers a change in the status of a monitoring node.

You can also navigate from the Central Scope's Monitoring Tree window to the Event Console window in the Central Console.

To Page Top