MQ Client and high availability
Our application runs on four different physical servers (Linux/Tomcat). We are currently using MQ Bindings mode, but the company is moving to an mq client "hub" to save the licensing costs of having qmgrs on every server. The nice thing about bindings (local qmgr) is that each of the four nodes points to a different qmgr and qmgr maintenance or issues can be handled easily. Does Pega provide a way to dynamically call different remote qmgrs if one is down? How are other customers handling this scenario?
Accepted Solution
Ameriprise Financial
US
Hi - I did not end up creating an SR. We are currently mimicking the same level of availability by pointing the application on serverA to qmgr on clienthubA. serverB would point to the qmgr on clienthubB and so on. A higher availability option is no longer a current requirement and it does not appear that PRPC supports dynamic connect to a list of qmgrs, which would be needed in that situation. We can close this request.
Ameriprise Financial
US
Hi - I would really like some Pega input on the question/situation. Perhaps I should create an SR indicating that PRPC doesn't seem to support mq client hub configurations?
Pegasystems Inc.
US
Hi @MarkH960,
Did you end up opening a Support Request on this question? If so, could you share the SR ID with me please for tracking?
Thank you!
Accepted Solution
Ameriprise Financial
US
Hi - I did not end up creating an SR. We are currently mimicking the same level of availability by pointing the application on serverA to qmgr on clienthubA. serverB would point to the qmgr on clienthubB and so on. A higher availability option is no longer a current requirement and it does not appear that PRPC supports dynamic connect to a list of qmgrs, which would be needed in that situation. We can close this request.