Users Guide

Understanding Hierarchical View | Presentation Capabilities
OMNM 6.5.3 User Guide 253
Understanding Hierarchical View
Hierarchical views manage what appears in other portlets on the same page, including Topology
and Maps portlets. If a page with a Topology portlet has no Hierarchical View portlet, clicking a
topology node limits other portlets on that page to only that node’s information (for example
Alarms).
Here are the
context display rules for how portlets manage each others’ displays:
The context rule displays in a portlet’s header if its appearance is being managed by another portlet
as defined by these context display rules.
When a page with a
Hierarchial View loads, the hierarchy loads first and then starts polling. If a
System Topology portlet is on the same page as a Hierarchical View portlet, the System Topology
portlet starts its polling after the page loads, so some lag may occur between the Hierarchical View
and Topology Views portlets, depending on your settings. Clicking Context from a portlet or
drilling down or expanding nodes in the Topology portlet resets the refresh timer since it may poll
different nodes. This can also offset refresh timing for different page elements. You can change
refresh timing from the Application Settings window (see
Redcell > Application Settings on page
34 for details), but synchronizing such portlets is not likely.
NOTE:
Some portlets may display a selected context without operating as though it was selected. For example if
you put Managed Resources.
Some pages may not exhibit this default behavior. For example, custom branding on pages may
interfere with these rules, in which case, you can see the default behavior by creating a new page
with the relevant portlets. You may also try refreshing the page.
You can disable the context responses in the Alarms portlet from its preferences menu (click the
wrench). When you disable context responses, the Alarm portlet instance’s auto refresh displays
new, unique alarms, but does not display, for example, a selected hierarchical view’s alarms.
Otherwise, you must change the context call from the Hierarchical View portlet to refresh alarms.
Rule Description
1 If the Hierarchical View portlet is on a page, its selections drive all portlets that
accept context. If you have no hierarchies configured, the other portlets are empty.
If the Hierarchical View portlet is not on a page, then the remaining rules may apply.
2 If the System Topology portlet is on a page, it acts like the Hierarchical View portlet
and drives all portlets’ appearance.
3 If rules 1 and 2 are not in effect, the Managed Resources portlet drives Ports and
Links portlets’ appearance.
4If rule 1 is not in effect and the Topology Views portlet is on the same page as the
System Topology portlet, the selected view appears in the Topology portlet.