Migrating from one Continuous Delivery release to another
An overview of how we migrate from one Continuous Delivery (CD) release to another.
Before starting
To migrate replicated data queue managers, follow the instructions in Migrating replicated data queue managers.
- Back up your existing IBM MQ environment. This is
required in case we need to revert to your current CD release of IBM MQ. Important: Once the new
installation is started, all of the existing IBM MQ objects will be migrated to the new modification level. If we do not back up the system, you
cannot revert the objects to their previous level without completely uninstalling, and restoring a
backup you made before you carried out the migration.
Copy the qm.ini file and the registry entries.
For more information about backing up the system, see Backing up and restoring IBM MQ queue manager data.
- Use the dmpmqcfg command to save the current configuration details to a text file.
Procedure
- Stop all of the IBM MQ processes for the installation being migrated.
- Uninstall the existing CD installation. Note: This does not remove the object definitions from the system; they remain in place.
- Install the new CD modification level, for example, 9.2.1 onto the same system.
-
Start the queue manager.
strmqm QmgrName
When you first start a queue manager after migration to the new CD level:- Any new attributes for existing objects are set to their default values.
- Any new default objects are created.
- Queue manager objects are migrated to the new modification level.
Note: If we have saved your current configuration details in a text file, that file can be used to duplicate these objects in the newly created queue manager after it has been created, if you installed the new version onto a different system.
See the runmqsc command for instructions on how we can do this.
Parent topic: Migrating IBM MQ
Related information