Definition File Format for Windows
The format of the definition load file for events and event handlers follows the keyword / value-pair convention used for Universal Agent configuration files. However, because more than one definition can be specified in a load file, some additional conventions are used.
- The begin_event and end_event keywords are used to mark the beginning and end, respectively, of each event definition entry.
- The begin_handler and end_handler keywords are used to mark the beginning and end, respectively, of each event handler entry.
- The begin_script and end_script keywords are used to mark the beginning and end, respectively, of any user script contained in the definition load file.
Lines that belong to the script must begin with the stmt keyword. Long stmt values that have to be split across lines can be done so using the + and - line continuation characters (as described in Configuration File Syntax). These lines will be accepted verbatim, and no script syntax validation will be done. Lines will continue to be added to the script until an end_script, end_handler, begin_handler, or begin_event keyword is read, or the end of the file is reached.
If a parameter's value contains spaces, it must be enclosed in double ( " ) quotation marks.
If quotes are to be saved as part of the parameter's value, use extra double ( " ) quotation marks to escape the quotes (for example, optname "optval1 ""optval2 optval2a"" optval3").
The script keyword can be used in lieu of a begin_script/end_script block, in which case the contents of the specified file will be written to the event handler.
A sample definition file for Windows is shown in the following figure.
Definition File Options
The Definition File options used in this example are:
|
Option |
Description |
|
Identifier that uniquely identifies an event definition record. | |
|
Type of system event represented by the event definition record. | |
|
Event-driven UEM Server responsible for monitoring the event. | |
|
Event definitions that should be processed or ignored by UEM. | |
|
Date and time at which UEM will stop monitoring an event definition. | |
|
ID of an event handler record that UEM will execute when an event occurrence is triggered. | |
|
Name of a file to monitor. | |
|
Specification for whether or not UEM should rename a monitored file when an event occurrence is triggered. | |
|
Specification for how a file should be renamed when an event occurrence is triggered. | |
|
Identifier that uniquely identifies an event handler record. | |
|
Type of process executed for the event handler, based on the contents of the USER_COMMAND and USER_SCRIPT parameters. | |
|
Highest value with which a handler can exit to still be considered as having executed successfully. | |
|
ID of a user account in whose security context the handler process will be executed. | |
|
Type of script statements contained in the action field of the event handler record. | |
|
Command to execute on behalf of the event handler. |