| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ OUTPUT NODE OUT Terminal Continuation flow |
« View previous topic :: View next topic » |
| Author |
Message
|
| MD |
 Posted: Mon Nov 06, 2017 2:14 am Post subject: MQ OUTPUT NODE OUT Terminal Continuation flow |
 |
|
Novice
Joined: 19 Apr 2017
Posts: 15
|
Hello All,
I have a requirement in which one request-reply also included in between the flow.
My flow contains,
MQ-INPUT -> Java Compute -> MQ-OUTPUT -> MQ GET -> Remaining transformation -> MQ-OUTPUT
MQ INPUT node: Will get the input message.
Java Compute node: Will set some headers, req->reply setup so it will request for a response message and put it in reply queue(REPLYINQ)
MQ OUTPUT node: To send the request to target queue specified in JCN(Previous node). (Out terminal connected to GET node)
MQ GET: Take the message from REPLYINQ(reply queue) and do the remaining transformation.
So now I want to commit the transaction at 1st MQ-OUTPUT node to send the request and then to get reply for that.
How can I commit the transaction in the middle of the flow ? And based on the reply I have to continue the flow after 1st MQ-OUTPUT node.
Please advise..
Thanks in advance
 |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Nov 06, 2017 5:16 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The MQ Output node has a setting. Set transaction no.
You will need a transformation node between the MQ Output and the MQ Get node to get the message/correlation id from the local environment and put it into the MQMD for the get.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| MD |
| Posted: Mon Nov 06, 2017 7:15 pm Post subject: |
|
|
Novice
Joined: 19 Apr 2017
Posts: 15
|
Thanks much Grand
It worked with Transaction mode setup.
BR/MAnoj |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Nov 07, 2017 12:32 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
For scalability it's better to terminate the flow at MQoutput and let the reply start a new flow. That would avoid blocking the thread.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
