Introduction to the "Using a message map to enrich a message with data from a database" scenario

This scenario shows how you can enhance a message in IBM® Integration Bus by using a message map. The data is available in a database system. The data is stored across multiple database tables. All the tables are located within the same database schema.

About this task

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. Message maps offer the ability to transform a message without the need to write code, providing a visual image of the transformation, and simplifying its implementation and ongoing maintenance.

WebSphere Message Broker Version 8.0 also introduces the Select transform that allows you to enrich a message by accessing data located in an external database system. This feature simplifies the programming model. It eliminates the requirement to use a Database node, a JavaCompute node, a .NETCompute node, or a Compute node to access data located in a database. You can design simpler message flows by using a single Mapping node to complete graphically a message transformation that requires data from an external database system.

Note: You can continue to use maps that were created in versions earlier than WebSphere Message Broker Version 8.0. However, if you need to modify any of your legacy maps, or if you want to use the Select transform, you must convert these legacy message maps into .map message maps. For more information about converting maps, see Converting a message map from a .msgmap file to a .map file.

Read the following topics to understand the scenario and the concepts the scenario is intended to demonstrate:

What to do next

Implement the solution. For more information, see Implementing the solution for the scenario to enrich a message with data from a database.