[AIX][Linux]

Migrating on AIX and Linux: side-by-side

Side-by-side migration is the term used to describe installing a later version of IBM® MQ alongside an earlier version on the same server. Queue managers remain running during the installation and verification of the later version of IBM MQ. They remain associated with the earlier version of IBM MQ. When you decide to migrate queue managers to the later version of IBM MQ, you stop all queue managers, uninstall the earlier version, and migrate them all to the later version of IBM MQ.

Before you begin

  1. The upgrade from the earlier version to the latest version of the product requires a full migration of queue managers. Create a migration plan. Use the planning task Planning to migrate IBM MQ to a later version on AIX and Linux, as a guide.
  2. Review the IBM MQ system requirements for the later version; see System Requirements for IBM MQ.
  3. Back up your system before you install a later version of IBM MQ over an earlier version. After you start a queue manager, you cannot revert to the previous version. If you must restore the system, you cannot recover any work, such as changes to messages and objects, performed by the later version of IBM MQ. For more information about backing up your system, see Backing up and restoring IBM MQ queue manager data.
  4. Review any other installed SupportPacs for their applicability to the later version.
  5. If you are running on a server with multiple installations, you must identify the installation. Make sure that the commands you enter run against the correct installation; see setmqenv.
  6. From IBM MQ 9.0, the ccsid_part2.tbl file replaces the existing ccsid.tbl file that is used in previous versions of the product to supply extra CCSID information.
    Attention:
    The ccsid_part2.tbl file takes precedence over the ccsid.tbl file and:
    • Allows you to add or modify CCSID entries
    • Specify default data conversion
    • Specify data for different command levels
    The ccsid_part2.tbl is applicable to the following platforms only:
    • [Linux]Linux - all versions
    • [Windows]Windows

    If you added any of your own CCSID information into your existing ccsid.tbl file, copy this information into the new ccsid_part2.tbl file to take advantage of the new formats in your customizations

    Copy the required information, rather than move the information, so that your existing version of IBM MQ continues to work.

About this task

In the side-by-side migration scenario, you install the later version of IBM MQ alongside queue managers that continue to be associated with the installation of the earlier version of the product. When you are ready to migrate the queue managers, and applications, to the later version:
  1. Stop all the queue managers.
  2. Uninstall the earlier version of the product.
  3. Migrate all the queue managers and applications to the later version.

Procedure

  1. Install the later version in a different installation directory from the earlier version.
    1. Decide on an installation naming convention. Give the installation a name of your choosing, or accept the default installation name.
      For the first installation, the default name is Installation1. For the second installation, the name is Installation2, and so on.

      [AIX]On AIX there is no option to set the installation name, Installation1 is set by default.

    2. Install the later version. For more information see, Installing IBM MQ server on AIX or Installing additional IBM MQ installations on Linux using the rpm command.
    3. Verify the installation.

      Run the installation verification procedures and your own tests.

  2. Uninstall the earlier version of the product.
    • When uninstalling the earlier product, you must stop all queue managers and applications that have loaded an IBM MQ library on the server. For this reason, you might choose to postpone uninstalling the earlier version of the product until a convenient maintenance window. When an earlier version of the product is not installed on a server, it is sufficient to stop the queue managers and applications that have loaded libraries from the installation that you are uninstalling or updating. It is not necessary to stop applications and queue managers associated with other installations.
    1. Log in as a user in group mqm.
    2. Stop all applications using the IBM MQ installation.

      If you use the 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. Stop the mqweb server that is associated with the IBM MQ installation by entering the following command: 
      endmqweb
    4. List the state of all the queue managers on the system by using the dspmq command: 
      dspmq -a
    5. List the status of listeners associated with a queue manager by using the DISPLAY LSSTATUS MQSC command: 
      echo "DISPLAY LSSTATUS(*) STATUS" | runmqsc QmgrName
    6. Stop any listeners associated with the queue managers, using the endmqlsr command: 
      endmqlsr -m QMgrName
    7. Stop each running queue manager that is associated with this installation by using the endmqm command: 
      endmqm QMgrName
    8. Uninstall the earlier version of the product. For more information, see Uninstalling or modifying IBM MQ on Linux
  3. Set the primary installation to avoid specifying a search path to run IBM MQ commands by using the setmqinst command: 
    INSTALLATION_PATH/bin/setmqinst -i -n installationName

    Use the dspmqinst command to discover the InstallationName.

    If there is a primary installation, AIX and Linux applications that expect to find the IBM MQ library in /usr/lib, find a symbolic link to the library in /usr/lib/32 1 . /usr/lib/32 is normally in the default search path. It is also specified as a load path in the IBM MQ build scripts for AIX and Linux.

    It is sufficient to link applications only to /usr/lib. With a primary installation of the later version of the product defined on the server, an application can connect to any queue manager associated with any installation on the server. IBM MQ loads the correct library for the application.

  4. Optional: Associate the queue managers with the installation by using the setmqm command: 
     
setmqm -m qmgrName -n installationName
  5. Start the queue managers and migrate them to the later version of the product by using the strmqm command: 
    strmqm qmgrName
    When you first start a queue manager after migration:
    • Any new attributes for existing objects are set to their default values.
    • Any new default objects are created.
    • Queue manager data is migrated.
    At this point, queue manager data is migrated and you cannot revert to a previous release.
    Important: Do not use the -c option to start the queue manager, unless you explicitly want to reset or re-create the default system objects.

    You must start IBM MQ before you start any listeners.

  6. Start your applications.

What to do next

You cannot reinstall an earlier version of the product on a system that has the latest, or any other, version of IBM MQ installed.

1 /usr/lib for 64 bit applications.