Thingworx 9.1 displays times with 2 hours less/more

[PGrasso]

Hello, we are facing this issue

Thingworx shows times with 2 hours less, retrieving the dates on the platform, and 2 hh more retrieving dates from the database (See attaches).

ThingWorx version 9.1.1-b483.
The VMs & MSSQL are in CET. They are in the same industrial infrastructure.
The data in the SQL table is in CET.

Is it possible to change the timezone into the platform/tomcat?

Thanks in advance

Pier

[PaiChung]

ThingWorx works in UTC it then offsets it based on the Server or Client time that you are using to access the information.

So it sounds like your Server and Client are set to different time zones.

If that has to be the same, then you would change the server clock to match.

[slangley]

Hi @PGrasso 

Did you install 9.1 as a fresh installation or were you upgrading?  If installed as a fresh installation, did you install manually or use the installer?

There is an option that needs to be set in the Tomcat Java options as detailed under step 16 of this page from the Help Center.  Here is a link to the upgrade section in case you were upgrading.

Please provide more information and we'll be happy to assist further.

Regards.

--Sharon

[PGrasso]

Hi @slangley 

ThingWorx: 9.1.1-b48, Installed from scratch, using the installer.

The database and the TWX platform are on different servers and both servers have OS timezone = CET.

If I can try to give an idea of the overall view, the current solution has just purpose to show the data that already exists on an external db. So this data is not generated by the solution.
The dates contained in this external db are in CET.

I've found this about the installation:

The questions are: is it possible to change the -Duser.timezone from UTC to CET in tomcat? If on, why?

Is it possible to remove the current -Duser.timezone, from tomcat configuration, by forcing the platform to use the OS timezone? If on, why?

Thanks in advance

Pier

[slangley · Accepted solution]

Hi @PGrasso.

You may have overlooked it in the article you found, but there is the potential for data loss if changing the time zone parameter to one that observes daylight saving time.  Removing this parameter would have the same effect.

It would be best to change your external database to UTC time to keep everything in sync.

Regards.

--Sharon

[slangley]

Hi @PGrasso

If you feel your question has been answered, even if it wasn't the answer you wanted, please mark the appropriate response as the Accepted Solution.  This will help others in the community with the same issue.

Regards.

--Sharon