| Author |
Message
|
| satchin |
 Posted: Mon Nov 14, 2011 4:55 am Post subject: can we put MQInput and SOAPInput nodes in one message flow? |
 |
|
Apprentice
Joined: 08 Feb 2011
Posts: 33
|
Hi All,
Please provide me the solution for the solution in the below scenario.
We have a requirement to accept the request from mqinput node and invoke a webservice using SOAPRequest, it sends acknowledge message and will pass the acknowledgement message to source application.
After a some period of time the destination application will send the actual response message and ESB will send this response message to the source application.
I am planing to put these interactions in one message flow as mention below, I have to calculate the timeout for these 2 flows thats why I am putting these 2 in one message flow
MQInput->SOAPRequest->MQOutput -> to invoke the service and to send the acknowledgement message to source application
SOAPInput->MQOutput->SOAPReply -> to send the response message to the source application
Please suggest, whether the solution that I am following is correct or not, if not please provide the correct solution.
Thanks in advance. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Nov 14, 2011 5:20 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Why are you planning to put them in the same flow?
Essentially, these are two separate operations. I hope that there is something in the data being exchanged to facilitate the originating application to keep track of what is going on.
What you seem to be emulating is an ASYNC webservice. Have you looked at the ASYNC webservice sample?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 14, 2011 5:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I'm confused.
Why aren't you using SOAP ASync nodes? This is exactly what they are for and do.
 |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Nov 14, 2011 6:46 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| mqjeff wrote: |
I'm confused.
Why aren't you using SOAP ASync nodes? This is exactly what they are for and do.
|
Perhaps the OP is using a version of Broker that does not use Async Soap nodes?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 14, 2011 6:52 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| smdavies99 wrote: |
| mqjeff wrote: |
I'm confused.
Why aren't you using SOAP ASync nodes? This is exactly what they are for and do.
|
Perhaps the OP is using a version of Broker that does not use Async Soap nodes? |
So, what you're saying is that the OP now has a business requirement that requires them to upgrade their version of Broker. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Nov 14, 2011 7:14 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| mqjeff wrote: |
So, what you're saying is that the OP now has a business requirement that requires them to upgrade their version of Broker. |
Yes BUT (there has to be one...) this is easier said than done in many organisations.
It took me 9 months to get a FP installed. (8.5 to get the agreement to do it).
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| satchin |
| Posted: Mon Nov 14, 2011 7:17 am Post subject: |
|
|
Apprentice
Joined: 08 Feb 2011
Posts: 33
|
Thanks all for your response.
I need to consider two message flows as one transaction only.
For the two message flows I need to main timeout, if the whoel transaction is not completed in 15 sec, I have to send timeout exception.
Here whole transaction is
First -> accepting the request from source application through MQInput node and invoke destination application through SOAPRequest node and then send the acknowledgement response to originating application through MQOutput node.
Second, after some periodof time destination application will send the actual response message and ESB will send this response to originating application.
The source application will be waiting until it gets the actual response message.
Please help me how to maintina these 2 flows as one transaction. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 14, 2011 1:12 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You can not create a single transaction that spawns multiple Input nodes.
Each input node will be fired independently and create a unique transaction.
Even if you do the correct thing for this use case and use the SOAPAsync nodes, you will still not be able to create a transaction that spawns both the MQInput and the SOAPAsync response.
You can, however, ensure that the MQInput does not complete it's transaction until the flow that is started from that receives a response from something else. But you can't receive that response using another Input node.
And that's as much help as I'm willing to give you. |
|
| Back to top |
|
|
|
|
