IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Using message maps

You can use a message map to graphically transform input messages into a required output message, using the functions specified in the map; to enrich the output message with data from a database; to route the output message based on the input message values and additional database content; and to modify data in a database system. You can use drag actions to make connections, select transforms, and build logic to transform your message data without programming.

A message map is the IBM® Integration Bus implementation of a graphical data map. It is based on XML schema and XPath 2.0 standards.

A message map offers the ability to achieve the transformation of a message without the need to write code, providing a visual image of the transformation, and simplifying its implementation and ongoing maintenance.

You can use a message map to perform any of the following integration requirements graphically:

Transform a message: You can use a message map to graphically transform a message assembly, message body, and properties, according to the transforms and XPath functions defined in the message map. The input and output data must be defined by a message model, which defines the structure of the data and provides information about the data type.
Enrich a message with data available in an external database: You can use a message map to enrich, or conditionally set the output message with data from a database table. The table data structure must be defined to the message map, and an SQL where clause can be used to select specific rows. The resulting row data is presented as an additional input in the message map, according to the database schema.
Modify data located in an external database.
Route a message based on content: You can use a message map to graphically route a message. You can modify the local environment tree to set a dynamic message destination.

Read the following sections to learn how to design, create, configure, and troubleshoot a message map and its associated resources:

Graphical data maps offer the ability to achieve the transformation of a message without the need to write code, providing a visual image of the transformation, and simplifying its implementation and ongoing maintenance. Depending on the data transformation reusability and manageability requirements, you can use a message map, a submap, a local map, or a legacy message map. For more information, see Graphical Mapping overview.
You can create a graphical data map, a message map, a submap, or a legacy message map to transform a message without the need to write code, providing a visual image of the transformation, and simplifying its implementation and ongoing maintenance. For more information, see Creating a message map.
You can edit a message map by using the Graphical Data Mapping editor. For more information, see Editing message maps.
You can use advance features to transform your messages. For more information, see Advanced editing in a message map.
You can diagnose and solve problems that you encounter when using a message map. For more information, see Troubleshooting graphical data maps.
You can compile and deploy a legacy message map in IBM Integration Bus. However, if you need to modify the legacy message map, you must first convert the legacy message map to a message map. For more information, see Using or converting legacy resources into message maps.

br28800_.htm |

Last updated Friday, 21 July 2017