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
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:
- Define schema models for any xsd:any element in your input or output structures.
- Run the conversion process. For more information, see Converting a message map from a .msgmap file to a .map file.
- 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.
- 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.
- Deploy and test your message flow. For more information, see Deploying resources.