Instruction Manual

OEM User’s Guide—520330-001
5-1
5
Custom Views
The OEM Server provides a Custom View facility that you can use to create your own
logical groupings of OEM objects. You can base these groupings on any criteria you
choose, and can include only objects whose states fall within the range you specified.
By creating Custom Views, you can form subsets of OEM objects that span different
branches of the object hierarchy. For example, all objects related to a particular
application can be added to one view, while all objects related to another application can
be added to another. You can also create views that group all objects of a like type, such
as all CPUs or all disks, and then display the states and relationships of these objects
separately from any unassociated objects. These Custom Views can help you more
easily determine the state of entire applications and subsystems so you can detect and
diagnose problems more quickly.
Custom Grouping of Objects
Unlike the Alerts and Max Alerts windows, which display all objects within a given
branch of the OEM hierarchy, Custom Views let you combine objects from disparate
branches of the tree. Individual elements or sets of elements from anywhere in the object
hierarchy can be grouped into a single, logical collection.
For example, you could group objects based on type, application function, or geographic
location. The states and relationships of these objects can then be displayed
independently of any other objects or views defined within the OEM. The same object
can also reside in any number of Custom Views, so including the node \Seattle in a
“West Coast” Custom View does not preclude you from also including that node in a
“Funds Transfer” Custom View.
State Filtering
In addition to providing logical grouping of objects, Custom Views also permit you to
add state filters as part of the view configuration. Using this state filtering mechanism,
you can choose to only include objects in the view whose states fall within a particular
range of values. For example, you might create a view of all objects that have failed or
are in danger of failing; another view of all objects whose state has degraded since the
prior update; and maybe another view that shows all objects that are up. By combining
state filtering and logical grouping of objects, it becomes relatively easy to create a very
refined view configuration that quickly and efficiently alerts you to problems in an
application or subsystem.
Independent State Propagation and Arbitration for
Each View
Because the OEM treats each Custom View as an independent entity, the OEM
propagates state information and performs state arbitration separately for each view. As
a result, the states of high-level objects in a view accurately represent the propagated