MQ

MQ

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

How to apply MQ fixes in a MSCS cluster?

  • 1.  How to apply MQ fixes in a MSCS cluster?

    Posted Tue December 29, 2020 03:48 PM

    The partners ask us how to apply MQ V9.1 fixes in a Microsoft Cluster Service (MSCS) cluster environment.



    #MQ
    #Support
    #SupportMigration


  • 2.  RE: How to apply MQ fixes in a MSCS cluster?

    Posted Tue December 29, 2020 06:11 PM

    Regarding the question on how to apply MQ V9.1 fixes in a MSCS cluster, the steps needed depend on whether it is a development environment. If it is a development environment, you may simply stop MSCS service on both Active and Passive nodes, and then apply the MQ fix on both nodes based on the documentation below:

    Applying maintenance to IBM MQ

    https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.mig.doc/q006250_.htm

    If you need to do it in a production environment, please use the steps below:

    1. Modify the possible owners of the IBM MQ resource to encompass only the Active node. With no owners assigned to Passive node, the IBM MQ resource that is being updated cannot be activated.
    2. Ensure that the group containing the IBM MQ resource is currently on one of the nodes defined as a possible owner. The group must include any applications connecting to the queue manager resource.
    3. Stop the cluster service on the Passive node being updated. The cache is cleared of any IBM MQ DLLs that have been registered.
    4. Apply the required maintenance level on the Passive node.
    5. Start the cluster service on the Passive node.
    6. On the Active node to be migrated next, ensure that the IBM MQ resources are offline.
    7. Remove this node from the list of possible owners.
    8. Move the group containing the IBM MQ resource to one of the possible owners(Passive node in this case) and bring it online.
    9. Repeat steps 3-8 as necessary for the Active node.


    #MQ
    #Support
    #SupportMigration