This topic contains sections marked as revised for this release

WebSphere Message Brokers
File: ar25188_
Writer: Cerys Giddings

Task topic

This build: July 31, 2007 21:36:14

Transforming a SOAP request message

SOAP is an XML-based language defined by the W3C for sending data between applications. A SOAP message comprises an envelope containing:
  • An optional header (containing one or more header blocks)
  • A mandatory body.

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).

For complex type elements with type composition message, the Message Mapping editor follows these rules:
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:

  1. In the main map, expand the levels (both source and target) of Envelope and Body until you find the wildcard message, and select this on both the source and target sides.
  2. Right-click either the source or target and click Create New Submap.
  3. From the dialog box, select a source (for example reqmess) and a target (for example rspmess).
  4. With the submap open in the Message Mapping editor, make the appropriate mappings between the source (reqmess) and target (rspmess).
Related concepts
Message model objects: wildcard attributes
Message mappings overview
Related tasks
Creating a new submap for a wildcard source
Related reference
SOAP applications
Wildcard element properties
Wildcard attribute properties
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:36:14

ar25188_ This topic's URL is: