BizTalk Consume WebServices with SOAP Header

BizTalk Consume WebServices with SOAP Header

When working with Web Services, the common scenario is to pass in the credential in the SOAP Header.

In this post, I will provide the steps how to do this in BizTalk Orchestration.
This will be a simple flow like below screen shot :

Flow Detail :

1. Web Application will call an exposed web services by Biztalk Orchestration
2. The request object consists of 3 elements : UserName, Password, Message
   
3. BizTalk Orchestration will construct the SOAP Header Message with UserName and Password
4. BizTalk Orchestration will assign the Message as the body and assign the SOAP Header
5. BizTalk Orchestration calls the Web Services (WSSOAPHeader)
6. Web Services will read the SOAP Header message and return back some message
7. BizTalk will also return back the message to the web application

BizTalk Orchestration layout

One of the most crucial thing in here is the SOAP Header message.
To create the SOAP Header message schema :

1. Create a property schema file
2. In the schema properties, change the Target Namespace to http://schemas.microsoft.com/BizTalk/2003/SOAPHeaderSet the Node Name property to the SOAP Header Name and the Property Schema Base to MessageContextPropertyBase

After creating this property, we can assign the SOAP Header into the message like this below

varXMLSOAPHeader = msgSOAPHeader;
msgWSRequest(MyBizTalkApp.AuthenticationSOAPHeader) = varXMLSOAPHeader.OuterXml;

Note :

• When assigning the SOAP Header, it expects string value, that's why I assign the msgSOAPHeader into an XML document variable and get the string from OuterXml property.
• If the SOAP Header is not received by the web services even though you have assigned it in the code, make sure that you have followed each of the steps to create the SOAP Header message schema above, especially the namespace part. It caused me 2 days to notice this one in the end :P

You can find and download the whole VS 2005 solution at here :


Here is the link to the MSDN Site : Consuming Web Services with SOAP Headers