5.11.4 Automatic generation of a monitoring tree
The flow of processing in automatic generation of a monitoring tree when the work-oriented tree or server-oriented tree is selected as the template is described below. The following figure is an example.
|
The flow of processing is described below, following the numbers in the figure:
-
An auto-generation request is sent from a window on the viewer to JP1/IM - Manager on the manager. On receiving the request, JP1/IM - Manager instructs JP1/Base on the manager to collect the monitoring objects (definition information) that will constitute the monitoring tree.
-
On receiving the collection instruction, JP1/Base (definition collection and distribution function) on the manager references the configuration definition (configuration management) information and sends collection requests to JP1/Base on the agents.
-
On receiving the collection request, JP1/Base on each agent requests the linked product (which supports the JP1/Base definition collection and distribution function) on that host to forward the required definition information.
-
On receiving the request, the linked product passes the definition information to JP1/Base on that agent. (This information will be the source data for defining the monitoring objects.)
-
JP1/Base on each agent forwards the transferred definition information to JP1/Base on the manager.
-
JP1/Base on the manager passes the received definition information to JP1/IM - Manager, which re-organizes the data into monitoring objects.
At this point, the definition information is not yet saved to the object database managed by JP1/IM - Manager.
-
JP1/IM - Manager passes the re-organized monitoring object information to JP1/IM - View. The information appears in tree format in the JP1/IM - View windows.
If the generated monitoring tree and objects are adequate for your requirements, you can save them to the manager and immediately begin monitoring from JP1/IM - View. If any adjustments are needed, you can modify the tree configuration and monitoring object definitions, and then save the changes to the manager. (For details about how to modify a monitoring tree, see 5.4 Editing a monitoring tree.)