IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Building mediation flows > Transforming messages

Create Mapping transformations

When the message types of source and target operations do not match, you need to transform the source message type so that the target operation can receive it and you do this with the Mapping transformation primitive which uses a map file to map source and target message types.

In the Mediation Flow editor, you cannot connect primitives or nodes whose message types are different; you will see an error on the input terminal of the target node indicating that the terminal types are incompatible. In this case, you need a Mapping transformation primitive, as shown in the following image:

The Mapping transformation primitive uses a map file that contains the information required to map between two message types. You can select an existing map, and optionally edit it, or create a new one using the XML Map Editor. An XSL file is automatically generated for the map file and used at run time.


If : If you create a map and set its input and output types, the types you have selected will be present at the input and output terminals of the primitive regardless of the wiring. The same applies when using a previously created map. To reset the input or output message type, right-click the terminal and select Reset Message Type. The map will have to be recreated because it is not refactored when the terminal type changes.

Transforming messages