Decide how you want to use your existing resources with WebSphere Message Broker Version
6.1. Except for user-defined extensions and mapping files,
you do not need to perform any tasks to migrate your development and deployment
resources, such as message flow files, message set definition
files, ESQL files, XML Schema files, and broker archive files. You can
start using these resources with WebSphere Message Broker Version
6.1 immediately.
All Version 5.0 and Version
5.1 user-defined
node projects must be upgraded to work with Message Broker Toolkit Version 6.1 . Upgrade a project by cleaning it: click .
When you clean a project, the extension point that is required by Version 6.1 to
compile the ESQL files contained in the user-defined extension is created
in the project plugin.xml file.
After
you have migrated Version 5.0 mapping files (.mfmap)
to Version 6.1 mapping files (.msgmap) using
the mqsimigratemfmaps command,
edit them in Message Broker ToolkitVersion 6.1 .
There is no migration tool to migrate a mapping that is called from ESQL.
After
you start using your current resources in the Message Broker Toolkit Version 6.1, reeuse of those resources is subject to restrictions
in Message Broker Toolkit Version 5.0 or Version
5.1. For more information, see Conditions for using migrated resources with previous versions of the Message Broker Toolkit