Hi,
I have a orchestration published as a web service.  I have also
deployed the orchestration (not even sure that's necessary).

The receieve port is set up as far as I can tell.

I am using a windows service to call the web service orchestration.
The Windows service runs, but i must not be calling the orchestration
correctly.

----------------------------------------------------------------

string SerialNum = "1";

WS.WSMethod myWS = new WS.WSMethod();
myWS.Operation_1(SerialNum);

-----------------------------------------------------------------

Am I way off here or at least on the right path?  Any insight is
greatly appreciated.
Thanks,
Tom

[ Post a follow-up to this message ]

Steps,

Create Orchestration
Build the solution
Publish as web service (allow anonymous access)
Deploy orchestration
Enlist and start orchestration

Call your web method and that will do it.

Things to keep in mind,
After building your solution, and publishing your web service, do not
build the solution again since the version of the dlls created would
mismatch and you will run into trouble.

BizTalk sucks. No good documentation on things like these. It's very
very flimsy. Not a good idea to use it for publishing web services, in
my opinion. Hope the next version of BizTalk is upto par.

[ Post a follow-up to this message ]

Thanks a bunch for the reply.

I think perhaps my recieve port is not configured correctly.

I have it public of course, since the wizard runs without error.  However,
I'm ignorant on how else to configure the port.

I'm assuming I called the Orchestration web service correctly as no one has
said otherwise that has viewed this thread.

If I am allowing anoymous access, should i take out the:
myWS.Creditials(user, password, domain);
out of my code for now?

thanks again,
Tom

"kplkumar@gmail.com" wrote:

> Steps,
>
> Create Orchestration
> Build the solution
> Publish as web service (allow anonymous access)
> Deploy orchestration
> Enlist and start orchestration
>
> Call your web method and that will do it.
>
> Things to keep in mind,
> After building your solution, and publishing your web service, do not
> build the solution again since the version of the dlls created would
> mismatch and you will run into trouble.
>
> BizTalk sucks. No good documentation on things like these. It's very
> very flimsy. Not a good idea to use it for publishing web services, in
> my opinion. Hope the next version of BizTalk is upto par.
>
>

[ Post a follow-up to this message ]