Network management systems can monitor servers in various ways and provide specialized information. Instead of using these separate views of network management systems, consider merging related views so that all information is available in a single view and is correlated for easy interpretation. SCM can correlate network objects to provide a unified view.
Use the SCM to merge similar objects and views into a single view. For example, different applications can provide host data, change management data, trouble tickets, and/or impact data. Correlated views enable you to merge all objects and views into a unified view.
This example scenario combines twoviews into one correlated view that can expose and combine information.
Use SCM to combine two T/EC adapter views into one integrated view that represents objects monitored by both adapters as one correlated object in the new configuration. Figure 11-1 shows the resulting correlated view.
Figure 11-1 Network View: Two Network views are combined into one correlated view.
This scenario uses:
Two Tivoli T/EC adapters that monitor various servers on the network
Many servers are found in both views.
Use SCM to correlate two T/EC adapter views into a unified view:
In the Explorer pane, add an element that is the parent of the new hierarchy.
In this example, the new element is named Correlated T/EC Elements.
Right-click the element, then select> to open the Service Configuration Editor.
Define the Structures for the element by identifying an existing hierarchy that drives the shape of the new tree.
In this example, define two Structures definitions, each with apointing to the element of one of the two T/EC Adapters.
For more information on defining structures, see Section 8.3.2, STEP 2: Define Structures.
To see all elements contained in thehierarchy for both definitions, leave and at O.
Use the default Matching Rule to apply a simple name match to select elements.
For more information on matching rules, see Creating a Matching Rule.
Define the Sources by identifying an existing hierarchy that provides state and information to the elements in the new configuration.
This scenario assumes there is no interest in obtaining state or element information from other sources; it is possible to rely solely on the elements and state information from the T/EC adapters. Therefore, do not create any Source definitions.
For more information on defining sources, see Section 8.3.3, STEP 3: Define Sources.
To defineand policy rules to further define how the configuration is generated and elements are correlated:
In the left pane, expand, then click or .
The right pane updates.
Because state is integrated directly from, in the page, select the and s check boxes.
For more information about Section 8.3.5, STEP 5: Select Generation Options., see
Retain thedefaults to correlate configuration objects using a basic Static Match.
Those objects that are matched are included in the new configuration tree.
For more information about Section 8.3.6, STEP 6: Select Element Correlation Options., see
Clickto save configuration settings.
Clickto generate the new tree.
The new hierarchy generated undercombines the two Tivoli T/EC adapter views into a unified view, as shown:
After the configuration is run and results are verified, create a schedule for the generation of the service configuration on a routine basis.
For an up-to-date view of technology, schedule this configuration to generate every 5 minutes.