Hi there:

Does anyone has a solution to workaround a soliciti-response port WITHOUT
using an Orchestration?

I am using a solicit-response port to send a request and receive a response
but I am not allowed to use an Orchestration. Is it even possible?

Thanks a million!

Regards,
Shamod

[ Post a follow-up to this message ]

You can certainly wire up a solit response send port to a two-way receive
port - (you can subscribe in the send port via message type or
bts.receiveportname, etc.)

You will have the opportunity to run a map & a pipeline on either (or both)
sides.  If the work you are doing will fit that model, you should be in good
shape.

Scott Colestock
www.traceofthought.net



"Sam" <Sam@discussions.microsoft.com> wrote in message
news:37478032-2CB9-4BA7-A1AF-4E5B31DFC908@microsoft.com...
> Hi there:
>
> Does anyone has a solution to workaround a soliciti-response port WITHOUT
> using an Orchestration?
>
> I am using a solicit-response port to send a request and receive a
> response
> but I am not allowed to use an Orchestration. Is it even possible?
>
> Thanks a million!
>
> Regards,
> Shamod

[ Post a follow-up to this message ]

Scott,

Can you please elaborate a bit more on "wire up a solicit-response port to a
two-way receive port"?

Thanks for your help!


"Scott Colestock" wrote:

> You can certainly wire up a solit response send port to a two-way receive
> port - (you can subscribe in the send port via message type or
> bts.receiveportname, etc.)
>
> You will have the opportunity to run a map & a pipeline on either (or both
)
> sides.  If the work you are doing will fit that model, you should be in go
od
> shape.
>
> Scott Colestock
> www.traceofthought.net
>
>
>
> "Sam" <Sam@discussions.microsoft.com> wrote in message
> news:37478032-2CB9-4BA7-A1AF-4E5B31DFC908@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

If you create a two-way receive port within BizTalk, and you also create a
static solit-response port, you will find that in the properties of the
solicit-response port you can select - under "filters and maps" - a filters
node.  There, you can select "BTS.ReceivePortName", and use the "=="
operator, and in the right-most column put in the name of your receive port
that you created.

At that point, your solicit-response port is "subscribed" to your receive
port.

If that isn't clear, let me know -

Scott Colestock
www.traceofthought.net




"Sam" <Sam@discussions.microsoft.com> wrote in message
news:524F5C53-D2CB-41FA-B074-A9506DE16868@microsoft.com...[vbcol=seagreen]
> Scott,
>
> Can you please elaborate a bit more on "wire up a solicit-response port to
> a
> two-way receive port"?
>
> Thanks for your help!
>
>
> "Scott Colestock" wrote:
> 

[ Post a follow-up to this message ]