03-08-06 10:53 PM
You may not even need the master orchestration.
This can be achieved with content based routing.
You promote the orchestration_to_call element from the message into the
message context
For OrchestrationA would have a filter on the Receive shape:
MyProperties.OrchestrationName = OrchestrationA
You can declare each orchestration Receive shape to be direct or you can
bind each orchestration to the same receive port.
If a message arrives with orchestration_to_call = OrchestrationZ and there
is no OrchestrationZ you will get a Routing Failure.
If the master orchestration is required for some common pre-processing, the
same result can be achieved using direct ports in the send and receive
orchestration and promoting the same element. Although there is a trick to
promoting the element when sent from an orchestration. You need to define a
correlation set using this property and initialize the correlation on the
send shape of the master orchestration.
Greg
<rnorthedge@hotmail.com> wrote in message
news:1141833864.303373.151680@p10g2000cwp.googlegroups.com...
>I wonder if anyone could help me with this question about Biztalk 2004.
> Would it be possible to take all my messages into a master
> orchestration, but then route off to a dynamically chosen child
> orchestration based on the contents of an element in the message data?
> So the message would come in with an element like
> <orchestration_to_call>OrchestrationA</orchestration_to_call>, and it
> would be routed to the orchestration named "OrchestrationA". And if I
> created a new OrchestrationB, and changed the XML in the incoming
> message to OrchestrationB instead, I could get the message to route to
> OrchestrationB without altering the master orchestration?
>
> Thanks for any help,
> Richard
>
[ Post a follow-up to this message ]
|