|
Home > Archive > BizTalk Server Orchestration > April 2005 > Separation of parameters and Receive shapes
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 |
Separation of parameters and Receive shapes
|
|
| n.s.tho 2005-04-26, 5:49 pm |
| (using bts 2004)
I have an orchestration that I want to call from another orchestration using
the Start Orchestration Shape, and I also want the option of invoking this
orchestration by placing a msg in a receive port.
1. I know how to paramaterize the orchestration
2. I know how to set the orchestration to monitor a receive port
Question:
If I call the orchestration programatically and pass in parameters, what
will happen when the orchestration reaches the Receive shape?
Should I create a "wrapper" orchestration for this paramaterized one? The
wrapper would monitor the receive port and then programatically call the
paramaterized orchestration. that way, the parameterized orchestration would
not have to have a receive shape
| |
| Stephen W. Thomas 2005-04-26, 5:49 pm |
| Hello.
One potential solution would be to use Direct Message Box binding rather
then the Start Orchestration shape. This way, would could set a context
value on the message inside the Orchestration, say “StartOrch2”, and route
the message based on this property to the Receive Port in the second
Orchestration.
Likewise, when you wanted a Receive Port to send a message to that
Orchestration all you would have to do is promote this “StartOrch2” value
inside the pipeline and it too would get routed to the correct Orchestration.
In the past, this was the approach I took to solving this problem.
The wrapper Orchestration might be a little more straight forward though.
Hope this helps.
Stephen W. Thomas
http://www.geekswithblogs.net/sthomas
"n.s.tho" wrote:
> (using bts 2004)
> I have an orchestration that I want to call from another orchestration using
> the Start Orchestration Shape, and I also want the option of invoking this
> orchestration by placing a msg in a receive port.
>
> 1. I know how to paramaterize the orchestration
> 2. I know how to set the orchestration to monitor a receive port
>
> Question:
>
> If I call the orchestration programatically and pass in parameters, what
> will happen when the orchestration reaches the Receive shape?
>
> Should I create a "wrapper" orchestration for this paramaterized one? The
> wrapper would monitor the receive port and then programatically call the
> paramaterized orchestration. that way, the parameterized orchestration would
> not have to have a receive shape
|
|
|
|
|