|
Structure of the Export File |
Inside Automation Engine |
Best Practices Guide |
|
There are various processes in the AE that take place automatically at certain times. As a user, you can manipulate some of them.
| Processing/Procedure | Processing takes place ... | The effective TimeZone is ... | This affects ... | Additional Explanations |
|---|---|---|---|---|
| Validity check of calendars | daily, at 00:00 am | UTC | all clients | You activate the validity check for calendars in the variable UC_CLIENT_SETTINGS with the settings CALE_WARN_LEVEL and CALE_WARN_NOTIFICATION. |
| Calculation of calendars | on the first day of the year, at 0:00 am or when the Automation Engine starts. | UTC | all clients | The calculation of the days on which the keys of Calendar objects are valid is important in order to ensure that they can be checked. |
| Period turnaround of schedules | as defined in the Schedule object | the Schedule's time zone | every Schedule in a different way. | - |
| Log-file change | daily, at 00:00 am | UTC |
all agent and server processes, events, Schedules, RemoteTaskManagers, Sync objects, and the recurring tasks in all clients. |
In the variable UC_SYSTEM_SETTINGS you use the settings CHANGE_LOGGING_DAYS and CHANGE_LOGGING_MB to determine how often and in which intervals the automatic log-file change should take place. You can also determine the log-file change for agents and server processes in the System Overview or by using the script element CHANGE_LOGGING. |
| ILMStands for Information Lifecycle Management, which refers to a wide-ranging set of strategies for administering storage systems on computing devices. partition change |
on the days that are specified in the calendar that is set in the variable UC_ILM_SETTINGS with the key CALENDAR, at 00:00 am. |
the time zone of the system client 0000 | the AE databaseA database is an organized collection of data including relevant data structures. | See also: Partitioning with ILM |