WebSphere Message Broker Version 8.0.0.5 Betriebssysteme: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

Sehen Sie sich die Informationen zur aktuellen Produktversion im IBM Integration Bus Version 9.0 an.

Technical solution

To complete the scenario and successfully transform message data, you must create a message map and customize it based on your SOAP message and transformation requirements. In this scenario, you use the SOAP domain to parse your SOAP message.

You configure a message domain on an input node such as a SOAPInput node to define the parser that WebSphere® Message Broker uses to parse a message. WebSphere Message Broker supplies a range of parsers to parse and write messages in different formats.

WebSphere Message Broker supports SOAP 1.1 and SOAP 1.2 messages.

Depending on the message domain that you configure in your input node, you might have to consider the differences between SOAP 1.1 and SOAP 1.2 when transforming SOAP messages.
Depending on the nodes that you use when you model your message flow or your service operation, and the message domain you configure, you must use a different schema model:
The following table summarizes the different types of nodes and domains that you can use to map a SOAP message and the schema that you must use when you use a message map to transform a SOAP message.
Table 1. Schemas to use when transforming a SOAP message
Message domain   Schema to configure in a message map
SOAP SOAP nodes SOAP_Domain_Msg
XMLNSC SOAP nodes including the SOAPExtract node where the SOAPExtract node is modeled before the Mapping node Schema associated with the SOAP operation
XMLNSC HTTP nodes SOAP 1.1 or 1.2 schema as the root model of the map
XMLNSC MQ nodes SOAP 1.1 or 1.2 schema as the root model of the map

Use this scenario to learn how to create a message map that transforms a SOAP message in a message flow where the Mapping node is connected directly from a SOAPInput node with no SOAPExtract node. For more information, see Implementing the solution.