Migrating XML maps

The underlying structure of XML maps was changed between releases of WebSphere Integration Developer. Use the migration wizard or the quick fix feature to migrate your maps to the current version.

About this task

XML maps that were created in versions of WebSphere Integration Developer earlier than version 7.0.0.3 must be migrated to the current version for the following reasons:

Maps that were created in versions 6.0.x and have a file extension of .xmx must be migrated to the current version if you want to edit them or if you want to run them in the lazy business object parsing mode.
Maps that were created in versions earlier than 7.0.0.3 and have the file extension of .map must be migrated to the current version if you want to run them in the lazy business object parsing mode.

When you import existing maps from previous versions into IBM® Integration Designer V8.5.6, the older maps are detected and a migration wizard is launched to help you migrate the maps to the current version. The migration wizard handles the migration for both situations that were described previously, and no further action is required after migration is completed. If the maps have the .xmx extension, the .xmx files are deleted and a .map file is created for each .xmx file. If the maps have the .map extension, the existing .map files are updated.

Note: Variable names used in applications of earlier versions of Integration Designer might have changed. You must update these manually in the applications after the maps are migrated.

If you choose to exit the wizard and migrate the maps later, you can launch the wizard by selecting the Run workspace migration action from the Migration Results view.

Tip: If the Migration Results view is not visible, you can bring it into perspective by selecting Window from the main menu and choosing Show view > Other. Then, from the Show View page, select the Migration Results view.

What to do next

If you do not migrate the maps using the migration wizard, and you choose to use the Configure Business Object Parsing Mode option to set the business object parsing mode of a module or library to lazy, the associated older maps are automatically migrated for you during this action. However, if you manually change the business object parsing mode to lazy by editing the properties of the module or library, older maps are not migrated automatically and you will see errors in the problems view for the associated older maps. When you see such errors in the problems view for .xmx or .map files, use the quick fix function to migrate the maps as follows:

Right-click the error message and select Quick Fix.
Optionally choose to migrate all the maps, and click Finish.