The components (such as server processes, agents, databaseA database is an organized collection of data including relevant data structures.) internally use the internationally valid and precise UTC time scale. You can create TimeZone objects in order to have local times displayed and use them in taskAn executable object that is running. Tasks are also referred to as activities. and scriptA particular Automation Engine object type. elements.
You can specify the point in time for changing from winter to summer time in a TimeZone objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task. The following illustration shows the relevant section in the Attributes tab.
Changing from Standard Time to Daylight Savings Time
When you change over from standard time (winter time) to daylight savings time (summer time), the clock is set forward by a particular number of minutes. The time difference from standard time to daylight savings time is country specific. Usually, a value of 60 minutes (one hour) is used. Setting the clock forward means that on the day on which you change over to the new daylight savings time, you lose one hour. This day is then one hour shorter than a regular day.
For example:
The local time is set forward for 60 minutes from 02:00:00 to 03:00:00. As a result, this day has only 23 hours and there is no local time between 02:00:01 and 02:59:59.
Consequences:
Changing from Daylight Savings Time to Standard Time
When you change over from daylight savings time to standard time (winter time), the clock is set back. Therefore, the time difference between the point when the time is set back and the newly set winter time is doubled. This day is then longer than a regular day.
For example:
The local time is set back for 60 minutes from 03:00:00 to 02:00:00. As a result, this day has 25 hours and the time between 02:00:01 to 02:59:59 is doubled.
Consequences:
Event objects
The interval for eventAction that is triggered if particular conditions apply. It can be an Automation Engine object type or an entry in a Policy Orchestrator EventBase. activation is not synchronized with time zones. For example, if an Event object should be triggered every 4 hours, a clock change to daylight savings time has the following impacts (time indicated in 24 hours):
Start time: 08:00
Additional triggering times: 12:00, 16:00, 20:00, 00:00, 04:00, 08:00
Clock change to daylight savings time: ..., 20:00, 00:00, 05:00,
09:00, 13:00
05:00 because the clock is set forward when it is changed to daylight savings time (at 02:00 to 03:00 o'clock), but the object still keeps its 4-hour interval. The same applies when you change over to standard time.
Pay special attention to this behavior if a calendar with a time period has been defined in the Event object. In this case, the triggering times are re-scheduled and can lie within or outside of the specified time frame after the clock has been changed. Automic recommends starting the Event object via a Schedule in order to avoid such a situation. The event's start time is then adjusted to summer or winter time when the period turnaround takes place.
When you set up an interval where the object would be executed in the hour that is missed out by the time change, the object will be executed at the next full hour.
Example: An interval of 20 minutes has been set, the first check time is 01:49, then the next check time should be 02:09. But since that hour is missing because of the time change, your object will be executed at 03:00. So the interval would be 11 minutes long only in this one instance.
The reason for this behavior is the necessity for the EH_NEXTCHECK to re-calculate UTC into local time (of clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients.
A particular Automation Engine object type. or object, respectively), in order to ensure that e.g. workflowAn object of the Automation Engine that can include several executable objects and which runs them in a specified order. [Formerly called "ProcessFlow" and "JobPlan."] or calender objects with time settings are executed correctly.
See also:
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |