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

See information about the latest product version

Creating a message map

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.

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. You can use a message map to graphically transform, route, and enrich a message. You can use a message map 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 submap is a reusable form of graphical data map. Submaps enable you to use a set of mapping functions in multiple graphical data maps to transform a common set of elements in the input object to the output object. You can use a submap to reuse common data transformations. You can reuse submaps in other products that support graphical data maps.

Note: If you plan to reuse data transformations across different products, read Guidelines for developing reusable graphical data mapping assets.

A local map is a subset of data transformations between input elements and output elements that are part of a graphical data map. You define a local map by creating a Local map transform in a message map. A local map is not an independent resource. There is no physical file associated with a local map. The scope of a local map is the message map. A local map is processed with the graphical data map. Local maps provide a way of breaking up a large graphical data map into nested groups of mapping elements. You can use local maps to simplify the overall graphical data map presentation. You can structure complex data transformations into nested groups that are easier to manage and implement.

A legacy message map is a message map created as a .msgmap file in earlier versions of WebSphere® Message Broker Version 8, for example in WebSphere Message Broker Version 7. You can compile and deploy a legacy message map in IBM Integration Bus. However, if you need to modify a 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.

Note: WebSphere Message Broker Version 8 introduces graphical data maps. These message maps replace the previous message map format, and are created as .map files.

Choose any of the following options to create a graphical data map:

You can use the following table to identify the type of map that you must create when transforming data graphically in the Graphical Data Mapping editor:

Table 1. Types of map based on design requirements
  Recommended use Type of resource Supported in IBM Integration Bus
Message map Transform messages graphically .map file Yes
Submap Reuse of common data transformations .map file Yes
Local map Reduce complexity reading and managing a Message map No file. It is embedded within a Message map Yes
Graphical data map Share graphical data maps across different software products .map file Yes
Legacy message map Solutions migrated from earlier versions of IBM Integration Bus .map file Supported for compatibility with earlier releases of IBM Integration Bus. (See note below.)
Note: You can use a legacy message map, but you cannot modify it in IBM Integration Bus. These type of maps are maintained for compatibility with earlier versions of IBM Integration Bus.

You can see the message map in the Application Development view displayed under a Maps category, and organized by namespace.

After you create a graphical data map, edit the map, and define transformations between the input message and the output message. For more information, see Editing message maps.

cm28000_.htm | Last updated Friday, 21 July 2017