Messages with Four Character Timezone Format Such As AEST or CEST Fail in RIB

(Doc ID 2417276.1)

Last updated on JULY 02, 2018

Applies to:

Oracle Retail Integration Bus - Version 13.2 and later
Information in this document applies to any platform.


The RIB XML Schema Definition (XSD) has the ribMessageDateTime field with a limitation of three characters to represent timezone format. If the timezone passed is of 4 characters such as AEST or CEST in a XML, they are failing.

In RibMessages.xsd, the below is specified :

But when the XML is generated, it gets below kind of values for some time-zones as there are four characters based on Daylight saving info:

For example:
<publishTime>2016-09-27 13:20:13.053 AEST</publishTime>
<publishTime>2016-09-23 15:41:00.322 CEST</publishTime>

Since AEST / CEST is of 4 characters, but the XSD has given only [A-Z]{3} restriction, such messages are failing while parsing by other systems which refer the XSD and try to load the XML.




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms