Snapshot an IBM MQ Configuration

Overview

A snapshot of a queue manager retrieves all of the objects that have been defined on the queue manager. This snapshot can then be used as a basis for creating similar queue managers using the IBM MQ plugin. Another use for a snapshot is to be able to compare configurations between queue managers - either the same queue manager over time, or different queue managers (for example to compare a Production queue manager to a System Testing queue manager).

Prerequisites

To be able to perform a snapshot the following conditions must be met:

  • For pre 7.1 versions of WebSphere MQ, the IBM Support Pac M072 (Saveqmgr) must be used, specifically saveqmgrc (.exe or otherwise).
  • The location of either saveqmgrc or dmpmqcfg will need to be added to the product configuration of an environment (see below).
  • The user that the RapidDeploy web application runs as must have permission to access the queue manager and view all objects.
  • The MQ Client must be installed on the same machine as the MidVision RapidDeploy web application.
  • An Server object must be created in RapidDeploy. No connection details are required, but the server object must exist.
  • An Environment object must be created in RapidDeploy with connection information to the target queue manager.

Taking a snapshot

  1. Log into the framework server.
  2. Navigate to Projects and select a project, or, if not present, create a new one.
  3. On the Orchestration tab, select the "Snapshot IBM MQ Server" task from the task list. If not present in the list, ensure the plugin is installed.
  4. Ensure the prerequisites are met and complete the task fields with the required data.
  5. Save the configuration.
  6. Create a deployment package and run the job.

Troubleshooting

The most common issue is ensuring your user on the RapidDeploy server has sufficient access to the target queue manager. This is resolved using standard MQ techniques to allow access to a queue manager. Later queue managers (7.5+) have enhanced security and further administration of the channel might be required.

Using saveqmgrc (MS02 support pac) on version 7.5 queue managers is also inappropriate.

Using saveqmgr instead of saveqmgrc is also a common problem.