WSDL without SOAP Action (BTS.Operation?)

Question

Hi
I got a WSDL without SOAP Action specified. I'm able to generate XSDs, set up a send port and  call an operation. Since I was calling a single web operation then I set up my Action at send port WCF config to be
http://localhost/CarService/updateLocation, i.e. [service URL]/[operation name].
My problem now is that I need to call two separate operations from that web service by using BTS.Operation property; one is still
updateLocation and the other one is removeLocation. How can I specify Action in send port WCF config when SOAP Action is missing in WSDL? I tried specifying different values but none of them were successful.
Ex.
<BtsActionMapping>
   <Operation Name="updateLocation" Action=""/>
   <Operation Name="removeLocation" Action=""/>
</BtsActionMapping>
Kind regards
A.H.

Answer 1

Hi,
How are going to call these web-methods. Are your going to call these two methods from the same Orchestration. Or are you going to call these methods from two different send ports by content-based routing (send port filter).
In BizTalk, this instruction (SOAP Action) is set by assigning a value to WCF.Action context property. You can specify WCF.Action property in two ways:
Single Action Format
Action Mapping Format
The way you have been calling before "http://localhost/CarService/updateLocation" is called Single Action Format. Now you have use the Action mapping format.
In Action mapping format, you map the WCF.Action context is “mapped”/resolved from another context property BTS.Operation. So if you call from the Orchestration, set the BTS.Operation approirately to resolve the URL in the config. i.e if you have config
like this:
<BtsActionMapping>
<Operation Name="updateLocation" Action="http://localhost/CarService/updateLocation"/>
<Operation Name="removeLocation" Action="http://localhost/CarService/removeLocation"/>
</BtsActionMapping>
In your orchestration, if you set the WCF.Action to "removeLocation", WCF.Action would be resolved to "http://localhost/CarService/removeLocation". In orchestration, you set the
WCF.Action  context, by setting the logical send port's operation name. Refer to this article for more info:http://www.fortuvis.com/blog/biztalk-and-wcf-soap-action/
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.