OEM User's Guide

Custom Views
OEM User’s Guide—520330-001
5-2
Hierarchical and Object-based Display of Data
values of underlying objects within that view only, and not within the OEM object
database as a whole.
For example, suppose the objects \Chicago\Disk\$System and \Chicago\Disk\$Data are
added to the OEM object database, $System with a state of 6 and $Data with a state of 4.
Within the OEM database and standard Alerts displays, \Chicago\Disk reflects the
highest state of any subordinate object – in this case 6, the state of $System. However, if
you created a Custom View that included \Chicago\Disk\$Data, but not
\Chicago\Disk\$System, the state of \Chicago\Disk within that view is 4 – the state of
$Data. Because \Chicago\Disk\$System was not included in the view configuration, the
state of that drive has no impact on the Custom View. The Custom View always reflects
the states of objects contained within it only, regardless of what is occurring elsewhere.
Hierarchical and Object-based Display of Data
You can choose to view data hierarchically or object based in Custom View windows.
The hierarchical display presents data in highest-level to lowest-level order. The states
of the higher-level objects are determined by propagating state information from lower-
level objects. You navigate to items by drilling down through the hierarchy. It is easy to
find objects of interest because the number of items at any level is generally low, but
some navigation is almost always necessary to get to the lowest level of data.
The object-based display is virtually identical to the standard Alerts window: it shows a
list of all lowest-level objects contained in the view. No navigation is needed to find the
state of an object. All information is easily at hand, so there is no need to move through
different levels of the hierarchy to find specific object-state information, but information
for a specific object can be difficult to find as the number of entries increases.
Because each display method has advantages and disadvantages, the OEM Custom
View facility makes it easy to switch between them. Only the display changes, not the
underlying view data.
Display of All Clients or Max Client Modes
The OEM architecture allows any number of client applications to supply state
information on a particular object. The state propagation and arbitration engines ensure
that the most critical state data is reflected in higher levels of the object hierarchy and
forwarded to the EM framework adapters.
The standard Alerts and Max Alerts windows contain an entry for each client that
reported a particular object. For example, if ClientA reports \Chicago\Disk\$System
with state 5 and ClientB reports \Chicago\Disk\$System with state 2, both entries appear
in any Alerts window that includes information on that branch of the tree.
Custom View windows give you the option to continue to display data in this same
fashion or to display data only for the client reporting the maximum state. Using the
previous example, the latter scheme shows only ClientA’s \Chicago\Disk\$System entry
because it is the maximum reported state for that object. This maximum client-only
option is particularly useful when object counts are high because it further limits the