You can define a message that embeds other messages to create a multipart message. To achieve this, you should include a complex type or group in the embedding message and define it with the property Type Composition set to message. You can define this complex type or group to contain one or more messages, all of which you must define in the same message set as the outermost message.
The identity of a message can be specified using the message set Message Type Prefix property. This provides the mechanism to specify an absolute or relative path to the innermost message from the outermost.
In a CWF messaging environment, there is no mechanism to directly identify within the actual message bitstream which embedded message appears within the input message. However, if you generate a message dictionary for deployment to WebSphere Business Integration Message Broker this can be specified in one of two ways:
CWF can only use the Message Type property to resolve the hierarchy of the first embedded message structure. If you have defined the outer message to contain more than one complex type that defines embedded messages, you must resolve the message choice within the second and subsequent complex types using ESQL.
Related Concepts
Ways to create message definitions
Multipart messages
Custom wire format - Relationship to the logical model
Related Tasks
Working with a message set
Working with physical properties
Adding a Custom Wire Format (CWF)
Configuring Custom Wire Format (CWF) properties: Message sets
Removing a physical format
Related Reference
Custom Wire Format physical properties for message model objects
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ad00782_ |