This scenario explains how to convert a message map to a graphical data map, how to check that all transforms work as intended in the mapping solution, and explains some of the logic of the mapping so that you can make decisions about your mapping solutions.
The scenario message map contains a simple transformation that takes an input generic message with details of a person and transforms it to a message required by a member database system that adds a member record for the person. In the converted map, you can see automatically converted transforms, and transforms that must be configured manually.
The scenario prepares you for converting your message maps so that you can edit them in later versions of WebSphere® Message Broker or WebSphere Message Broker Toolkit, and enables you to make updates to your mapping solutions.
If you import your message map solutions from WebSphere Message Broker Version 6.1 or Version 7.0, you can still compile and deploy message flows that use message map (.msgmap) files. However, in WebSphere Message Broker Version 8.0 and later, message map files are accessible only in read-only mode, and cannot be modified. For example, you cannot take advantage of deploying broker resources as source, so if you continue to use message maps, you cannot deploy reusable subflows independently from all flows that are using them.
To be able to take advantage of editing, and the transforms available by using the Graphical Data Mapping editor in WebSphere Message Broker Version 8.0 and later, you must use a graphical data map (.map) file type.
The Graphical Data Mapping editor is based on XML schema and XPath standards so that you can use the full set of XPath 2.0 expressions for controlling and implementing transformations. The Graphical Data Mapping editor provides a greater range of transforms compared to the Message Mapping editor. The Graphical Data Mapping editor also includes developer accelerators, such as the Auto map wizard, which automatically creates transforms based on correlation of the names of input and output elements, and content assist for paths and expressions. The WebSphere Message Broker Version 8.0/WebSphere Message Broker runtime has a dedicated Java based runtime execution engine, enabling the map execution to benefit from Java JIT optimization.
To observe what changes take place during conversion, review Technical solution.