| Author |
Message
|
| shyamkumarsharma001 |
 Posted: Thu Apr 13, 2017 3:27 am Post subject: Need to send all propagated message to same QMGR Q in clust |
 |
|
Novice
Joined: 24 May 2011
Posts: 18
|
Hi,
I have flow which takes input from front end and loops through 1 array to send multiple messages to mainframe over MQ. Suppose the flow has propagated 10 messages, these all messages should go to 1 Qmgr queue in the cluster but currently alternate messages are routed to 2 Qmgr queues due to cluster load balancing.
Mainframe is supposed to send only 1 response message but now it is sending 2 response messages as it is receiving 2 sets of messages in 2 different QMgr queues.
I thought of using Qmgr name in the MQOutput node Qmgr Name property. As We have 2 IIB servers in QA region, 1 IIB server can use QMgr1 and other IIB server can use QMgr2.
But I am facing issues on how to override the QMgr name differently while deploying the flow to the QA region as the deployment is automated through UCDeploy.
Please let me know if you have an alternate solution to this issue.
Thanks,
Shyam. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Apr 13, 2017 3:35 am Post subject: Re: Need to send all propagated message to same QMGR Q in cl |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| shyamkumarsharma001 wrote: |
Hi,
I have flow which takes input from front end and loops through 1 array to send multiple messages to mainframe over MQ. Suppose the flow has propagated 10 messages, these all messages should go to 1 Qmgr queue in the cluster but currently alternate messages are routed to 2 Qmgr queues due to cluster load balancing.
Mainframe is supposed to send only 1 response message but now it is sending 2 response messages as it is receiving 2 sets of messages in 2 different QMgr queues.
I thought of using Qmgr name in the MQOutput node Qmgr Name property. As We have 2 IIB servers in QA region, 1 IIB server can use QMgr1 and other IIB server can use QMgr2.
But I am facing issues on how to override the QMgr name differently while deploying the flow to the QA region as the deployment is automated through UCDeploy.
Please let me know if you have an alternate solution to this issue.
Thanks,
Shyam. |
you did not specify which version of MQ you're talking about. Did you think of setting instead of bindnotfixed bindgroup ? Have your messages that need to go to the same queue manager issued in a group and bind group should take care of it 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| shyamkumarsharma001 |
| Posted: Thu Apr 13, 2017 5:34 am Post subject: |
|
|
Novice
Joined: 24 May 2011
Posts: 18
|
| Sorry about that, MQ version is 7.5. The messages are not issued under group. Probably that may resolve it but I have not tried grouping messages through IIB yet. I will update you on the same if I try to implement grouping of messages. Thanks for your reply. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 13, 2017 5:40 am Post subject: Re: Need to send all propagated message to same QMGR Q in cl |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shyamkumarsharma001 wrote: |
| But I am facing issues on how to override the QMgr name differently while deploying the flow to the QA region as the deployment is automated through UCDeploy. |
Using uDeploy has no impact on your situation. Anything you can do to override properties in an environment that doesn't have uDeploy can be incorporated into a uDeploy workflow.
Caveat: if what you'd usually do is "edit the bar file in the Toolkit and then deploy it to Prod", then I accept that's probably hard to implement in a workflow. It's also a bad idea.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shyamkumarsharma001 |
| Posted: Thu Apr 13, 2017 11:29 pm Post subject: |
|
|
Novice
Joined: 24 May 2011
Posts: 18
|
| Thanks for the reply. I am now checking the QueueManagerName for the broker in particular environment and accordingly setting the destination list through esql. It's working as expected now. The properties are promoted to flow which gets overridden through UCDeploy at deploy time. |
|
| Back to top |
|
|
|
|
