| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| JMS msgId and correlId trouble in WMB |
« View previous topic :: View next topic » |
| Author |
Message
|
| JohnSmith |
 Posted: Tue May 25, 2010 1:55 am Post subject: |
 |
|
Voyager
Joined: 17 Mar 2010
Posts: 86
|
fjp_saper wrote
| Quote: |
| Use the JMS node to pick up all messages regardless of provider. This message is picked up from which ever provider you have. You then have a JMS to MQ transform and put the message to the broker's qmgr with an MQOutput Node. This is a little helper flow. |
Hi fjp_saper, here the problem is that our Message Broker environments are seperate for both UAT and SIT, which means our queue manager also located in 2 different servers. So if I am going to put the message in one Q, it wouldnt be available to other Broker/environment.
fjp_saper wrote
| Quote: |
The actual processing flow then does an MQGet on the broker's qmgr queue with check of correlationId.
All should be well and there should be no problem keeping your environments separate.... So yes you need one more flow but you gain in flexibility... |
Again, only having one separate flow wouldn't help as the environment is totally different. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue May 25, 2010 10:21 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And you can't have the application that is putting those JMS messages have a different destination by environment? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| JohnSmith |
| Posted: Tue May 25, 2010 5:32 pm Post subject: |
|
|
Voyager
Joined: 17 Mar 2010
Posts: 86
|
| Quote: |
And you can't have the application that is putting those JMS messages have a different destination by environment?
|
Unfortunately NO. As they are running only one instance of the application with message being put in only 1 queue. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue May 25, 2010 7:40 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| JohnSmith wrote: |
| Quote: |
And you can't have the application that is putting those JMS messages have a different destination by environment?
|
Unfortunately NO. As they are running only one instance of the application with message being put in only 1 queue. |
My understanding is that this application does a server process in a request / reply model. Would it be possible to specify a different JMSReplyTo destination on the request message to split the environment?
Worst case scenario, provide the messages with a decent expiry to both environments (duplication, dist list ) and let each environment choose its messages by correlationId on the MQGET node. The unused messages from the other environment will just expire...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| JohnSmith |
| Posted: Tue May 25, 2010 9:13 pm Post subject: |
|
|
Voyager
Joined: 17 Mar 2010
Posts: 86
|
| Quote: |
My understanding is that this application does a server process in a request / reply model. Would it be possible to specify a different JMSReplyTo destination on the request message to split the environment?
Worst case scenario, provide the messages with a decent expiry to both environments (duplication, dist list ) and let each environment choose its messages by correlationId on the MQGET node. The unused messages from the other environment will just expire... |
I think we need to give up here, as this so called "Application" is managed by a Vendor, who will ask for another Million $ just to make this small change.
Only solution we have decided as only 2-3 flows are using JMS INput node, so we would not run SIT and UAT both in parallel for them.
Well, that is the price we have to pay and definitely it is much cheaper than the Million dollar I mentioned earlier 
Thanks. |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
