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
  • 1.  full repository for two cluster

    Posted 10/11/13 03:01 PM
    The v7 infocenter makes it look pretty straight forward. Use the REPOSNL and then the qmgr shows up on both the clusters in the explorer.


    When i try that nothing happens and if i try to add a full repository from 1 cluster to another cluster it doesnt allow me.


    it says" queue manager already in cluster"

    any thoughts on how to add a queue manager as repos on two clusters?       


  • 2.  full repository for two cluster

    Posted 11/13/13 10:36 AM
    Hello,

    As I understood each time you are making each queue manager as full repository. That's not right.
    "he v7 infocenter makes it look pretty straight forward. Use the REPOSNL and then the qmgr shows up on both the clusters in the explorer."

    According to IBM you should have few full repository and all other should be partial repositories.
    In this case you shouldn't connect full repository of cluster 1 to cluster 2.
    You can use next scenario:
    1. create qmgr
    2. add it to cluster 1 as partial repository
    3. add it to cluster 2 as partial repository

    "When i try that nothing happens and if i try to add a full repository from 1 cluster to another cluster it doesnt allow me."

    Right comment above should help.
    "it says" queue manager already in cluster"

    I suppose it's not possible.
    "any thoughts on how to add a queue manager as repos on two clusters?"
     
    You can send me message if you need help with this.


  • 3.  full repository for two cluster

    Posted 11/13/13 10:40 AM
    Here is how to add new qmgr to cluster:
    publib.boulder.ibm.com/infocenter/wmqv7/...


  • 4.  full repository for two cluster

    Posted 03/13/14 01:47 AM
    It isn't sufficient to set REPOSNL because this only tells the QMgr that it participates in the new cluster.  You must also share the CLUSRCVR in the new cluster.

    If you use CLUSNL on the CLUSRCVR channel it is possible to participate in two clusters over the same channel.  This is almost mandatory if you use IBM's example of TO.QMGRNAME for the channel  Instead, I use CLUSNAME.QMGRNAME as the CLUSRCVR channel.  That forces a dedicated CLUSRCVR for each cluster.  This prevents many cluster namespace management and stability problems. 

    For more thoughts on WMQ cluster best practices, please see Mission:Messaging: WebSphere MQ cluster design and operation.