Re: BTS2004 Dynamic Send Port with XmlDocument and SOAP

Tech-Archive recommends: Fix windows errors by optimizing your registry

So there really isn't any way to call a web service purely dynamically. You
have to at some point have declared a reference to that web service in code,
even if it's WSDL is as simple as an ANY type? At some point you have to
reference the web service and generate a client side stub?



"Matt Milner" wrote:

The send port will need an assembly and class specified as context
properties on the message. These are for the client side proxy class that
will be used to call the web service. You'll also want to specify the
method name. This gives the adapter enough information to create the proxy
class and call the right method on it. So you need to have a client proxy
(.NET class) built to call the web service; this is what the adapter uses to
call it. When you add a web reference, the class for this gets built into
your orchestration project and the orchestration correctly sets those values
for you (this is a web port, as Scott was mentioning).

Matt


"MattBell" <MattBell@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9B642F06-201B-406E-AC38-B7FD186378F0@xxxxxxxxxxxxxxxx
I'm not entirely sure I know what a web port is. Is that something in
2006?

I switched my port initialize call to use SOAP://URL.asmx and it correctly
sets it up as a SOAP protocol, but not it's giving an error saying I need
to
specify an Assembly in my message.

I'm not sure what Assembly it wants. I put in the Orchestration assembly
and
that didn't work. I haven't tried the web service assembly name yet, and
I
hope that isn't the one it's looking for because that would really defeat
the
point of a service architecture if you can only call .NET assembly's
dynamically over the web.

Any thoughts?
Matt
"Scott Colestock" wrote:

Is the port a "Web port" ? (Use a web port in conjunction wtih
"dynamic")

Scott Colestock
www.traceofthought.net


"MattBell" <MattBell@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:27FC346B-2B79-4BFC-89B3-1CCBCDC14C90@xxxxxxxxxxxxxxxx
I have a dynamic send port which I initialize in my orchestration. I
set
the
Address on the port to be the Web Service address I'm trying to call,
and
then set properties on the message which is of type XmlDocument, to
define
the method to call and I specify the BTS.OutboundTransportType to SOAP.

However my orchestration keeps trying to send it using HTTP transport.
Is
there some way of making sure it uses soap when setting the address on
the
send port?

Any help is much appreciated
Matt Bell







.

Relevant Pages

  • Re: Send port calling web service?
    ... address property on the port before sending. ... I haven't tried this with a web service, so I'm not sure it will work. ... the send port associated with the party ... > Ok, let's say I use orchestration - then how can I, within the ...
    (microsoft.public.biztalk.general)
  • Re: Send port calling web service?
    ... Calling web services from send ports without using orchestration is not ... properties after the port gets created. ... > BizTalk is running) by consuming a web service. ...
    (microsoft.public.biztalk.general)
  • Re: receive and send without orchestration
    ... OK - if you have a request-response receive port, ... receive and send without orchestration ... a supplier web service, which I have no control over ...
    (microsoft.public.biztalk.general)
  • Re: Web Service response has only null values
    ... Could you please provider more information on how to debug the Web Service ... Orchestration receives response message from HttpSolicitResponse ... Orchestration sends reponse message to a File port ...
    (microsoft.public.biztalk.general)
  • Re: WCF (WinFX Jan CTP) and BizTalk (2006 B2) problem
    ... Paul - I'm in favor of having a seperate .net assembly with the webservice client. ... You can now configure this in the Send Port itself in 2006. ... reference", and there's nothing that explains why it failed. ... in the BT project if the web service is implemented with ASP.NET Web ...
    (microsoft.public.biztalk.server)