Technical bulletin — Daylight Saving Time (DST) change impact on the TrueSight console
Due to the Daylight Saving Time (DST) change, the time displayed and time of events in the TrueSight console lag by 1 hour.
This topic contains information about resolving the impact of DST changes on the TrueSight console.
Affected versions
TrueSight Presentation Server 10.7.00 and later.
How can you resolve it?
For version 11.3.04 only
Download and install the latest hotfix from the
FTP location.
For all other versions:
Prerequisites
Download the moment-timezone-with-data-2010-2020.min.js
file from one of the following locations:
TrueSight Presentation Server standalone setup
- From the TRUESIGHTPSERVER_HOME\truesightpserver\modules\tomcat\webapps\ROOT\lib\moment directory, back up the
moment-timezone-with-data-2010-2020.min.js
file to a location outside the installation path. - Stop the TrueSight Presentation Server by using the following command:
tssh server stop
- Download the
moment-timezone-with-data-2010-2020.min.js
file and save it in the TRUESIGHTPSERVER_HOME\truesightpserver\modules\tomcat\webapps\ROOT\lib\moment directory. - Start the TrueSight Presentation Server by using the following command:
tssh server start
TrueSight Presentation Server High-Availability setup
- From the TRUESIGHTPSERVER_HOME\truesightpserver\modules\tomcat\webapps\ROOT\lib\moment directory, back up the
moment-timezone-with-data-2010-2020.min.js
file to a location outside the installation path on both the nodes of the TrueSight Presentation Server. - Stop the secondary server that is the standby node by using the following command:
tssh server stop
- Stop the primary server that is the active node by using the following command:
tssh server stop
- Download the
moment-timezone-with-data-2010-2020.min.js
file and save it in the TRUESIGHTPSERVER_HOME\truesightpserver\modules\tomcat\webapps\ROOT\lib\moment directory on both the nodes of the TrueSight Presentation Server. - Start the primary server by using the following command:
tssh server start
- Verify that the primary server is the active node by using the following command:
tssh ha status
- Start the secondary server by using the following command:
tssh server start
TrueSight Presentation Server Disaster Recovery setup
You must apply this fix to resolve the issue in a Disaster Recovery (DR) setup.
Was this page helpful? Yes No
Submitting...
Thank you
Comments
Log in or register to comment.