Daylight Saving Time(DST) not being updated in the OpManager

Daylight Saving Time(DST) not being updated in the OpManager

Issue: Daylight Saving Time(DST) difference is not reflected in OpManager. The Time that is being shown in "About" tab in OpManager UI will have 1 hour time difference with respect to the actual time.


Reason:  Daylight Saving Time(DST) changes that happen across various regions of the world needs to be updated in OpManager Java's timezone database. There is no auto update option as of now. So issue exists untill the timezone database is manually updated.


Updating our JRE tzdata to the latest version (tzdata2023c published on 28-03-2023) will update latest time changes to respective timezone and that will fix the time difference issue.


Solution

FILE DOWNLOAD :
1. Download the zip from attachment as per the product installed version and place it in desktop.

      For 12.6.119 and above - time_jar_update_2023c_126119_and_Above.zip

       For 12.6.118 and below - time_jar_update_2023c_till_126118.zip

2. Extract the zip to  OpManager\ directory. (give Yes to replace all the files while extraction) 
3. After extraction make sure the OpManager/jre/bin has tzupdater.jar and tzdata-latest.tar.gz files are present. Also go to 
OpManager\apiclient\fluidicv2\javascript\plugins\timezone folder or [For product version below 126119 - OpManager\apiclient\fluidicv2\javascript\timezone folder ] and check moment-timezone-with-data.min.js file's modified time is 31-03-2023.

STEPS TO UPDATE TIME IN JAVA TIMEZONE DATABASE:

1. Stop OpManager Service. Open CommandPrompt in Administrator Privilege from \OpManager\jre\bin directory  and execute below command

  1. Windows
    1.  java -jar tzupdater.jar -l "file:///<OpManagerHome>/jre/bin/tzdata-latest.tar.gz" -v
  2. Linux:
    1. ./java -jar tzupdater.jar -l "file:///<OpManagerHome>/jre/bin/tzdata-latest.tar.gz" -v

replace <OpManagerHome> with OpManager folder path 

Example:

C:/ManageEngine/OpManager/jre/bin> java -jar tzupdater.jar -l "file:///C:/ManageEngine/OpManager/jre/bin/tzdata-latest.tar.gz"-v  for windows (or)

/opt/ManageEngine/OpManager/jre/bin>./java -jar tzupdater.jar -l "file:////opt/ManageEngine/OpManager/jre/bin/tzdata-latest.tar.gz"-v for linux

2. Once command successfully executed "Validation complete. JRE updated to version : tzdata2023c" message will be shown. [Take a screenshot]

3. Start OpManager service. Refresh the browser cache. Check the timezone as well as time displayed in OpManager(About tab, Alarm time, Availability timeline,reports time,etc.,). Please check in incognito window.


                  New to ADSelfService Plus?

                    • Related Articles

                    • Configuring response time and packet loss threshold values for a group of devices in OpManager

                      In this video you'll learn how to set response time and packet loss threshold values for a group of devices in OpManager ​
                    • Discover Layer 2 Maps in OpManager.

                      Discovery mechanisms used in OpManager Layer 2 discovery: The following discovery mechanisms are used for discovering layer 2 devices in OpManager. ARP (Address Resolution Protocol): Maps IP addresses to physical (MAC) addresses, mainly used by Layer ...
                    • Types of credentials supported in OpManager

                      OpManager accesses the remote devices using the protocols such as SNMP, CLI, or WMI. The credentials like the password/snmp community, port etc., may differ for different device types. Pre-configuring a set of credentials in OpManager helps applying ...
                    • Discovering IPMI devices in OpManager

                      From OpManager version 125344, users can discover and monitor their IPMI devices along with their associated interfaces in OpManager. Using IPMI, critical metrics of your servers can be monitored even if they were down, thereby helping you stay ...
                    • Alarm severity levels in OpManager

                      Device Availability Alarm Severity OpManager has different severity for device status polling alarms. Critical: A device will be in the 'Critical' state when it does not respond for 5 consecutive availability polls that OpManager triggers. (Device ...