Jedox clients and offices are located all over the world. This requires a standard time format that can facilitate communication. We use UTC (Coordinated Universal Time) as a reference time format.
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||
|Jedox 2019.1 and earlier||
The screenshot below shows the contents of a typical setenv.sh file.
The highlighted line:
sets the time zone for this part of the system.
If you suspect your Jedox time zone settings are not correct, please contact firstname.lastname@example.org.
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.
|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.