04-29-06 12:14 AM
There are several options for this. The easiest is to use an HTTP
solicit-response send port from orchestration, sending a request message to
it, and getting a response message as a reply. This will abstract some of
the subscription enlistments that take place under the covers. It will
also allow you to use Delivery Notification to effectively catch delivery
failures and handle them, if needed. You can see the "HTTP Send Adapter"
article for more information.
Another option is to string together a request-response receive port with a
solicit-response HTTP send port. This is a non-orchestration based
approach. On the send port, you'll set up a filter to subscribe to the
Receive Port. When the receive side publishes to the Message Box, it will
determine that it has one waiting send side subscriber and will create a
correlation id to route the send side's return message back to the receive
side.
Yet another option would be to have: (X) a send port which simply publishes
into the message box, (Y) a solicit-response send port filtering on certain
message properties from X, and (Z) another send port which is filtering on
the response message from Y. The Z send port may be filtering on SendPort
= Y or some specific promoted properties.
Yeah it's easy to get subscription issues when working with 2-way ports, so
be careful. The subscription viewer is also very helpful in these cases.
HTH,
Doug Girard [MSFT]
Note: This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
>Thread-Topic: Subscribe to HTTP Response?
>thread-index: AcY77B07Af9Jstd+TK2PGEfyKs5lRg==
>X-WBNR-Posting-Host: 68.22.255.4
>From: "examnotes" <Buck@discussions.microsoft.com>
>Subject: Subscribe to HTTP Response?
>Date: Mon, 27 Feb 2006 14:21:11 -0800
>Lines: 13
>Message-ID: <FA63AF4D-B219-48A8-ACE3-488F97CDC389@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.biztalk.general
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.biztalk.general:35266
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>Hello,
>
>I am confused about http solicit response send ports. I can send the
>request but how do I receive the response. I get "no subsciption" errors.
I
>know how to subscribe to a regular receive port via the "Recieve Port
Name"
>filter, but I don't know how to subscribe to the response part of the
solicit
>response send port.
>
>I'm told that I do not need an orchestration for this.
>
>Any suggestions?
>
>Buck
>
[ Post a follow-up to this message ]
|