Event Handler Database

An event handler record describes the action that Universal Event Monitor (UEM) should take in response to a monitored event's outcome. This action, or response, is simply a system command or script that UEM executes upon an event's completion, failure to complete, or failure to occur. The UEM Server executes these processes in a secure context, using user account credentials stored in the event handler record.

A Stonebranch Tip

Security is a primary concern within all Universal Agent components.

Whenever the user account information stored in an event handler record includes a password, that password is encrypted using the Data Encryption Standard (DES) algorithm.

An event-driven UEM Server relies upon stored event handlers to determine its response to the events that it monitors. The event definition records that describe events to UEM also contain the IDs of event handler records that UEM should use to respond to those events.

A demand-driven UEM Server also may respond to an event using a stored event handler record, but it is not required. Typically, a demand-driven Server relies upon the UEM Manager's command line parameters to describe the actions that it should take in response to the event that it monitors.

When a UEM Server needs to use a stored event handler record, it sends a request to the Universal Broker to retrieve the record using the ID specified in the event definition record or provided from the UEM Manager command line. The Universal Broker returns the event handler record to the UEM Server, which then executes the specified system command or script.

Event handler records are added and maintained with the UEMLoad Utility.

Browser not supported