[UNIX, Linux, Windows, IBM i]

Migration methods on IBM MQ for Multiplatforms

There are three main methods of migrating from one release to another: Single-stage migration (called a slip installation on IBM® i), side-by-side migration, and multi-stage migration. Multi-stage migration is not an option for IBM i.

Important:

If you are migrating to IBM MQ 9.1 from IBM WebSphere® MQ 7.5 or earlier, you must first migrate to an interim version. See Migration paths.

Single-stage migration

Single-stage migration is the term that is used to describe replacing the only installation of IBM MQ on a server, with a later release.

The advantage of single-stage migration is that it changes the configuration of a queue manager on the earlier version as little as possible. Existing applications switch from loading the libraries from the earlier version, to loading the libraries of the later version, automatically. Queue managers are automatically associated with the installation on the later version. Administrative scripts and procedures are affected as little as possible by setting the installation to be the primary installation. If you set the installation of the later version to be the primary installation, commands such as strmqm work without providing an explicit path to the command.

Of the three approaches, single-stage migration preserves the greatest number of existing scripts and procedures for running IBM MQ. However, the other migration approaches support a gentler transition to the new version, which can reduce the overall impact on users.

Figure 1. Single_stage migration: earlier version installed with connected queue managers and associated applications
Graphic showing the earlier version of the product installed.
Figure 2. Single_stage migration: later version installed but queue managers not yet connected and applications not yet associated
Graphic showing the later version of the product installed, with the earlier version uninstalled and the queue managers and applications still to be associated with the later version.
Figure 3. Single_stage migration: migrated queue managers connected to and applications associated with later version
Graphic showing the later version of the product installed and the queue managers and applications associated with the later version.
For more information about single-stage migration, see:

Side-by-side migration

On UNIX, Linux® and Windows, side-by-side migration is the term that is used to describe installing a later version of IBM MQ alongside an older version on the same server. The side-by-side migration scenario sits half-way between the single-stage and multi-stage migration scenarios and is based on the following premise:
  • Install additional IBM MQ code alongside existing installation while queue managers are still running.
  • Move queue managers one at a time to the new installation.
  • Migrate and test applications one at a time.

During the installation and verification of the later version of IBM MQ, queue managers continue running, and remain associated with the older version of IBM MQ.

Figure 4. Side-by-side migration: later version installed but queue managers still connected to and applications still associated with earlier version
Graphic showing the later version of the product installed alongside the earlier version, but with the queue managers and applications still associated with the earlier version.

When you decide to migrate queue managers to the later version of IBM MQ, you stop all queue managers, migrate them all to the later version, and uninstall the earlier version of IBM MQ.

Figure 5. Side-by-side migration: migrated queue managers connected to and applications associated with later version
Graphic showing the later version of the product installed alongside the earlier version, and with the queue managers and applications associated with the later version.

The advantage that the side-by-side migration has over the single-stage migration is that you can install and verify the later IBM MQ installation on the server before you switch over to it.

Although side-by-side migration is less flexible than multi-stage migration, it does have some advantages over the multi-stage approach. With the side-by-side approach, you can assign a later version of IBM MQ to be the primary installation. With the multistage approach, and one version of IBM MQ set as the primary installation, many applications restart without having to reconfigure their environment, as IBM MQ commands work without providing a local search path.

For more information about side-by-side migration, see:
[IBM i]Note: Side-by-side migration has a different meaning on IBM i. A side-by-side installation upgrades IBM MQ on a different computer. For more information, see Installation methods on IBM i. Multiple installations are not applicable to IBM i.
[UNIX, Linux, Windows]

Multi-stage migration

Multi-stage migration is the term that is used to describe running a later version of IBM MQ alongside an older version on the same server. Multi-stage migration is the most flexible approach.

After you install the later version alongside the earlier version, you can create new queue managers to verify the installation of the later version, and develop new applications. At the same time, you can migrate queue managers and their associated applications from the earlier version to the later version. By migrating queue managers and applications one by one, you can reduce the peak workload on your staff who are managing the migration.

Figure 6. Multi-stage migration: one queue manager and application migrated to later version, and another queue manager and application still at earlier version
Graphic showing the later version of the product installed alongside the earlier version, with one queue manager and application associated with the later version and another queue manager and application still associated with the earlier version.
For more information about multi-stage migration, see: