| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| soap replyidentifier |
« View previous topic :: View next topic » |
| Author |
Message
|
| Sam Uppu |
 Posted: Sun Mar 13, 2011 5:08 pm Post subject: soap replyidentifier |
 |
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
Hi Guys,
I have couple of questions. Can you pls clarify.
1.I know that SOAPReply node is used to send SOAP messages from the broker to the originating client in response to a message received by a SOAPInput node based on reply identifier.
I would like to know what info does this reply identifier have?
2. If we are using loadbalancer to route webservice request to message brokers on two different hosts and when message broker processess these requests and sends reply, is the reply sent to loadbalancer(which routes to client) or to webservice client directly?
Thanks |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Mon Mar 14, 2011 9:07 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Hi Sam,
>> what info does this reply identifier have?
The SOAPReply node must always be in the same execution group as its corresponding SOAPInput node, and the ReplyIdentifier in the LocalEnvironment tree is used as a Correlation Id to correlate the inbound SOAP message with the corresponding reply sent from the SOAPReply node. It is usually a GUID, but can be any value and is specified by the originator of the SOAP request.
>> loadbalancer
You cannot use loadbalancer on SOAP requests unless you create a mechanism to match SOAP request and ReplyIdentifier in the event that your async request to downstream replies to the other node.
HTH.
Lance
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Mar 14, 2011 3:03 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| lancelotlinc wrote: |
>> loadbalancer
You cannot use loadbalancer on SOAP requests unless you create a mechanism to match SOAP request and ReplyIdentifier in the event that your async request to downstream replies to the other node. |
Depending on how you look at it, a loadbalancer on a SOAPRequest is really the same thing as a loadbalancer on the Soap Provider front-end.
The important thing is that the same TCP/IP socket is used to provide the reply as the request was sent over.
Because the SoapRequest node is listening to that specific socket for the HTTP response.
I mean, unless you're using SOAP/JMS. |
|
| 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
|
|
|
|
