All containers created within the CirrusGrid PaaS utilize the UTC timezone by default. However, in case of necessity, you can easily change it to any preferable one with the help of the TimeZone Change add-on. Follow the steps provided within the linked section to switch timezones on any of your instances.
Alternatively, you can apply the changes manually. For example, all of the Java and PHP application servers at CirrusGrid are supplied with special timezone packages, which includes data about the history of local time in different locations around the globe and current timezone rules. This information is required for software, running inside the appropriate containers, and is regularly updated within the corresponding server builds in the confines of the newly released CirrusGrid Platform versions.
Besides that, you can instantly update the timezone rules manually if necessary, or change the currently used TZ, based on the preferred location. So, below we’ll reveal some specifics of the timezone data management at CirrusGrid for the application servers of the programming languagesmentioned above:
TimeZone Change add-on can be installed on top of any of your environments, changing the timezone for all of the comprised containers in a matter of minutes.
1. Before proceeding to installation, let’s check the timezone on our target container using the date command.
As you can see, the UTC zone is used (default for all CirrusGrid-managed containers).
2. Go to the TimeZone Change add-on repository within the CirrusGrid JPS Collection at GitHub. Copy a link to the manifest.jps file and import it via the dashboard: https://github.com/jelastic-jps/time-zone-change/blob/master/manifest.jps
Tip: Based on your particular hosting provider settings add-on can be available via CirrusGrid Marketplace.
3. Within the opened frame, select the target Environment and type the preferable TimeZone Name (list of time zones) for it.
Click Install to apply changes.
4. After add-on installation, you can verify the timezone change by running the date command one more time.
As you can see, the system time was successfully switched to the EDT (Eastern Daylight Time).
The timezone rules within Java compute nodes are delivered by means of the dedicated TZdata package, comprised in each appropriate container. Follow the instructions below to:
Despite the fact the newest TZdata package edition is integrated into a node during its creation, after some time it becomes outdated due to periodical changing of the intrinsic data. Thus, old containers may require the corresponding updating from time to time (particularly, in order not to be recreated each time this is needed). For that, a special embedded TZUpdater tool is used, intended for keeping your timezone data accurate and up-to-date. It is fairly simple to use and can be run with a single-line command; you just need to:
1. Connect to your Java environment via SSH, e.g. using the embedded Web SSH client:
2. Once inside, you can check the currently used TZdata version by executing the following string:
java -jar /usr/java/utils/tzupdater.jar -V
3. If you’ve observed the corresponding package in the chosen container is outdated, you can update the timezone information using the embedded TZUpdater tool:
java -jar /usr/java/utils/tzupdater.jar -u
As you can see, getting the latest timezone package version for Java-powered server is a really simple operation with CirrusGrid.
Now, let’s discover how to check and change the application server’s local time – we’ll consider this on the example of a Tomcat 9 server.
1. Let’s set the current timestamp to be shown at the server start page – this will help to quickly ensure that new timezone settings have been successfully applied and are relevant for now.
For that, paste the code below instead of the /opt/tomcat/webapps/ROOT/index.jsp file default content (the easiest way is to use the inbuilt CirrusGrid File Manager for that).
2. Save the changes and Open your environment in browser with the corresponding button to see the current server time, like:
3. In order to change the actual timezone for a particular server, perform the following:
Note: Depending on a particular application server used, the location of this file may vary:
for GlassFish Access the GF admin panel, go to the Configurations > gfcluster-config (or server-config for GF 4) > JVM Settings > JVM Options section and click the Add JVM Option button. Paste the corresponding string (e.g. -Duser.timezone=US/Pacific) within the appeared input field:
for WildFly Switch to the /opt/wildfly/bin/standalone.conf file (or, if a server was scaled horizontally, refer to the /opt/wildfly/bin/domain.conf config) and declare the corresponding variable using the following format: export JAVA_OPTS=”-Duser.timezone=US/Pacific”
4. Save the made adjustment and Restart your application server in order to apply new settings.Now, just refresh the server start page or click Open in Browser again to see the updated local time:
Great, new rules were applied successfully. In such a way, you can set any desired time location for your server without any problems, in a matter of minutes.
Managing of the timezone settings at Jelastic PHP application servers (Apache and NGINX) is performed within the [date] section of the main PHP configuration file – php.ini.
To access it, you need to click the Config button next to the required node. In the opened tab, locate the appropriate file within the file tree (or use the shortcut in the Favorites list to the left) and find the above-mentioned section:
As you can see, this section comprises two options, which can be used to:
The first setting allows you to use the alternative external timezone database (namely – the Olson one) in case the internal one is outdated.
For that, simply uncomment the appropriate extension through removing the first semicolon symbol, Save the made alteration and Restart your app server.
Now, if you click Open in browser and scroll until the date section of the opened phpinfo() page, you’ll see the latest timezone package version listed, with the denotation the external DB is used:
The second option in the [date] section is intended for defining the current timezone location (by default it points to the UTC zone) of a node. For showing this on a real example, we’ll modify the default server’s start page (the /var/www/webroot/ROOT/index.php file) with the following code:
Now, if Saving the updated file and clicking Open in browser, you’ll see the timestamp output:
Return to the CirrusGrid dashboard and specify the desired timezone as a value for the date.timezone parameter within the php.ini file (e.g. Australia/Sydney in our case).
Again, Save your new configurations, Restart the corresponding PHP compute node and refresh the page with current time shown:
That’s it! As you can see, the timezone was successfully changed and now corresponds to a required location.
Powered by BetterDocs
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.