| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| calling multiple webservices simultaneously |
« View previous topic :: View next topic » |
| Author |
Message
|
| Rahul999 |
 Posted: Tue Jul 13, 2010 7:14 am Post subject: calling multiple webservices simultaneously |
 |
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
Hi All,
We have developed a message flow in which we are invoking multiple web services (running on different URL's) in a sequential order, and then consolidating the responses from all the calls again a sequential order.(receiving the response of 1, store it in a environment variables, then call 2nd web service, received its response, store again and then call 3rd and so on..), but then the overall response time becomes more(slow).
What we would like to know is it possible to call all the services in parallel and collect the response in parallel to speed up the processing time, how it can be done?
thanks in advance.
_________________
"For all your days be prepared, and meet them ever alike.
When you are the anvil, bear - when you are the hammer, strike."
- Edwin Markham |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Jul 13, 2010 7:31 am Post subject: Re: calling multiple webservices simultaneously |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Rahul999 wrote: |
| collect the response in parallel to speed up the processing time, how it can be done? |
On the face of it, collecting the responses could be done with a Collector node but it would depend a lot on how much dependency there is between the web services (e.g. do you need the response from one to send a subsequent request)?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jul 13, 2010 9:51 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Yes, wrap each http call in an mq flow driven from an Aggregation pattern.
Collector won't help here, as you still have to call each service in sequence and then pass it to another input. |
|
| Back to top |
|
|
| Rahul999 |
| Posted: Wed Jul 14, 2010 6:24 am Post subject: |
|
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
| Quote: |
Yes, wrap each http call in an mq flow driven from an Aggregation pattern.
Collector won't help here, as you still have to call each service in sequence and then pass it to another input. |
Do I need to use Aggregation node for the same,
What i was trying to do was use n number of output nodes , let the HTTP call gets submitted in parallel with these nodes and then all of them will put reply in a single queue, but then all of these messages can not be picked by a single MQGet node. So, kinda stuck here.
Regards
_________________
"For all your days be prepared, and meet them ever alike.
When you are the anvil, bear - when you are the hammer, strike."
- Edwin Markham |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jul 14, 2010 7:05 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Rahul999 wrote: |
| Quote: |
Yes, wrap each http call in an mq flow driven from an Aggregation pattern.
Collector won't help here, as you still have to call each service in sequence and then pass it to another input. |
Do I need to use Aggregation node for the same, |
Yes. |
|
| 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
|
|
|
|
