WebSphere Message Broker Version 8.0.0.5 Betriebssysteme: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

Sehen Sie sich die Informationen zur aktuellen Produktversion im IBM Integration Bus Version 9.0 an.

Technical solution

To complete the scenario, you must convert a message map, and verify the transform behavior of the converted map.

Use the scenario steps to go through the conversion process, review the new map to check the created transform logic, and if necessary, complete any required manual steps to provide equivalent behavior for the converted transform.

When you convert a message map, the transform logic is automatically converted so that it becomes valid behavior for a graphical data map.

During conversion, the transforms can change in the following ways:

Most transformations that are used in .msgmap files automatically convert to working transforms in a .map file. However, in complex maps you might need to make changes to the graphical data map, or check that the behavior matches what you expect after the conversion.

If you experience problems with the behavior of a converted transform in the runtime, it is always best to try to resolve those problems in the mapping, by using the Graphical Data Mapping editor, rather than create a workaround in the runtime. This ensures that your mapping solutions remain robust for future versions of WebSphere® Message Broker or WebSphere Message Broker. If the problem is not resolvable in the mapping, then contact your IBM service provider.

You cannot convert a .map file back into a .msgmap file, but a backup of the file is created when you start conversion. The backup file name is in the format filename.msgmap_backup. To restore your message map, rename the file extension.

The following topics explain the initial configuration that is used to start the scenario, and the target configuration that is the result of following the steps that are documented in the scenario: