Introduction

Any time Time zone names are specified according to the List of tz database time zones.

...

• JS7 Components
  • JOC Cockpit, Controller and Agents can be operated in different time zones. Time zones are preset by the operating system.
  • This includes to run running a number of Agents in different time zones.
• Scheduling Objects
  • Orders are scheduled for a point in time calculated for the given time zone by the orders' JS7 - Schedules.
  • Jobs consider the The time zone of their workflow to calculate the workflow is taken account of when the JS7 - Admission Times for Jobs are calculated.
  • The JS7 - Daily Plan considers the Daily Plan time zone. A Daily Plan does not necessarily have to span midnight to midnight, instead the Daily Plan can use any hour of the day as the starting point for its 24 hours period.
    • The Daily Plan's time zone is taken account of in both the start of the Daily Plan period and the point in time when the Daily Plan is calculated are both considering the Daily Plan's time zone.
    • Cyclic workflows that make use of the JS7 - Cycle Instruction consider also take account of the Daily Plan time zone.
• Graphical User Interface (GUI)
  • Any dates and times that become visible with are shown in the GUI are first converted to the time zone specified with in the user's profile.
    • This applies to order start dates, job admission times, any entries of the JS7 - History etc.
    • This also applies to timestamps of order logs and task logs that are executed on Agents in different time zones. Users can choose from their user profile settings if they prefer to be presented with original log timestamps of logs or if they prefer to have timestamps converted to the time zone specified with in the user profile.
  • When adding orders by the GUI then the time zone of the order's start date is specified.
  • When posting notices to JS7 - Notice Boards then the time zone for the notice's lifetime is specified.
  • Any time zones applied by the GUI by default are populated from the user profile's time zone setting and can be modified by the user.

Time zone changes include that:

• changes time zones can change for individual countries due to government 's decisions. The same This also applies to changes to the date and time of daylight saving changetime,
• Note that such changes can occur at short notice and therefore might not be reflected with in the time zone database that ships with an earlier JS7 release.
• Consider to update updating JS7 at a regular basis in order to receive up-to-date time zone databases.

...

The JS7 Controller, Agent and JOC Cockpit by default use the time zone specified by the operating system by default.

Controller

The Controller does not use any time zone specification except for the time zone reported by the operating system.

• The Controller forwards dates to JOC Cockpit in UTC time and in case of JS7 - Order State Transitions with Agents, it adds the Agent's time zone if applicable.
• The timestamps of entries in the Controller's log files are determined from the operating system time zone. This can be modified with the Log4j2 configuration file, see JS7 - Log Rotation.

...

• JS7_AGENT_TZ indicates the Agent's time zone.
• JS7_SCHEDULED_DATE indicates the date an order is scheduled for and includes the offset of the Agent's time zone to UTC, e.g. 2020-12-03 09:13:59+0100.
• JS7_SCHEDULED_YEAR, JS7_SCHEDULED_MONTH, JS7_SCHEDULED_DAY, JS7_SCHEDULED_HOUR, JS7_SCHEDULED_MINUTE, JS7_SCHEDULED_SECOND are indicated in the Agent's time zone.
• JS7_JOBSTART_DATE indicates the date a job is started in the Agent's time zone and includes the offset of the Agent's time zone to UTC e.g. 2020-12-03 09:13:59+0100.
• JS7_JOBSTART_YEAR, JS7_JOBSTART_MONTH, JS7_JOBSTART_DAY, JS7_JOBSTART_HOUR, JS7_JOBSTART_MINUTE, JS7_JOBSTART_SECOND are indicated in the Agent's time zone.

Note:

• Consider Note that the offset of the Agent's time zone to UTC can change during a Daylight Saving Change. The offset to UTC indicated by the above environment variables is calculated at the point in time when a job starts. Jobs sensible sensitive to Daylight Saving Change should consider Changes should take account of the fact that such changes can occur during job execution.

JOC Cockpit

The JOC Cockpit makes no does not use of the time zone reported by the operating system for the following purposes:

• the JOC Cockpit switches its Java Virtual Machine to the UTC time zone. This behavior is required to guarantee consistent database transactions that are not aware of Daylight Saving Change.
• the JOC Cockpit Web Services perform any date calculation calculations in the UTC time zone.

By default, the JOC Cockpit by default makes use of the operating system time zone when writing timestamps to log files. Users can modify the time zone for log timestamps, see JS7 - Log Rotation.

...

Note: If the option "Now" is used then the order starts immediately independently from of the user's time zone setting. 

Daily Plan Service

The Daily Plan Settings consider take account of a time zone for the start of the 24 hours period of the Daily Plan and for the point in time when the Daily Plan is calculated, see JS7 - Daily Plan Service.

...

User Profile

The user profile by default is populated with the browser's time zone setting by default. Users are free to choose a different time zone. Any dates visible with JOC Cockpit are converted to the user profile's time zone.

...

Orders Overview

The date range for the selection of orders in this view considers take account of the user's current time zone setting:

...

Changes to Daylight Saving can happen at different points in time per for individual JS7 component components, if the JOC Cockpit, Controller and Agents are operated in different time zones.

...

• The Controller calculates dates and times in UTC that doesn't does not know of Daylight Saving.
• The Controller is not involved in calculation of timestamps reported from Agents for log output or orders and tasks.

The By default the Controller's own log files by default state contain timestamps in the server's time zone that is as determined by the Controller Start Script.

• The Controller Start Script applies the server's time zone as reported by the operating system to Java. If no a server time zone is not set then it will fall back to the UTC time zone.
• The Controller Start Script provides the JS7_CONTROLLER_TZ environment variable to indicate the time zone in use.

By default the Controller's Log4j configuration makes use of the JS7_CONTROLLER_TZ environment variable and applies timestamps accordingly. This includes to reflect reflecting Daylight Saving Changes for timestamps in the Controller's log output if indicated by the time zone. For details see JS7 - Log Rotation.

...

The Agent keeps track of timestamps created for log output of orders and tasks as follows:

• The Agent runs in its server's time zone and applies Daylight Saving Changes accordingly.
• Log output of orders and tasks immediately reflects changes to the server's time.

The By default, the Agent's log files by default state contain timestamps in the server's time zone that is as determined by the Agent Start Script.

• The Agent Start Script applies the server's time zone as reported by the operating system to Java. If no a server time zone is not set then it will fall back to the UTC time zone.
• The Agent Start Script provides the JS7_AGENT_TZ environment variable to indicate the time zone in use.

By default the Agent's Log4j configuration makes use of the JS7_AGENT_TZ environment variable and applies timestamps accordingly. This includes to reflect reflecting Daylight Saving Changes for timestamps in the Agent's log output if indicated by the time zone. For details see JS7 - Log Rotation.

...