Re: Consuming BizTalk webservice

The web service exposed by your orchestration is not different from any other webservice. In your orchestration case the parameter you pass will be the message, from a XSD schema which is equivalent to a complex type in ..NET. Say for example a webservice is expecting an object of type Employee, then the client application needs to construct that object and pass it as a parameter, which will eventually get serialized in the wire format (SOAP) and transmitted to the webservice.

The easiest way to construct your parameter (Complex type aka message from XSD) for the webservice is to
1. Take a sample message the orchestration expects,
2. In your client application, use XmlSerialization to serialize that message into typed object.
3. Call the webservice with the typed object you constructed in step #2.

Regards,
Saravana Kumar
http://www.biztalk247.com/v1/
http://www.digitaldeposit.net/blog
[Please mark the response as "Answer" if it solves your problem.]

"golddog" <golddog@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:4B86C794-9CBB-4916-AED7-7D51FD3893E7@xxxxxxxxxxxxxxxx
I'm missing at least one key thing here. Probably several, and likely some
bad assumptions.

Created a simple orchestration to accept an XML message and FTP it
somewhere. Tested with a file adapter on the front end, worked fine.

Then exposed it as a web service. Wrote a little test windows forms app to
simulate "something external" hitting the web service.

What it seems like is the service is exposed as methods to kick off the
operation in the receive port; I see in the Reference.cs file my operation
has a bunch of "Async" methods.

So, I've got an XmlDocument which I've read from disk, but the operation
calls all want this object of "rootNodeName" type. Of course, those break
down into "childNodeName" objects, et cetera down the line til we finally get
to the attribute level.

It seems awfully convoluted to have an application construct n attributes
into their object types, then coalesce those objects into object representing
nodes up the tree, et cetera, until finally we build the "rootNodeName"
object.

Is that what I really need to do, use xPath to take apart my XmlDocument at
the granular level and build up the "rootNodeName" object, passing that to
the Operation_Async call, or am I missing something simple?

Or, as likely, have I simply went down the wrong path in trying to create a
test environment?

Thanks to all who take time to read this.

.

Relevant Pages

  • Re: WebService: Via SendPortSOAP Adapter or Orchestration ?
    ... If you want to call web services, you should do it from an orchestration by ... adding a web reference to the project which will create message types and ... > implement a WebService or make a web service method call in a BizTalk2004 ...
    (microsoft.public.biztalk.general)
  • Re: BizTalk/WSDL Problems
    ... Do you want to call the WebService in the Orchestration? ... we want to use the web service as part of an orchestration project. ... adding a web reference or a service reference not the appropriate thing to ...
    (microsoft.public.biztalk.general)
  • Re: WinForms and WebServices
    ... The OP wants to create a WebService and a WebForms application to ... who will install the WebService on their Web servers. ... When that is installed your program can reference to that. ... So you say that I can change the web service URL in the config file at run ...
    (microsoft.public.dotnet.languages.vb)
  • Re: WinForms and WebServices
    ... The OP wants to create a WebService and a WebForms application to ... who will install the WebService on their Web servers. ... When that is installed your program can reference to that. ... So you say that I can change the web service URL in the config file at run ...
    (microsoft.public.dotnet.languages.vb)
  • Re: DateTime WebService Discrepancy.
    ... When the datetime is sent by the webservice, ... > Ofcourse I had not even though of just passing a string as a parameter ... > locally and cut out the call to the web service. ...
    (microsoft.public.dotnet.framework.compactframework)
Loading