Implementing the solution using the graphical user interface

Implementing the solution in this scenario involves using the graphical user interface to migrate from an earlier release of IBM MQ , running on a Windows operating system, to a later release, also running on a Windows operating system, then verifying that the queue managers and queues have been successfully migrated to the later release.

Before you begin

If you want to try out the scenario, first follow the instructions to set up a copy of the sample messaging infrastructure as described in Creating a sample initial IT configuration. This sample configuration is based on IBM MQ Version 8.0.

The migration process described in this scenario shows migrating a queue manager from IBM MQ Version 8.0 to IBM MQ Version 9.0.

Option 1: Single-stage migration

In single-stage migration, the installation of the later version of the product replaces an earlier version in the same installation location.

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 latest version, automatically. Using this approach, your system will be unavailable for the entire process.

Option 2: Side-by-side migration

In side-by-side migration, you install the later version of IBM MQ alongside an earlier version. The queue managers continue to be associated with the earlier version until you are ready to migrate them to the later version.

With the side-by-side approach, because you uninstall the earlier version before starting any migrated queue managers in the later version, we can assign the installation of the later version to be the primary installation.