Why is the Concept DateTime property not storing TimeZone in TIBCO BusinessEvents (BE)?

book

Article ID: KB0082321

calendar_today

Updated On:

Products	Versions
TIBCO BusinessEvents Enterprise Edition	-
Not Applicable	-

Description

Description:
Title:
Why is the Concept DateTime property not storing TimeZone in TIBCO BusinessEvents (BE)?

Description:

You may notice a DateTime property in a concept isn't storing timezone information (in certain instances) while an Event DateTime property does, yet Constructors for both Concepts and Events accept a Calendar in their respective constructors.
Symptoms:
Here is an example log:

Info [$default.be.mt$.Thread.3] - [user] [inference-class] Scheduled time interval received

Info [$default.be.mt$.Thread.3] - [user] [inference-class] Next time interval event has been scheduled for 2015-09-10 16:36:05.000GMT-04:00

Info [$default.be.mt$.Thread.4] - [user] [inference-class] Scheduled time interval received

Info [$default.be.mt$.Thread.4] - [user] [inference-class] Next time interval event has been scheduled for 2015-09-10 16:37:05.000GMT-04:00

Info [$default.be.mt$.Thread.5] - [user] [inference-class] Command request received

Info [$default.be.mt$.Thread.5] - [user] [inference-class] The Controller's status has been set to 'Suspended'

Info [$default.be.mt$.Thread.6] - [user] [inference-class] Scheduled time interval received

Info [$default.be.mt$.Thread.7] - [user] [inference-class] Command request received

Info [$default.be.mt$.Thread.7] - [user] [inference-class] The Controller's status has been set to 'Running'

Info [$default.be.mt$.Thread.7] - [user] [inference-class] Next time interval event has been scheduled for 2015-09-10 20:37:05.000GMT

Info [$default.be.mt$.Thread.8] - [user] [inference-class] Scheduled time interval received

Info [$default.be.mt$.Thread.8] - [user] [inference-class] Next time interval event has been scheduled for 2015-09-10 20:38:05.000GMT+00:00 -- No time zone information.

Cause:
The missing timezone information is due to use of the wrong function. Use of DateTime.translateTime(dt, null) function to translate the datetime to current timezone with the BE catalog format.

XPath functions(e.g. drag and drop through XPath edition, or use Functions provided in XPath) use the GMT format for datetime however BE catalog functions use the region format.

Environment

Product: TIBCO BusinessEvents Version: 5.x OS: All Supported Operating Systems --------------------

Resolution