Context for the scenario to transform SOAP messages
This scenario explains how to create a message map that transforms a SOAP message, how to configure the map properties, and how to define transformations between the different parts of a SOAP message.
Your company has implemented an AddressBook service that is used by different departments in different countries in your organization. This service allows your employees to obtain a client's mail address or to save a new client's mail address.
The company uses IBM® Integration Bus to develop and manage a number of integration solutions that transform and communicate data between source and target systems. In order to make the service reusable by multiple applications, you design an application responsible for the transformation of the different data formats between the requesting application and the AddressBook service. The AddressBook service is a SOAP based service that stores a new address or returns an address to the user. You use a message map to define how to transform the SOAP message based on the operation that your user requests.
- Transform data by using a message map in a Mapping node.
- Transform data by using ESQL in a Compute node.
- Transform data by using an XSL transform in a XSLTransform node.
- Transform data by using Java™ in a JavaCompute node.
- Transform data by using .NET applications on Windows integration nodes.
- You can use a Mapping node to transform the incoming message, create new output messages, and interact with information in a database by using a graphical data map.
- You can use the XSLTransform node to transform the incoming XML message by using an XSL style sheet.
This scenario demonstrates how to transform SOAP messages by using a message map that you create, configure and assign to a Mapping node.