IBM Planning Analytics Tips & Tricks: GMT vs Local Time

May 1, 2018

Did you know that TM1 offers an easy way for you to convert GMT times to local times? Do you get tired of seeing your message log records in GMT? Are you frustrated that you have to convert times from GMT to local time? Does the concept of daylight savings time annoy you? Well, there’s not much that TM1 can do about that last question, but it does offer a solution to the first two.

TM1 contains many of your configuration settings within a file called tm1s.cfg, but there is also a second file called tm1s-log.properties. The properties file is designed to control message levels that are logged by TM1, but it also contains a configuration option to define the TimeZone.

One of the parameters in the tm1s-log.properties file is:

log4j.appender.S1.TimeZone=Zone

where Zone can be set to either GMT or Local.

If the parameter is set to Local, the log messages will have timestamps based on the local time of the machine where the TM1 server is running.
If the parameter is set to GMT, the log messages will have timestamps based on Greenwich Mean Time.
If the parameter is set to something other than GMT or Local (or if the parameter is not set at all), it defaults to GMT.

The properties file must be located in the same folder as the tm1s.cfg file and you must restart your TM1 server after changing this setting.

This setting will help you make your log files easier to read when looking at time stamps within the various lines of the log.

IBM Planning Analytics is full of new features and functionality. Not sure where to start? Our team here at Revelwood can help. Contact us for more information at info@revelwood.com. And stay tuned for more Planning Analytics Tips & Tricks weekly in our Knowledge Center and in upcoming newsletters!

Author

Lee Lazarow

View all posts