Windows: Migrating a queue manager to a later version

Follow these instructions to migrate a queue manager from Version 7.1 to Version 7.5.

Before you begin

  1. Create a migration plan. Use the planning task, Windows: Planning to migrate to a later version as a guide.
  2. The migration paths to IBM WebSphere MQ Version 7.5 on Windows Vista are listed in Table 1
    Table 1. IBM WebSphere MQ Version 7.5 on Windows Vista or Windows Server 2008: supported migration paths
    From: To:
    IBM WebSphere MQ Version 6.0 plus fix pack 6.0.2.1 on Windows Vista or Windows Server 2008 IBM WebSphere MQ Version 7.5 on Windows Vista or Windows Server 2008
    IBM WebSphere MQ Version 7.0.1 on Windows XP Professional SP2 IBM WebSphere MQ Version 7.5 on Windows Vista or Windows Server 2008
  3. Review the IBM WebSphere MQ system requirements for Version 7.5; see System Requirements for IBM WebSphere MQ.
  4. Back up your system before you install IBM WebSphere MQ Version 7.5 over Version 7.1. Once you have started a queue manager you cannot revert to the previous release. If you must restore the system, you cannot recover any work, such as changes to messages and objects, performed by IBM WebSphere MQ Version 7.5. For more information about backing up your system, see Backing up and restoring IBM WebSphere MQ queue manager data .
  5. Review any other installed SupportPacs for their applicability to IBM WebSphere MQ Version 7.5.
  6. If you are running on a server with multiple IBM WebSphere MQ installations, that is, IBM WebSphere MQ Version 7.0.1, Fix Pack 6 (or later), you must identify the installation. Make sure that the commands you enter run against the correct installation; see setmqenv.

About this task

Complete this task to migrate a queue manager to IBM WebSphere MQ Version 7.5 from Version 7.1.

All the objects that you previously created are maintained. The components that were previously installed are preselected in the feature options when you install the new level. If you leave these components selected, you can keep them or reinstall them. If you clear any of these components, the installation process uninstalls them. By default, a typical migration installs only the same features that were installed in the previous version installation.

For example, if IBM WebSphere MQ Explorer was not installed in the Version 7.1 installation, it is not installed in a Version 7.5 installation. If you want IBM WebSphere MQ Explorer, select a custom installation, and select the IBM WebSphere MQ Explorer feature on the Features panel. If you do not want IBM WebSphere MQ Explorer, uninstall the IBM WebSphere MQ Explorer feature by selecting a custom installation. Then clear the IBM WebSphere MQ Explorer feature on the Features panel. For more information about how to uninstall features, see Modifying the installation using WebSphere MQ Installation Launchpad.

You can also migrate a Version 7.1 queue manager to IBM WebSphere MQ Version 7.5 on a system where a previous version has been uninstalled. The queue manager data must have been retained, or restored from a backup.

Procedure

  1. Log in as a user in group mqm.
  2. Stop all applications using the IBM WebSphere MQ installation.

    If you use the IBM WebSphere MQ Managed File Transfer (MFT) component, ensure that any MFT agents have finished all of the file transfers that they were engaged in. There should be no incomplete transfers associated with the agents, and their SYSTEM.FTE.STATE queues should contain no messages.

  3. End all the activity of queue managers associated with the IBM WebSphere MQ installation.
    1. Run the dspmq command to list the state of all the queue managers on the system.

      Run either of the following commands from the installation that you are updating:

      dspmq -o installation -o status
dspmq -a

      dspmq -o installation -o status displays the installation name and status of queue managers associated with all installations of IBM WebSphere MQ.

      dspmq -a displays the status of active queue managers associated with the installation from which the command is run.

    2. Run the MQSC command, DISPLAY LSSTATUS(*) STATUS to list the status of listeners associated with a queue manager. 
      echo "DISPLAY LSSTATUS(*) STATUS" | runmqsc QmgrName
    3. Run the endmqm command to stop each running queue manager associated with this installation.
      Read syntax diagramSkip visual syntax diagram endmqm -c-w-i-p QmgrName

      The endmqm command informs an application that the queue manager it is connected to is stopping; see Stopping a queue manager.

      • For the maintenance to proceed, applications must respond to an endmqm command by disconnecting from the queue manager and releasing any IBM WebSphere MQ libraries they have loaded. If they do not, you must find another way to force applications to release IBM WebSphere MQ resources, such as by stopping the applications.
      • You must also stop applications that are using the client libraries that are part of the installation. Client applications might be connected to a different queue manager, running a different installation of IBM WebSphere MQ. The application is not informed about queue managers in the current installation being shut down.
      • Any applications that continue to have IBM WebSphere MQ shared libraries from the installation loaded prevent you applying IBM WebSphere MQ maintenance. An application might disconnect from a queue manager, or be forcibly disconnected, but keep a IBM WebSphere MQ shared library loaded.
    4. Stop any listeners associated with the queue managers, using the command: 
       endmqlsr -m QMgrName
  4. Back up the queue manager.
  5. Stop the MQSeries® Service and exit the Service taskbar icon application.
  6. Upgrade the IBM WebSphere MQ installation to Version 7.5 using one of these procedures:
  7. Reenter domain, user ID, and password information

    When the installation of IBM WebSphere MQ Version 7.5 completes, the Prepare WebSphere MQ Wizard starts automatically.

    On Windows Vista or Windows Server 2008 where UAC is enabled: If you rerun the Prepare WebSphere MQ Wizard, ensure that the wizard is run with Administrator privilege, otherwise the wizard might fail.
  8. Optionally, uninstall IBM WebSphere MQ Version 7.1.
    Note, that you carry out this step only if you are doing a single stage migration; see UNIX, Linux, and Windows: Single-stage migration to a later version

What to do next

You might be restoring Version 7.1 on a server with multiple IBM WebSphere MQ installations. If one of the installations is primary, after restoring Version 7.1, the Version 7.1 installation will be by default, the primary. You must review how applications connect to an installation. After restoring Version 7.1 some applications might connect to the wrong installation.