Time Zones in Jedox

image_pdfimage_print

Jedox clients and offices are located all over the world, so  standard time format that can facilitate communication between components. Jedox uses UTC (Coordinated Universal Time) as a reference time format.

The main factor for time-related functionality (including time zone) on the server side is the server time. On Linux systems, the time used is inside the changeroot environment.

Changes in timezone (either on a server generally or for Tomcat Java procedures through setenv) impact Jedox components in various ways:

  • Timezone changes in setenv for tomcat-etl (the Integrator component) influence the times logged by the Integrator Tomcat instance, including etlserver.log. These times are also shown in the execution log of a specific execution in the Integrator Monitor UI. Note that times that are logged before a seasonal time change are not retroactively changed in the log.
  • Timezone changes in setenv for tomcat-rpc  influence the times logged by the Tomcat instance of RPC, such as in schedule_server.log. The timezone here also affects when scheduled tasks are executed. For example, a task scheduled to run at 5am will run when tomcat-rpc says it is 5am.
  • Changes to the general system time affect the previous points, as well as times in log files of other components running on the system (e.g. olap_server.log).

As of Jedox 2020.1, the time zone in which the server is located is specified in a message in the olap.log file as well as in the header of requests.txt. This information will help Jedox Support solve issues more efficiently.

The current Jedox Cloud service runs on a Linux operating system and includes shell scripts that control a number of environment variables for the system, including the system’s time zone. These scripts are called setenv.sh. Depending on the version of Jedox in use, there may be one or two instances of this script, as outlined below:

Jedox 2019.2 and later

/opt/jedox/ps/tomcat-rpc/bin/setenv.sh

/opt/jedox/ps/tomcat-etl/bin/setenv.sh

 Jedox 2019.1 and earlier

/opt/jedox/ps/tomcat/bin/setenv.sh

The screenshot below shows the contents of a typical setenv.sh file.

Contents of setenv.sh

The highlighted line:

              export TZ=UTC-10

sets the time zone for this part of the system.

If you suspect your Jedox time zone settings are not correct, please contact support@jedox.com.

Time zones for Jedox locations

The table below lists the time zones where offices are located, and the time difference compared to UTC.

Note: Most of these areas use Daylight Saving Time (DST). For some of them, DST does not occur on the same date every year. You can check the time changes of any specific city here.

Office Local Time
Time
Freiburg im Breisgau, Germany CET/CEST UTC + 1h/ UTC + 2h during Daylight Saving Time.
Frankfurt am Main, Germany CET/CEST UTC + 1h/ UTC + 2h during Daylight Saving Time.
Düsseldorf, Germany CET/CEST UTC + 1h/ UTC + 2h during Daylight Saving Time.
Paris, France CET/CEST UTC + 1h/ UTC + 2h during Daylight Saving Time.
Bucharest, Romania EET/EEST UTC + 2h/ UTC + 3h during Daylight Saving Time.
Boston, MA, USA EST/EDT UTC – 5h/ UTC – 4h during Daylight Saving Time.
Melbourne, Australia AEDT/AEST UTC + 11h/ UTC + 10h during Daylight Saving Time.
Sydney. Australia AEDT/AEST UTC + 11h/ UTC + 10h during Daylight Saving Time.
Singapore SGT UTC + 8h

To find out your time zone in UTC, use a time and date converter.

image_pdfimage_print