Hi,
We have two orchestrations in two different assemblies. One orchestration
needs to start the other orchestration. Can any body tell me which is the
best way to go?
1. I can use start orchestration and start the other orchestration.
2. I can expose the first orchestration as a web service and consume in
other orchestration.
Will the performance comes down when we expose as a web service and consume
in other orchestration?

Regards, MM

[ Post a follow-up to this message ]

You can also do direct binding between the ports.  I'd go for that over
start orchestration (less coupling between the two orchestrations)

--
Jon Flanders
http://www.masteringbiztalk.com/blogs/jon/

"Mohan" <Mohan@discussions.microsoft.com> wrote in message
news:54D54EB8-F325-4058-91EE-7329A8EBFEA6@microsoft.com...
> Hi,
> We have two orchestrations in two different assemblies. One orchestration
> needs to start the other orchestration. Can any body tell me which is the
> best way to go?
> 1. I can use start orchestration and start the other orchestration.
> 2. I can expose the first orchestration as a web service and consume in
> other orchestration.
> Will the performance comes down when we expose as a web service and
> consume
> in other orchestration?
>
> Regards, MM

[ Post a follow-up to this message ]

Mohan wrote:
> Hi,
> We have two orchestrations in two different assemblies. One orchestration
> needs to start the other orchestration. Can any body tell me which is the
> best way to go?
> 1. I can use start orchestration and start the other orchestration.
> 2. I can expose the first orchestration as a web service and consume in
> other orchestration.
> Will the performance comes down when we expose as a web service and consum
e
> in other orchestration?
>
> Regards, MM

As for your performance question -
I'm pretty sure a web service call will be slower then calling an
orchestration (or using direct binding, as Jon suggested) because of the
extra layers required to handle the web service protocol.
however, it won't be a huge difference as web services are usually
considered slower because of the need to serialize the objects to xml
and the deserialize them back to objects on the web service (and in some
cases more then once).
by going through the message box you'll be doing the
serialization/deserialization the cost is not that big (I'm not sure if
this serialization takes place when calling orchestrations)

Using web service will give you more SOA design (Which is the latest
buzz word after all), if there's a chance you'll be needing that called
orchestration from other places (and especially from other
applications/server groups/networks) you should definitely use the web
services approach

Yossi Dahan

[ Post a follow-up to this message ]

Mohan,

Whatever John said is correct and best too.  You can use either start
orchestration shape / direct messagebox binding.   If the orchestrations are
in two namespace/assembilies (it is immaterial) you have to make the called
orchestration access specifier as 'public" and refer the assemly in the
calling orchestration.

-Sarbillgates

"Yossi Dahan" wrote:

> Mohan wrote: 
>
> As for your performance question -
> I'm pretty sure a web service call will be slower then calling an
> orchestration (or using direct binding, as Jon suggested) because of the
> extra layers required to handle the web service protocol.
> however, it won't be a huge difference as web services are usually
> considered slower because of the need to serialize the objects to xml
> and the deserialize them back to objects on the web service (and in some
> cases more then once).
> by going through the message box you'll be doing the
> serialization/deserialization the cost is not that big (I'm not sure if
> this serialization takes place when calling orchestrations)
>
> Using web service will give you more SOA design (Which is the latest
> buzz word after all), if there's a chance you'll be needing that called
> orchestration from other places (and especially from other
> applications/server groups/networks) you should definitely use the web
> services approach
>
> Yossi Dahan
>

[ Post a follow-up to this message ]