BizTalk and WCF adapters: Operation and SOAP Action

One area here is not so well documented.

When we are filling in the Transport properties for WCF adapter, we see the SOAP Action header section.

What is it? Where we could take the values for Operations and Actions?

If we use the Consume WCF Service wizard, this section is filled up automatically. But sometimes we have to fill it in manually.

NP

Open a WSDL for the Web-service and search for a binding section. If you add the “?wsdl” to the Web-service URL, usually the Web-service WSDL is opened.

That’s how operations and actions in the WCF parameters and WSDL are mapping:

Hope it helps.

Print | posted on Wednesday, December 21, 2011 2:53 PM

Feedback

# re: BizTalk and WCF adapters: Operation and SOAP Action

left by custom research paper at 12/22/2011 8:31 AM Gravatar
Thanks for providing such a great information here.

# re: BizTalk and WCF adapters: Operation and SOAP Action

left by Steef-Jan Wiggers at 12/31/2011 1:07 AM Gravatar
Good post.

# re: BizTalk and WCF adapters: Operation and SOAP Action

left by Leonid Ganeline at 12/31/2011 1:15 AM Gravatar
Thanks, Steef-Jan!

# re: BizTalk and WCF adapters: Operation and SOAP Action

left by Dan Rosanova at 1/3/2012 10:58 AM Gravatar
Are the WSDL Operation and the BtsActionMapping Operation related? I know the BtsActionMapping/@Name can be used to map BTS.Operation to a specific SOAP Action (BTS.Operation is the Operation from an orchestration logical port, among other things). I feel like I'm missing something here.

# re: BizTalk and WCF adapters: Operation and SOAP Action

left by Leonid Ganline at 1/3/2012 8:03 PM Gravatar
Hi Dan,
Good point! WSDL Operation and orchestration logical port are related.
When the BizTalk "WCF Service Consume" wizard generates an orchestration with port type inside, it creates a port operation equal a wsdl:operation.
This is a one way relation. wsdl -> BizTalk.
The wizard also creates a binding file with definition of a "physical" port. A "SOAP Action header" defined there also (see a picture above).
BTW These operations are tightly coupling the Web-service and the orchestration. This is really BAD. But seems there is no other good alternative.
Post A Comment
Title:
Name:
Email:
Comment:
Verification: