| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| One way operation using HTTPRequest node |
« View previous topic :: View next topic » |
| Author |
Message
|
| ghoshly |
 Posted: Mon May 26, 2014 6:10 am Post subject: One way operation using HTTPRequest node |
 |
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
Hello,
We are using WMB 8.0.0.2 in Windows & AIX.
I am trying to use HTTP Request node to call a end point as one way call without waiting for its response. Basically we need to call a JSON based REST service.
Similar SOAP based web services we were able to invoke using SOAP Request node as per below syntax.
| Code: |
| SET OutputLocalEnvironment.Destination.SOAP.Request.Gateway.OneWay = 'true'; |
Though even if we change SOAP to HTTP to set value before the request node, its failing after the timeout period.
Please guide if it is possible and how to proceed.  |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon May 26, 2014 9:44 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You need to make sure that your http return code is not 200.
A 200 code means success with a payload.
Check the spec but IIRC you need a 204 code on a one way acknowledgement. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ghoshly |
| Posted: Wed May 28, 2014 5:35 am Post subject: |
|
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
Hello,
We are trying with the code
| Code: |
| SET OutputLocalEnvironment.Destination.HTTP.Request.Gateway.OneWay = 'true'; |
Though it seems it has no effect on HTTPRequest node.
In case the end point service returns 200 (OK) with payload or 202 ( Accepted) or even 204 (Acknowledgement) without payload in all these cases, HTTPRequest node is accepting without any error.
Hence we can't say that we are calling strictly One-way.
Please let me know if it is clear or not. |
|
| Back to top |
|
|
| jsware |
| Posted: Wed May 28, 2014 8:59 am Post subject: |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
There's no such thing as one-way with the HTTP protocol. You will always get a protocol response (or no response which means something bad happened that means no response could be returned or that the request never made it - you're into an in-doubt scenario)
So at a protocol level, its always request/response.
But at an application level, you get no data in the response, just a 20x which means logically its one-way (no response data, just protocol acknowledgement).
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| 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
|
|
|
|
