|
Home > Archive > BizTalk Server General > June 2005 > Receive-response orchestration with versions of the request-respon
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Receive-response orchestration with versions of the request-respon
|
|
|
| We have several formats of XML we recieve to which we need to respond with
the same format. For example we may have 4 different types of requests (v1,
v2, v3, v4) and we must respond respectively. We'd like to create a single
orchestration that uses our internal cannonical form of the request-response.
So I'm needing suggestions on how to develop this kind of architecture
especially when performance is critical.
In looking at the adaptors we thought of creating a custom adaptor that
would do a transform for both the request and response. I had also
considered building several adaptors/pipelines however looks like on a
receive-response orchestration only one adaptor can be bound to it.
Any ideas and suggestions??
Thanks!!
ed
| |
| Scott Colestock 2005-06-27, 5:51 pm |
| No need for a custom adapter, unless I'm missing something -
I'm assuimg you are doing a request/response interaction? You should
consider having a request/response receive port for each of your 4 different
types of requests - each with a mapping that takes you to your internal
format. An outbound mapping can be specified to take you from internal back
to one of the four formats as well.
Your orchestration can subscribe to the internal canonical type (using
direct binding) rather than a receive port - and thereby pick up all four
kinds of documents.
Scott Colestock
www.traceofthought.net
"Ed" <Ed@discussions.microsoft.com> wrote in message
news:9D63A4F9-C1E4-4DFE-944A-C00ECE6FB78E@microsoft.com...
> We have several formats of XML we recieve to which we need to respond with
> the same format. For example we may have 4 different types of requests
> (v1,
> v2, v3, v4) and we must respond respectively. We'd like to create a
> single
> orchestration that uses our internal cannonical form of the
> request-response.
> So I'm needing suggestions on how to develop this kind of architecture
> especially when performance is critical.
>
> In looking at the adaptors we thought of creating a custom adaptor that
> would do a transform for both the request and response. I had also
> considered building several adaptors/pipelines however looks like on a
> receive-response orchestration only one adaptor can be bound to it.
>
> Any ideas and suggestions??
>
> Thanks!!
>
> ed
|
|
|
|
|