| Panel | |
|---|---|
|
Overview
A Universal Event Monitor (UEM) Server has three database files that it can use during event processing:
- ueme.db stores event definitions.
- uemh.db stores event handlers.
- uems.db is a spool file that records all activity related to event monitoring.
The UEMLoad utility (uemload) manages the event definition and event handler database files. (For information on the spool database file, see Universal Event Monitor Server.)
UEMLoad can be used to:
...
When a definition load file is redirected from stdin to Universal Command, Universal Command will in turn forward the redirected stdin to a remote instance of UEMLoad. UEMLoad then behaves as though it were reading a local definition load file.
For detailed information on the event definition and event handler database files, see UEMLoad Utility.
Controlling Database Access
Universal Broker is primarily responsible for providing access to the Universal Agent databases.
However, there are utilities provided, including Universal Spool List (uslist) and Universal Spool Remove (uslrm) that can be used for direct access to these databases. While these utilities should be used only following a recommendation from and with the assistance of Stonebranch, Inc. Customer Support, they are documented in the Universal Agent Utilities 7.36.x Reference Guide.
To protect the database contents, operating system permissions on the database files themselves should be set so that only accounts with super-user or administrative privileges have access to them.
For more information on the location, names, and contents of the UEM database files, see UEM Server Database Files.
Access via UEMLoad Utility
While the contents of UEM databases can be viewed using Universal Spool List, it is recommended that all access be done using the UEMLoad utility.
The ability to remove event definition and event handler records is provided only with UEMLoad. Universal Spool Remove cannot be used to delete records from those databases.
Only UEMLoad can manage event definition and event handler databases that are local to the system on which the UEMLoad resides. To process a request, the UEMLoad sends a message to the Universal Broker running on that system, instructing it to start a demand-driven UEM Server. A control session is established between UEMLoad and the UEM Server, which provides for direct communication between the two processes.
...
Support for controlling access to the event definition and event handler databases also is provided by UEMLoad.
A type of Universal Access Control List (UACL) is provided in order to grant or deny local user accounts the authority to execute UEMLoad. The type of database access (that is: add, update, delete, list, and export) allowed for each authorized user also can be defined.
...