Unable to update Daylight Saving Time (DST) in Applications Manager
Issue: The server System Time present in the bottom left corner of the Applications Manager UI does not display the Daylight Saving Time (DST) difference. It has a 1-hour time difference from the actual time.
Reason: The Daylight Saving Time (DST) changes that happen across various regions of the world need to be updated in Applications Manager Java's time zone database. Currently, Applications Manager does not offer an auto-update option for this change. So the issue remains until the time zone database is updated manually.
Updating the JRE tzdata to the latest version will incorporate the most recent time changes for each respective time zone, thereby resolving the time difference issue.
Solution:
For version 16430 and above
- Download the ZIUpdater tool from this link and extract the file to the AppManager16\working\jre\bin folder.
- Download the latest timezone database and move it to the AppManager16\working\jre\bin folder.
- Run the tool by executing the command java -jar ziupdater-1.1.1.1.jar -1 file://<path to the tzdata-latest.tar.gz>
- Once the JRE tzdata has been updated to the latest version, the following message will be displayed:
For versions below 16430
Follow the steps given below to download the file:
- Download the zip from this link.
- Extract the zip under the <AppManager_Home>\ folder (Enter 'Yes' to replace all the files during the extraction).
- After the extraction, make sure the jre/bin folder has the tzupdater and tzdata-latest.tar files in it.
Update the time in the JAVA time zone database:
- Stop the Applications Manager service. Open Command Prompt with Administrator Privileges from the \AppManager16\working\jre\bin directory and execute the command given below:
java -jar tzupdater.jar -l "file:///<AppManager_Home>/working/jre/bin/tzdata-latest.tar.gz"-v
Replace <AppManager_Home> with the appropriate Applications Manager folder path.Example:Windows - C:/ManageEngine/AppManager16/working/jre/bin> java -jar tzupdater.jar -l "file:///C:/ManageEngine/AppManager16/working/jre/bin/tzdata-latest.tar.gz"-v
Linux - /opt/ManageEngine/AppManager16/working/jre/bin>./java -jar tzupdater.jar -l "file:////opt/ManageEngine/AppManager16/working/jre/bin/tzdata-latest.tar.gz"-v
- Once the command has been executed successfully, a 'Validation complete. JRE updated to version: tzdata2023c' message will be displayed.
- Start the Applications Manager service and refresh the browser cache. Now check the time zone and the time displayed in Applications Manager (About tab, Alarm time, Availability timeline, reports time, etc.). Please check the details in an incognito window as well.
New to ADSelfService Plus?
Related Articles
Unable to login to Applications Manager Plugin after upgrade
Issue : After upgrading, users are unable to log in to the Applications Manager Plugin. Both auto sign-in and manual login fail. When accessing the Applications tab in the OpManager UI, it redirects to the Applications Manager login page instead of ...How to compare metrics between Applications Manager and Azure Portal
Comparing Metrics Between Applications Manager and Azure Portal Overview Applications Manager collects performance and configuration metrics for Azure resources by querying the Azure APIs. When a discrepancy is observed in the values shown in ...PostgreSQL authentication failure during Applications Manager startup
Problem: Applications Manager fails to start due to PostgreSQL authentication failure and shows the following error: The following errors are observed in the startup log (StartUpLogs_err.log) file, located under <Applications Manager Home>\logs\ ...Maintenance of Applications Manager backend database
Note: Please take complete database backup without fail prior to these steps. I. Applications Manager with PostgreSQL Database. Shutdown all Applications Manager related process as follows: For windows: Open services.msc --> stop ManageEngine ...Applications Manager not starting after upgrade
If Applications Manager is not starting, it could be due to the following: 1. License would've expired. Please apply valid license using updateLicense.bat/updateLicense.sh. Refer this link to know how to apply license. 2. Take a look at the log trace ...