| ckphua 2005-05-20, 8:48 pm |
| From what i can tell, the SOAP adapter does not support messaging only
scenarios. You can still configure it in BizTalk Explorer since you may want
to change the location of the web service you call in the orchestration. The
WSE adapter, however, can work without an orchestration, but you must develop
a custom pipeline component and specify the web service methodname you want
to call and pass it in as part of the SOAPaction header information. It's
frustrating that MS did not go all the way to make that configurable without
the need to deploy another pipeline, but perhaps they have their reasons.
ck.
--
Phua Chiu Kiang
http://www.pckconsulting.com
"Dan Tharp" wrote:
> I must be missing something.
> This won't work for me...regardless if I use the "Static Solicit-Response"
> type or "Static One-Way" type of send port.
> I can set it up, no prob.
> But whenever anything gets routed to it, I get that "AssemblyName context
> property was not valid" error:
>
> For example:
>
> Type: Error
> Source: BizTalk Server 2004
> Event ID: 5754
> Event Time: 5/20/2005 4:10:23 PM
> User: n/a
> Computer: ECOMMERCE1
> Description:
> The "SOAP" adapter is suspending an outbound message going to destination
> URL:"http://ecommerce1/WebServices/wsCDOWarehousePricingImport/wsCDOWarehousePricingImport.asmx?op=ProcessMessage".
> Details:"AssemblyName context property was not valid.".
>
> (Same thing, whether I include the ?op=ProcessMessage or not)
>
>
> Then, I tried installing the BizTalk Adapter for Web Services Enhancements
> 2.0
> (http://www.microsoft.com/biztalk/ev...se/default.mspx).
> So, instead of creating a send port with a transport type "SOAP", now I
> create a "WSE" send port.
> Same thing, regardless if it's a "Static Solicit-Response" type or a "Static
> One-Way" port, no workie.
> Although, I seems a little more promising, since the "GO" button on the URL
> pop-up screen pushes through a ?wsdl and is able to pull up the actual web
> method name, whereas "SOAP" can't see that deep.
>
> When anything gets to this send port I get messages like this:
>
> Type: Warning
> Source: BizTalk Server 2004
> Event ID: 5743
> Event Time: 5/20/2005 4:13:21 PM
> User: n/a
> Computer: ECOMMERCE1
> Description:
> The adapter failed to transmit message going to send port
> "wse://http://ecommerce1/WebServices/wsCDOWarehousePricingImport/wsCDOWarehousePricingImport.asmx".
> It will be retransmitted after the retry interval specified for this Send
> Port. Details:"Value cannot be null.
> Parameter name: methodname".
>
> Type: Error
> Source: WSE Adapter
> Event ID: 0
> Event Time: 5/20/2005 4:13:21 PM
> User: n/a
> Computer: ECOMMERCE1
> Description:
> Failed to transmit message. Exception : System.ArgumentNullException: Value
> cannot be null.
> Parameter name: methodname
> at Microsoft.Web.Services2.Messaging.SoapClient.SendOneWay(String
> methodname, SoapEnvelope envelope)
> at
> Microsoft.BizTalk.Adapter.WseTransmitter.WseTransmitter.SendRequest(RequestObject
> requestObject)
> at
> Microsoft.BizTalk.Adapter.WseTransmitter.WseTransmitter.ProcessMessage(RequestObject
> request)
>
>
>
> Then, I was looking around in the BizTalk help and ran across an article
> talking about web services and BizTalk and there was a mention of BizTalk
> Isolated Hosts when "Enabling Web Services".
> (See
> http://msdn.microsoft.com/library/d...rvices_lpfq.asp
> for details.)
>
> The following lines from this article peak my interest:
> "Note Only one adapter can run on a single Isolated Host. If you need to
> run the HTTP and SOAP adapters on the same BizTalk Server, you must create
> an Isolated Host for each adapter."
> "Note Only one application pool can host Web Services. If you need to run
> multiple IIS 6.0 application pools, you must create an Isolated Host for
> each application pool."
>
> Is there something on the server/setup side of this that, perhaps, I'm
> missing, that's preventing my SOAP/WSE send ports from working?
>
> Thanks,
> Dan
>
>
>
> "JGaska [http://www.IoniaSolutions.com]"
> < JGaskahttpwwwIoniaSolutionscom@discussio
ns.microsoft.com> wrote in message
> news:D10FF6A8-6E17-45AC-B611-9763BB0BA207@microsoft.com...
>
>
>
|