|
Home > Archive > BizTalk Server > February 2005 > Publishing WebServices as Orchestrations
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 |
Publishing WebServices as Orchestrations
|
|
|
| When an orchestration is published as a webservice, what I have seen so far
is that it does not become a stand alone entity. If this is true, why is
this the case? Why that orchestration still needs to be enlisted and started
in the BTS Explorer?
Thanks
Ali
| |
| Matt Milner 2005-02-20, 6:11 pm |
| All you are doing when you publish the orchestration as a web service is
creating a web service that provides an interface for your orchestration.
The web service simply receives messages, publishes them to the message box
and receives responses like any other request response adapter. When the
message is published ,the orchestration gets a copy and is instantiated.
So, the publish as web service really just helps you create a receive
location for your orchestration that uses the SOAP protocol. It would be
like having a wizard to "pulish as a file" which would just create a file
receive location for you.
Matt
"ali" <akhawaja@sbcglobal.net> wrote in message
news:AGIRd.52942$iC4.24321@newssvr30.news.prodigy.com...
> When an orchestration is published as a webservice, what I have seen so
> far is that it does not become a stand alone entity. If this is true, why
> is this the case? Why that orchestration still needs to be enlisted and
> started in the BTS Explorer?
> Thanks
> Ali
>
|
|
|
|
|