What type of graphical data map I need to use in my integration solution?
Marisa Lopez de Silanes 060000JMJ2 Visits (1424)
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. So which one should I use?
Let's look first into the options available!!!
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. Also, IBM's DFDL for text and binary industry and custom message formats is based on XML schema so you can also transform those in a graphical data map.
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 message map.
Submaps enable you to use a set of mapping functions in multiple message 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.
A local map is a subset of data transformations between input elements and output elements that are part of a message 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 message map.
Local maps provide a way of breaking up a large message map into nested groups of mapping elements.
You can use local maps to simplify the overall message map presentation. You can structure complex data transformations into nested groups that are easier to manage and implement.
Legacy message maps
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.
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.
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.
So which one to use?
Use the following table to identify the type of map that you must create when transforming data graphically in the Graphical Data Mapping editor:
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.