The
procedures for migrating a queue manager from Version 7.1 to Version 7.5 are
listed by platform.
Before you begin
If you have installed early support program code
on the server, you must delete all the queue managers created with
the installation. Uninstall the code before proceeding with installing
the production level code.
About this task
Migration is a complex task. It goes
beyond upgrading the IBM® WebSphere® MQ code.
The term upgrading
applies to the process of installing a new
code level. Migrating
refers to the process of upgrading code
and the to the task of migrating queue manager data, such as messages,
queues, channels, and other resources. Migrating queue manager data
is automatic.
Procedure
Queue manager migration follows this overall
plan:
- Review the WebSphere MQ system requirements for Version 7.5; see System Requirements for IBM WebSphere MQ.
- Back up your system. In particular back
up the queue manager.
You cannot run a queue manager
on a previous version of IBM WebSphere MQ,
once you start the queue manager on the new version.
- Carry out the platform-specific migration
or upgrade procedure.
- Upgrade IBM WebSphere MQ.
- Customize the configuration.
- Verify the installation.
- Create a queue manager to verify the installation. Verify applications
and management tasks work with the new level of IBM WebSphere MQ before migrating existing queue
managers. Consult Characteristics of different types of upgrade to help you decide on the
extent of testing required.
- Perform any additional migration tasks
that are required.
- If the queue manager is a member of a queue manager
cluster, or queue-sharing group, migrate the other members of the
cluster or group.
- Perform any additional migration tasks
that are required.
- If you are using publish/subscribe, you must migrate the publish/subscribe
broker.
- If the queue manager is a member of a queue manager
cluster, or queue-sharing group, migrate the other members of the
cluster or group.