Inside Automation Engine > Date and Time > Using TimeZones in the AE

 Using Time Zones in the Automation Engine

Time plays a key role in AE when programs communicate with each other, tasks are activated, conditions evaluated,  data is saved etc. Time becomes even more important when AE is used on a global basis across several TimeZones and when interconnected tasks are to run properly.

The components (server processes, agents, databaseA database is an organized collection of data including relevant data structures., etc.) internally use the internationally agreed and precise UTC time scale. Nevertheless, TimeZone objects can be created to indicate local times which can also be used in tasks and scriptA particular Automation Engine object type. elements. TimeZones contain specifications such as the point in time when the clocks are changed to winter time or daylight savings time, or the time difference to UTC. The name of a TimeZone objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task must not be comprised of more than 8 characters.Note that TimeZones consisting of more than 8 characters cannot be selected in other objects!

The folderTop level entities such as Environment, Deployment Target, Activity, … are stored in folders. The permissions a user has on an entity depend on the permissions that are set on the folder for the entities. "TEMPLATE" in the system 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. 0000 contains the following TimeZone templatesPre-defined 'workflows' for specific components/tasks, e.g. Tomcat, SubVersion.:

Usage

The created time zones can be used for various purposes such as:

Usage

Tab

Client

"Attributes"

User

"User"

Setting in the UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."]

"TimeZone/Calendar"

Executable objects

"Attributes"
"Runtime"

Properties in executable objects (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."] and schedule)

"Checkpoint"
"Earliest"
"Dependencies"
"Runtime"

Already when creating a new client you can specify a time zoneIt defines a local time. A particular Automation Engine object type.. This time zone is then used within this client when tasks are processed and for indicating date and time. If a different time zone is required for a particular object, it can be specified in this object's Attributes tab. Time zones can also be specified for taskAn executable object that is running. Tasks are also referred to as activities. properties in workflows and Schedules. These time zones will then be given priority.

Hence the appropriate time zone is searched for in the following order:

Object settings  -> Client

The client's time zone is used if no time zone has been selected in the object. UTC is used if no time zone has been specified at all. Automic recommends indicating a time zone at least in the Client object.

For the properties of workflows and schedules (such as the latest start time), either the time zone selected there or the time zone of the workflow or Schedule objectIt starts executable objects periodically. A particular Automation Engine object type. is used. If there is also no time zone available, the client's time zone or UTC is used.

For starting tasks in schedules, the particular schedule's time zone is valid!

Display

Time zones specified for a userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. serve mere information purposes (such as in the Message WindowA window that appears on the user interface and contains information, warning, and error messages.). The same holds true for UserInterface settings which can be specified by each user. Both do not influence the processing of tasks. Therefore, it is not important to know the user who has started the object.

Script

Time zones are additionally used in many script elements. The following listShows entities in a grid view shows the ones in which time zones are assigned as parameters.

Script Function

Description

CONV_TIMESTAMP

Converts date and time for use in another time zone.

SYS_DATE

Returns the current date at the beginning of the script processing.

SYS_DATE_PHYSICAL

Returns the current date.

SYS_TIME

Returns the current time of day at the beginning of the script processing.

SYS_TIME_PHYSICAL

Determines the current time of day.

SYS_TIMESTAMP_PHYSICAL

Provides current date and time.

Additional script elements referring to date and time are found in the document Script Elements - Ordered by Functions

Logical Date

When executing tasks with options and creating forecasts, you can indicate a so-called "logical dateThe logical date is used as a comparison date for checking Calendar conditions.". In this case the date specified in the calendarAn Automation Engine object type that defines a set of days based on calendar keywords. conditions of workflows and Schedules is used instead of the current date.

See also:

TimeZone Object
TimeZones - Overview

Examples for Using TimeZones

Time

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH