Hierarchy domains group and categorize objects by their type and function. A common example of hierarchy domains is a combination of various types of monitored operating systems, such as OS, Windows®, Linux®, UNIX®, AIX®, HP-UX, Oracle Solaris®.
Hierarchy domains are used by the Domain Viewer to sort and group objects for counting. Higher-level hierarchy domains can contain sub-domains.
Alarm Associations link alarms (using its rule ID) to default dwell and drill-down views, and optionally to a set of named or tagged diagnostic and remediation workflows, when such workflows are defined.
Views that display alarms can use alarm associations. An Alarm Association for a given rule ID contains the following elements:
A domain activity associates an activity with a hierarchy domain, and defines how objects in the domain are counted.
Domain activities are primarily used by hierarchy domains within the context of the Domain Viewer.
Each domain activity specifies an activity and a hierarchy domain, meaning that the given activity is available to that domain. It also specifies a function that is used to categorize the state of objects belonging to the domain, which generates counts in the Domain Viewer.
An Action Association defines an action for use in toolbars and action lists. A minimal action has label text and a reaction that is fired when the action is triggered.
Action Associations are used by toolbars and components that provide sets of actions internally.
Actions can be tagged and discovered by matching tags which means that a toolbar can dynamically have actions added to it, as functionality is added to the system.
The Disabled and Display properties may be bound to RVs which can control the visibility and accessibility of the action based on current data/state.
When an icon is configured for an action, it appears in toolbars and in action lists.