Correlating Important Events › Understanding Configuration Manager › How Unicenter Notification Services Works

How Unicenter Notification Services Works

Unicenter Notification Services keeps track of all notifications that you send. This is especially important for two-way notifications that must be matched with responses. Here is the process:

1. You create a notification message by using one of the following features:
   • User interface
   • Command line or script
   • Event Console by right-clicking a message
   • Event Management NOTIFY action
   • Alert Management escalation
   • Application using the Notification Services client SDK
2. Based on the recipient, provider, or protocol information in the request, the Notification Services daemon (unotifyd) selects a protocol-specific driver to send the notification.

   Note: The daemon runs as a service on Windows and as a background process on UNIX/Linux.

3. The daemon assigns a tracking ID, which it returns to the command or program that sent the notification.

   Note: If the daemon stops and then restarts, it also restarts the outstanding notifications stored on disk.

4. If a response was requested, the daemon checks for it periodically from the service provider.
5. The daemon stores information about the notification on disk, and updates that information throughout the life cycle of the notification. This is called checkpointing. Updates include:
   • The request is created.
   • The service provider received the notification.
   • The provider delivered it.
   • The recipient read it.
   • The recipient sent a reply.

More information:

Features of Unicenter Notification Services