Timezone considerations
For situations where it is not possible to follow the best practice of setting the system timezone to UTC, support was added in FTM V3.0.0 to maintain the database in UTC. The previous behavior of FTM regarding timezones remains available. Changes related to improved timezone support are shown in the following list:
- The database can be set to maintain UTC or to maintain the previous behavior by following the instructions in Setting the database time zone.
- For information about converting message timestamps to and from UTC, see ESQL timezone mapping functions.
- Timestamps can be adjusted to be viewed in the timezone of the OAC user. For more information, see Date and time search criteria and Setting user preferences.
- Support was also added for configuration modeling in a timezone that is different than where FTM is running. For more information, see Using the Application timezone.
Notes:
- For the Linux and UNIX operating systems
- For full timezone support in IBM® Integration Bus, use Continent/City notation (Olson tz ID) to set the TZ system variable. For example, set TZ to Europe/London to make London, England the timezone, or set it to America/New_York to make New York, America the timezone. For the most recent list of accepted timezone names, see Time Zone Database.
- For z/OS® systems
- Because the timestamp conversion API calls Java™ functions, you must correctly set the timezone environment variable for the z/OS UNIX System Services subsystem. The variable must either be set for the user that is running the WebSphere® Message Broker or IBM Integration Bus process, or be set globally as the default. For more information, see Setting your local timezone.
