|
Home > Archive > BizTalk Server Applications Integration > April 2006 > One WS receiving XmlDoc -> multiple typed message processes
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 |
One WS receiving XmlDoc -> multiple typed message processes
|
|
| Stephane Paquet 2006-04-10, 7:32 pm |
| Folks,
First of all, i hope i am posting this in the right place, otherwise let me
know.
I have a scenario where i am using BizTalk 2006 and need advice from an
architecture standpoint. Any comments would be appreciated.
I have full blown production/test/sandbox environments which are responsible
to route traffic of different message types from integrated system. The
middleware is evidently BizTalk (currently planning on go live with Biz2K4
but 2k6 as soon as rtm although i am confident enough even to use beta 2 of
2K6  )
I want to be able to receive any xml documents from a post to a web service
so i have used the untyped sample from Mr.Thomas as a base to start with.
Now, i have other orchestrations that deal with the specific messages, like
one for incidents for instance, this one has a req-res port receiving
xmldocuments with filter set to messagetype="Event" and receiveportname
exists as stated. My concern though, is in the fact that i am loosing the
strong type schema validation benefits since i need to construct my inner
message with an assignment from EventRequest = XmlMessage and do the same for
the outbound.
What would be recommended if i want to keep that strong typing while keeping
the benefits from the unique endpoint for receiving documents?
Thanks in advance
| |
| Greg Forsythe 2006-04-18, 12:46 am |
| You should be able to get the best of both worlds. Although you will need to
have separate endpoints for one-way and request response ports
The web service will deliver an Xml Message into a pipeline. If this
pipeline uses the XmlDisassembler the the message will be identifyed as long
the the appropriate schema is deployed. You should probably have an
XmlValidator component as well
You can bind multiple orchestrations to the one receive port.
So you have one orchestration with a subscription of messagetype=x and
receiveport ="onewayport" and a second orchestration with a subscription of
messagetype=y and receiveport ="onewayport".
The only real problem with this is you need to manage message schemas
independently - although this is the scenario with most of the other
adapters.
p.s. Biztalk2006 RTM'ed 2 weeks ago.
Greg
"Stephane Paquet" <StephanePaquet@discussions.microsoft.com> wrote in
message news:712905F4-1B34-483C-ADD6-8068E1A7986A@microsoft.com...
> Folks,
>
> First of all, i hope i am posting this in the right place, otherwise let
> me
> know.
>
> I have a scenario where i am using BizTalk 2006 and need advice from an
> architecture standpoint. Any comments would be appreciated.
>
> I have full blown production/test/sandbox environments which are
> responsible
> to route traffic of different message types from integrated system. The
> middleware is evidently BizTalk (currently planning on go live with Biz2K4
> but 2k6 as soon as rtm although i am confident enough even to use beta 2
> of
> 2K6 )
>
> I want to be able to receive any xml documents from a post to a web
> service
> so i have used the untyped sample from Mr.Thomas as a base to start with.
> Now, i have other orchestrations that deal with the specific messages,
> like
> one for incidents for instance, this one has a req-res port receiving
> xmldocuments with filter set to messagetype="Event" and receiveportname
> exists as stated. My concern though, is in the fact that i am loosing the
> strong type schema validation benefits since i need to construct my inner
> message with an assignment from EventRequest = XmlMessage and do the same
> for
> the outbound.
>
> What would be recommended if i want to keep that strong typing while
> keeping
> the benefits from the unique endpoint for receiving documents?
>
> Thanks in advance
|
|
|
|
|