Configure the Timezone

   Journey Manager (JM) Previously known as Transact Manager (TM). |   System Administrator |   v19.11 This feature was updated in v19.11.


You only need to configure a timezone if you have selected MySQL database during the upgrade of Journey Manager version 18.11 and older to Journey Manager version 19.05 and higher.

Manager version 19.05 and higher comes with the Connector/J 8.0 library for MySQL database. from This library doesn't include the legacy server code timezone any more, so it converts timezone based on the database's timezone. This can cause timezone discrepancy when the database is set up with a timezone different to the server where Manageris installed. Often, the database timezone is UTCUniversal Time Coordinated. Prior to 1972, this time was called Greenwich Mean Time (GMT) but is now referred to as Coordinated Universal Time or Universal Time Coordinated (UTC). It is a coordinated time scale, maintained by the Bureau International des Poids et Mesures (BIPM). It is also known as "Z time" or "Zulu Time"., but it's not always the case. The default database UTC timezone is only valid within the AWS RDS (Database) environment.

To address this, you need to check the timezone of your database and your Manager server. If they are different, you must add the additional JDBC parameter, serverTimezone, to match a Journey Manager instance timezone, so transactions time stamp will be created based on the application server timezone.


Manager prior to version 19.05 uses Connector/J 5.0, which includes legacy server code timezone, so it doesn't matter what the database timezone is and therefore no conversion of time is made.

To configure the timezone:

  1. Log on to the server where Manager is installed.
  2. Open an administrator command shell.
  3. Navigate to /data/avoka/transact/manager/server/standalone/configuration/.
  4. Open the standalone.xml file.
  5. Find the <connection-url> property for both FormCenterDS and TransactionHistoryDS datasources.
  6. Check Manager's system info to find out its timezone, which can be then applied as the serverTimezone in the <connection-url>.
  7. For on premise installations only, check the database timezone. If the two timezones are different, then you have to add the serverTimezone, equal to the timezone matching the Manager server as you have found above, to the connection-url. However, if the two timezones are the same, then DO NOT apply the change to the connection-url and proceed without it.
    For example, for the Manager version 19.11 server installed in Brisbane, Australia, use the following value:
  8. Save the standalone.xml file.