This topic contains sections marked as revised for this release
For common envelope message formats, such as SOAP, where both the envelope and the messages that can appear within that envelope have to be modeled, use the Message Mapping editor to select from available messages at points in the model that are defined with Composition="message" and Content validation="open" or "open defined".
Define the mappings by selecting from the allowed constituent messages. For example, in the case of SOAP, the outer level message is called Envelope and has one mandatory child element called Body, which is modeled with Composition="message". If the permitted content of Body is modeled by separate messages Msg1 ... MsgN, define mappings for each separate message (Envelope.Body.Msg1 to Envelope.Body.MsgN).
Content validation | Messages offered |
---|---|
Closed | Messages available in any message sets in the workspace |
Open defined | Any message defined within the current message set |
Open | The Message Mapping editor does not support open or open defined content when the type composition is NOT message |
Mapping an embedded message
When you are working with type composition message, with content open or open-defined (and no children defined), map the embedded message using a submap: