| Yossi Dahan 2005-02-22, 5:50 pm |
| Alex hi,
If I understand your scenario correctly you have a request-response port
(2way receive) and then a solicit-response (2way send) port subscribed to
the receive port (more/different filters may be in place for the send port)
If this is the case you do not need to worry about setting up your own
correlation, the BizTalk messaging engine handles all of this for you by
setting a guid to the correlation token context property when the initial
request is received and following on that value when the response comes in.
Hope this helps
Yossi Dahan
"Alex" <Alex@discussions.microsoft.com> wrote in message
news:56F2842D-3DEB-4884-8241-3C793184A748@microsoft.com...
> Hi
>
> Does anyone have experience with request-response scenarios that don't use
> orchestrations? How does BizTalk know which message is the response?
>
> In our scenario we use a request-response receive adapter which listens to
> a
> web service. In addition we have a solicit-response send port which
> filters
> for messages that arrived through the mentioned receive port and sends
> them
> to a custom built send adapter.
> The problem now is that we can track that the adapter receives the message
> and returns a valid stream to the response, but it never arrives at the
> web
> service client and neither HAT nor the event log shows any hint to it. Do
> we
> have to set up a kind of correlation or how does BizTalk know that our
> adapter response is the response to the web service?
>
> Cheers
> Alex
|