Before you start:Check that
your current installation of WebSphere® Message Broker is
at a supported level for migration. Details are provided in Supported migration paths.
For the latest details of all supported levels of hardware and software, visit the 
IBM Integration Bus Requirements website.
You
must migrate your queue managers to a supported version of WebSphere MQ before you can migrate your
brokers.
All WebSphere MQ installations
must be at Version 7.5.0.1 for distributed
platforms, and at Version
7.1 for z/OS®. For information about WebSphere MQ migration, see the WebSphere MQ information center. If you are
migrating from WebSphere Message Broker Version
6.1, see Migrating the Version 6.1 WebSphere Message Broker component for more information about how to manage
the WebSphere MQ migration.
If your Version
6.1 configuration
includes publish/subscribe applications,
support has transferred to WebSphere MQ.
You must take additional steps to migrate publish/subscribe information from a WebSphere Message Broker Version
6.1 configuration. Details are
provided in Migrating publish/subscribe information to WebSphere MQ.
To prepare for migration, complete
the following steps.
- Understand the options that are available to install IBM Integration Bus Version
9.0 components
on the same computer as components from previous versions of WebSphere Message Broker.
There
are two different ways to migrate your broker components. In-place broker migration allows you to migrate
your existing broker components immediately to IBM Integration Bus Version
9.0. For more information,
see In-place broker migration.
Parallel broker migration allows you to associate
the application logic on your existing broker with a new, separate Version
9.0 broker. For more information,
see Parallel broker migration.
For more information
about the options that are available for the WebSphere Message Broker and IBM Integration Bus components to coexist, see Coexistence and migration.
- Migrate your WebSphere Message Broker Toolkit resources.
Decide how you will use your existing development resources with Version
9.0. This can be done at
any time in the migration process. You do not have to perform
specific 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 use these resources
with Version
9.0 immediately.
However, some migration actions are performed automatically when you
open or rebuild resources in the IBM Integration Toolkit;
for details, see Migrating development resources to IBM Integration Toolkit Version 9.0.
- Decide how to migrate the WebSphere Message Broker product components.
- Learn about new and changed function in Version
9.0 by reading What's new in Version 9.0?. These changes might affect how
you want to use your migrated components in the future.
- Review the technical changes in behavior in Version
9.0 by reading Behavioral changes in Version 9.0. These changes might affect
your post-migration development tasks.
- Plan your migration of WebSphere MQ to
a supported version. It is a requirement that a supported
version of WebSphere MQ is installed
before you install Version
9.0.
If
you are migrating from WebSphere Message Broker Version
6.1,
publish/subscribe functions are no longer supported in the broker; WebSphere MQ provides this support. If your Version
6.1 applications use the publish/subscribe
communication model, you must migrate your subscriptions to a supported
version of WebSphere MQ before you migrate
your brokers.
- Check the requirements for other products on which Version
9.0 components might depend. If you configured your message flows to use external resources,
such as databases, or event monitoring applications, you might have
to modify your configuration. You can find details of supported versions
of optional products on the IBM Integration Bus Requirements web
page.
Next: After you have planned
your migration, complete the migration tasks by following the instructions
in Migration tasks.
Last updated Friday, 21 July 2017