Question
1
Replies
83
Views
Posted: November 30, 2017
Last activity: December 8, 2017
Closed
MQ Bindings mode in a multi-node environment
We use mq in bindings mode and have our PRPC 7.2.1 application running across 4 servers (4 nodes in one cluster). Each of the servers has its own MQ queue manager and they have unique names. We currently make use of the "default" mq queue manager, so we don't specify any qmgr names but our MQ team isn't that happy with us. What are the options for using mq bindings in a multinode environment if the default qmgr isn't used ; how do you specify the different qmgr names that the nodes would need to use?
***edited by moderator, Maryrita: moved to Product Support from Applications***
Moderation Team has archived post,
Close popover
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
I do not see how this would be done - but I'm guessing it can. Question is whether you want to use Pega MQ Rules (Connect-MQ, MQ-Server, MQListener) or whether you want to be on the cutting edge and use JMS. We've recently been consulting with IBM about best practices for their Liberty Profile app.server working with MQ ... and it was IBM that put forth the recommendation that the future for MQ connectivity is JMS. They've provided a set of libraries for JMS to replace their MQ libraries.
So, unless you're on Liberty, the choice is still up to you. Give me an idea of what you're looking at.
Here's a document from one of our exercises.