Overview of notifications

The
Global Manager
stores the topology and event information that it receives from the underlying domains in its repository. The topology and event information are stored as objects, that is as instances of the classes defined in the ICIM model. The notifications that
Global Manager
sends to clients are themselves objects in the
Global Manager
’s repository.
Notification objects, similar to other objects in the
Global Manager
’s repository, have attributes that describe their properties. For notifications, these attributes include the time the event occurred, the type of event, the name of the object where the event occurred, and much more information.
“Attributes for matching notification properties” on page 215
provides a complete list of notification attributes.
Notification attributes are used throughout
for a variety of purposes:
  • Notification attributes correspond to the columns in the Notification Log of the Global Console.
    Attribute names are not exactly the same as the column headings of the Notification Log.
  • You can specify a matching pattern against the values of notification attributes for filtering a notification list.
  • Twenty notification attributes are user-defined. You can write an ASL script that populates these attributes with additional information.
    This chapter discusses how you can manage notifications using the Global Manager. In addition to the standard notification processing provided by the Global Console, you can also manage notifications creation in a more extensive manner from any event source using the NOTIF Editor. This editor allows for real-time reconfiguration of event and notification processing without server restarts. The
    provides detailed information on configuring events and notifications using the NOTIF Editor.