Upgrading to Message Brokers Toolkit Version 5.1

Before you upgrade to Message Brokers Toolkit Version 5.1, see Different versions of the Message Brokers Toolkit for information about compatibility of Message Brokers Toolkit Version 5.1 with WebSphere Studio Application Developer Integration Edition. There are circumstances under which you must not upgrade from Message Brokers Toolkit Version 5.0 to Version 5.1.
Migration to Message Brokers Toolkit Version 5.1 is silent, except for user defined extensions. Before you upgrade to Message Brokers Toolkit Version 5.1, consider the following:
Coexistence
Message Brokers Toolkit Version 5.0 and Version 5.1 cannot coexist on the same machine. Start of changeIf you want to install Message Brokers Toolkit Version 5.1 on a system on which you have already installed Message Brokers Toolkit Version 5.0, you must first uninstall Message Brokers Toolkit Version 5.0.End of change
Development resources
Message Brokers Toolkit Version 5.1 can use Message Brokers Toolkit Version 5.0 development resources. Message Brokers Toolkit Version 5.0 development resources that are viewed in Message Brokers Toolkit Version 5.1 remain in Version 5.0 format until they are modified and saved in Message Brokers Toolkit Version 5.1.
However, when development resources are in the Version 5.1 format, you can no longer use them in Message Brokers Toolkit Version 5.0. We strongly recommend that before you upgrade to Message Brokers Toolkit Version 5.1, you store and version your Version 5.0 development resources using Eclipse compliant repositories such as CVS.
You cannot share development resources between Message Brokers Toolkit Version 5.0 and Version 5.1. For example, if you have separate development and production systems, you cannot use resources created on a development system that uses Message Brokers Toolkit Version 5.1 on a production system that uses Message Brokers Toolkit Version 5.0.
You can migrate WebSphere MQ Integrator Broker Version 2.1 development resources, such as message flows and message sets, to Message Brokers Toolkit Version 5.1 using the mqsimigratemsgflows command and the mqsimigratemsgsets command.
Deployment resources
You can share deployment resources (such as BAR files) between Message Brokers Toolkit Version 5.0 and Message Brokers Toolkit Version 5.1. For example, you can create a Version 5.1 BAR file that contains Version 5.0 compiled message flows and message dictionaries. Similarly, you can deploy BAR files created in Message Brokers Toolkit Version 5.1 using Version 5.0, and vice versa.
You can administer the broker runtime using either Message Brokers Toolkit Version 5.0 or Message Brokers Toolkit Version 5.1. Therefore, if you upgrade to Message Brokers Toolkit Version 5.1, you do not have to upgrade your development and administration machines at the same time.
User-defined extensions
You must migrate user-defined extensions to Message Brokers Toolkit Version 5.1. For more information on how to do this, see Migrating a user-defined node from a 5.0.x workbench to a 5.1.x workbench.
Related concepts
Different versions of the Message Brokers Toolkit
Related tasks
Migrating a user-defined node from a 5.0.x workbench to a 5.1.x workbench
Related reference
mqsimigratemsgflows command
mqsimigratemsgsets command