How to transform a SOAP message by using a message map
Marisa Lopez de Silanes 060000JMJ2 Visits (2876)
In WebSphere Message Broker version 8 and IBM Integration Bus version 9, you can use message maps to transform SOAP messages. You can set functions in a graphical data map to transform a SOAP input message into a required SOAP output message.
WebSphere Message Broker Version 8.0 introduces graphical data maps. These message maps replace the previous message map format, and are created as *.map files. If you migrate from an earlier version of WebSphere Message Broker Version 8.0, you can continue using your legacy maps. However, if you need to modify any of your legacy maps, you must convert these legacy message maps into *.map message maps.
Message maps are based on XML schema and XPath 2.0 standards. You can use these maps to transform and enrich messages in your integration solution. These maps offer the ability to achieve the transformation without the need to write code, providing a visual image of the transformation, and simplifying its implementation and ongoing maintenance.
WebSphere Message Broker supports SOAP 1.1 and SOAP 1.2 messages. A SOAP message is encoded as an XML document, consisting of an Envelope element, which contains an optional Header element, and a mandatory Body element. The Fault element, contained in the Body element, is used for reporting errors. Message maps provide a simple way to transform SOAP messages since they are messages encoded as an XML document.
Although using message maps is very intuitive, you might need help creating a map that transforms SOAP messages due to the multi part structure of a SOAP message. This scenario explains how to create a message map that transforms a SOAP message, how to configure the map properties, how to define transformations between the different parts of a SOAP message, how to configure derived types in a message map, and how to define transformations between simple elements, and complex elements such as the conditional transform If.