| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Asynchronous web service |
« View previous topic :: View next topic » |
| Author |
Message
|
| vennela |
 Posted: Mon Jan 23, 2006 10:01 pm Post subject: Asynchronous web service |
 |
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I want to expose a message flow as webservice. I want that to be like a 'fire and forget' kind of invocation. I mean I'll send a HTTP/SOAP message and I will not expect any reply. Can I do this in broker. Maybe this doesn't make sense but is a HTTPReply a must.
From the manual:
| Quote: |
| If you include an HTTPInput node in a message flow, you must either include an HTTPReply node in the same flow, or pass the message to another flow that includes an HTTPReply node (for example, through an MQOutput node to a second flow that starts with an MQInput node). |
HTTPInputNode |
|
| Back to top |
|
 |
| mgk |
| Posted: Tue Jan 24, 2006 1:48 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi,
HTTP is a Request-Reply protocol, which is why the nodes have to be paired. If you don't have a reply with a Reply node, a "Messageflow Timed Out" message will be sent back to the client (when the Input node timeout expires).
However, you can wire your flow such that it sends a reply from a Reply Node immediately after a message is received be an Input node. This fits the request/reply model and allows your client to know the message was received by the flow. However, then your flow can carry on processing and perform the real work of the flow, without having to send a "real" reply when it has finished processing.
If this does not fit with what you are trying to achieve, have you thoughtt about SOAP over JMS or MQ, which should fit your requirements better.
Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Jan 24, 2006 10:32 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Thanks for the response. Very useful.
| Quote: |
| If this does not fit with what you are trying to achieve, have you thoughtt about SOAP over JMS or MQ, which should fit your requirements better. |
Definitely this is a much better alternative.
I don't have any requirement yet, but I am exploring on the options MB has to host webservices. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jan 24, 2006 12:06 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
This has always been one of the features of webservices that has been a bit of a downside compared to MQ.
HTTP is stateless (like MQ properly is), and synchronous. Just pretend you're always in request/reply mode and you can do HTTP.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| thejavapill |
| Posted: Tue Jan 24, 2006 1:48 pm Post subject: Check out Axis2 for Async Messaging ! |
|
|
Newbie
Joined: 24 Jan 2006
Posts: 7
Location: Ca
|
|
| 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
|
|
|
|
