Systemwide variables that determine the period and size after which the log files are changed.

As a system administrator, you can change the log files to ensure that you system runs smoothly during high workload times for the Automation Engine and the Agents. The log files can be changed after a certain period of time, or after they have reached a certain size (in MB). You can also archive and reorganize this data in the Automation Engine database, even if the Automation Engine and the agents are active for several months without interruption. For more information, see AE DB Archive and AE DB Reorg.

For work processes, you use CHANGE_LOGGING_MIN_TIME to define a minimum period of time between to log changes. This allows you to avoid a lot of log changes in a short time, for example on very high load.

Also, you can specify temporary log file changes in the Administration perspective and specify server settings for the log file change of work processes, see Processes & Usage. These modifications are valid until the system reboots. Use the script element CHANGE_LOGGING to trigger a forced log file change.

To avoid endless reports for events, RemoteTaskManagers, Sync objects, and Schedule objects, their reports are also changed and a new statistical record begins. In this case, only the setting of CHANGE_LOGGING_DAYS is relevant.

Important! CHANGE_LOGGING_MB only works if the setting LOG_TO_DATABASE is set to Y. For the Automation Engine, define this setting in the UC_SYSTEM_SETTINGS variable. For agents use the variable UC_HOSTCHAR_DEFAULT - Host Characteristics. CHANGE_LOGGING_DAYS does not depend on this option.

The log files of all work processes are automatically changed if the logging of a work process (WP, DWP, PWP) changes. The logging of tasks that start on a recurring basis is changed on a daily basis or if the period settings are modified.




See also:

UC_SYSTEM_SETTINGS - Systemwide Settings