WebSphere
Message Broker Version
6.0 can coexist with previous versions
and other products. This topic explains the conditions that apply when you
deploy a message set to a Version 2.1 broker.
If you want to deploy a message set to a Version 2.1 broker
that is participating in a Version 6.0 broker
domain, the message set must satisfy the following conditions: - For the logical model:
- The Use Namespaces property of
the message set must not be selected.
- Integer values used in value constraints must be in the signed 32-bit
integer range.
- Datetime values used in value constraints must not specify a time zone.
- For an XML physical format:
- The Strict DateTime checking property
of the message set must not be selected.
- The Daylight Savings Time property
of the message set must not be selected.
- The Encoding Numeric Null property
of the message set must not have the value NULLXMLSchema.
- The Encoding Non-Numeric Null property
of the message set must not have the value NULLXMLSchema.
- For a Custom Wire Format (CWF) physical format:
- The Strict DateTime checking property
of the message set must not be selected.
- The Daylight Savings Time property
of the message set must not be selected.
- The Trailing Skip Count property
must have the value 0 (zero).
- For a Tagged Delimited String (TDS) physical format:
- The Strict DateTime checking property
of the message set must not be selected.
- The Daylight Savings Time property
of the message set must not be selected.
- If the Suppress Absent Element Delimiters property
of a group or complex type is set, it must have the value End
of Type.