UEM Server for UNIX - Configuration
Overview
All UEM Servers defined on a particular system share a single configuration. A demand-driven UEM Server reads configuration options when it starts, and uses those values while it executes. Because an event-driven Server can run for an extended period of time, the configuration information it caches at start-up can be refreshed whenever the stored configuration options are refreshed (see Configuration Refresh).
A UEM Server's configuration consists of default values that are used to establish the runtime environment and provide missing values for required event definition and event handler parameters.
Configuration File
Stored configuration options reside in the UEM Server configuration file. The name of this file can be set in the UEM component definition file. The default name for this file is uems.conf. This is a plain text file that can be edited with any text editor.
Configuration options stored in the configuration file are done so using a keyword/value combination. The keywords for each configuration option are included along with the description of the option.
UEMLoad
The UEMLoad utility can override a configured default via its command options when it adds records to the event definition and event handler databases. Also, a UEM Manager can override options for a demand-driven UEM Server when it submits a monitoring request. The syntax for those overrides, when available, are included with the option's description.
Configuration Options Categories
The following table categorize available UEM Server configuration options according to function. Each Category name is a link to a table of options in that category. Each Option Name in those tables is a link to detailed information about that option.
|
Category |
Description |
|
Allow default values to be set for any required event definition parameters that were omitted from the UEM Manager or UEMLoad utility request. | |
|
Allow default values to be set for any required event handler parameters that were omitted from the UEM Manager or UEMLoad utility request. | |
|
Options that specify installation requirements, such as directory locations | |
|
UEM message options. | |
|
Control UEM activity. | |
|
Manage data transmission between local and remote systems. |
Event Definition Category Options
|
Option Name |
Description |
|
UEM Server component to which a stored event definition is assigned. | |
|
Frequency, in seconds, with which a tracked event occurrence is tested for completeness. |
Type-Specific Event Definition Options
These options are specific to event definitions with an event type of FILE.
|
Option Name |
Description |
|
Smallest size a file may be in order for it to be considered complete. | |
|
Flag that indicates whether or not a completed file should be renamed. | |
|
Name or pattern to use when a file is renamed. |
Event Handler Category Options
|
Option Name |
Description |
|
ID of a stored event handler record that should be used whenever an event is set to an expired state. | |
|
Specifies whether or not to load a user's profile and environment when a handler process is executed. | |
|
Highest return code than an event handler may exit with to still be considered as having executed successfully. | |
|
ID of a stored event handler record that should be used whenever an event occurrence is set to a rejected state. | |
|
Default shell interpreter for event handler processes executed as scripts. | |
|
ID of a stored event handler record that should be used whenever an event occurrence is set to a triggered state. | |
|
Specifies whether or not user account authorization is required to monitor an event and/or execute a handler process. |
Installation Category Options
|
Option Name |
Description |
|
Base directory in which the product is installed |
Message Category Options
|
Option Name |
Description |
|
Level of messages written. | |
|
List of message IDs representing Universal messages to be suppressed. | |
|
Directory location of message catalog and code page tables | |
|
Specifies the directory in which trace files are written. | |
|
Maximum number of lines written to a trace file before it wraps around. | |
|
Memory trace table specification. |
Monitoring Category Options
|
Option Name |
Description |
|
Frequency with which a UEM Server will detect new occurrences of a system event. The UEM Server will also check at this time see if a monitored event should be made inactive. |
Network Category Options
|
Option Name |
Description |
|
Code page used for text translation. | |
|
Frequency with which a Keep-Alive message is sent to the UEM Manager. |