WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Planning the conversion of a legacy message map

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

You can compile and deploy legacy message maps and legacy message flow nodes in WebSphere® Message Broker Version 8 and later versions. However, if you need to modify any of these resources, you must convert them into message maps that the new Mapping node consumes.

Complete the following tasks to plan the conversion of a legacy message map to a 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 to be able to convert automatically your map transformations.

  2. Identify the legacy message map resources used in your transformations.
    1. Check the input and output structures to 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 type of transformations:
  1. Define schema models for any xsd:any element in your input or output structures.
  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 WebSphere Message Broker Version 7 Mapping node.
  5. Deploy and test your message flow. For more information, see Deploying resources.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:27


Task topicTask topic | Version 8.0.0.7 | br40819_