Planning the conversion of a legacy message map

Before you convert a legacy message map, review this section to help you plan the migration.

About this task

If you want to deploy legacy message maps (.msgmap format) in IBM® App Connect Enterprise, you must first convert them into message maps in .map format, which the IBM App Connect Enterprise Mapping node can consume.

Legacy message maps, which have not been modifiable since WebSphere® Message Broker Version 7, could be deployed in later versions of WebSphere Message Broker; however, they cannot be deployed in IBM App Connect Enterprise until they have been converted.

Procedure

Complete the following tasks to plan the conversion of a legacy message map to an IBM App Connect Enterprise message map:

  1. Verify that all the projects that include resources used by the legacy message map are available in your workspace, and the project dependencies are defined.

    The conversion process needs access to all projects that include resources used by the legacy message map, so that it can convert your map transformations automatically.

  2. Identify the legacy message map resources used in your transformations:
    1. Check the input and output structures of the legacy message map.
      • Are you doing transformations that include the local environment tree?
      • Are you doing transformations that include data structures with xsd:any elements?

      For more information, see Converting a legacy message map that includes transformations of the local environment tree or xsd:any elements.

    2. Check your transformation for any of the following types:

What to do next

  1. Define schema models for any xsd:any element in your input or output structures. You can also use the Add user-defined function to qualify the xsd:any element. This approach is recommended when the xsd:any element only involves a small number of elements. If you reuse the same structure in multiple maps, it is recommended that you create a schema model.
  2. Run the conversion process. For more information, see Converting a message map from a .msgmap file to a .map file.
  3. Review the newly created message map and complete the post-conversion tasks. For more information, see Managing conversion warnings on converted legacy message maps and Managing conversion errors on converted legacy message maps.
  4. Update the message flow that includes the legacy message map to include the new Mapping node and reference the newly created message map. For more information, see Replacing a legacy Mapping node.
  5. Deploy and test your message flow. For more information, see Deployment rules and guidelines.