Calling a Web Service with Custom Parameters from an Orchestration in BizTalk Server 2004

• Download BizTalk project - 21.99 KB
• Download Web Service project - 19.08 KB

Introduction

It is generally very straight forward to invoke a Web Service from an BizTalk Orchestration. In some special cases, a Web service returns or accepts an object. In such cases, a custom map is required to send a request to the web service. We shall consider a case where an object is returned from a web service and how this is handled in BizTalk.

Employee Data Retrieval - Example

Consider a simple scenario where some information about an Employee is required within an orchestration. This employee information is provided by some web service, which takes in a EmployeeInput object as a input parameter and returns a EmployeeOutput object. Notice that both the input and output parameters to the web service are objects, and not simple .NET types.

First Came the Schemas...

Let us have a quick look at the input and output schemas...

Employee Request Schema

This is very simple schema with EmployeeCode element.

Employee Response Schema

The output schema contains all the elements related to the employee information.

Approach Overview - Steps to Invoke a Web Service

• In the Solution Explorer, right-click on the Project and select "Add Web Reference". Follow the instructions on the dialog displayed.
• Look under the folder "Web References" and open the file "Reference.xsd". This file would contain the expected input and output formats (XML elements) to correctly invoke the Web Service.
• Promote all the properties (XML elements) in the "Reference.xsd" file, which are required within the Orchestration.
• Create a new "Map" which maps the data from the Orchestration message to the Web Service input. In this case, select the namespace for "Reference.xsd" as the Destination schema.
• Lastly use the "Send" and "Receive" shape to send Web service Request and Response respectively.

BizTalk Maps

In this project, we are using two maps:

• The first one, would convert the input message into the one required by the Web Service.

  

• The second one would convert the input message into the output message as required by the orchestration.

  

Building the Orchestration (Also Known as a "Business Process")

The parallel branch in this orchestration shall invoke the Web Service and perform the Transformation simultaneously.

Setting the parameters required to invoke the Web Service:

WSParamEmployeeInput.EmployeeCode = EmployeeIn.EmployeeCode;
WSRequest.employeeInput = WSParamEmployeeInput;
System.Diagnostics.EventLog.WriteEntry("Transformation", "EmployeeIn -> WSRequest");

Assigning the EmployeeOut message into a temporary variable:

TempEmployeeOut = EmployeeOut;
System.Diagnostics.EventLog.WriteEntry("Transformation", "Employee In to EmployeeOut");

Assigning the data obtained from the Web Service to the EmployeeOut message:

EmployeeOut = TempEmployeeOut;

EmployeeOut.EmployeeCity = WSResponse.RetrieveEmployeeResult.EmployeeCity;
EmployeeOut.EmployeeName = WSResponse.RetrieveEmployeeResult.EmployeeName;
EmployeeOut.EmployeeDept = WSResponse.RetrieveEmployeeResult.EmployeeDept;
EmployeeOut.EmployeeEmail =WSResponse.RetrieveEmployeeResult.EmployeeEmail;

List of various messages used in the Orchestration...

Executing the DEMO

Input XML File

Notice the input file data. The EmployeeCode is filled up.

Solution Explorer

Observe the various artifacts in the Solution Explorer.

Output XML File

The output XML file has all the information about the Employee.

About the Downloadable Code

• Unzip the file WSParamDemo.zip with the folder names in the C:\ drive.
• Unzip the file EmployeeInfoService.zip with the folder names in the C:\inetpub\wwwroot drive and setup the Web Service Application through Internet Services Manager.
• The folder KeyAndBindings contains the Bindings.xml file, which can be imported after the solution is built and deployed.
• Place the EmployeeRequest_1.xml in the In folder and observe the Event log to find out the various events generated, and finally observe the Out folder for the output XML file.

Quick Takeaways

1. Always set the Activate property to "true" for the first Receive shape in the orchestration.
2. Note the XSD file generated when a Web Reference is added to the Project.
3. Ensure that all the promoted properties in the schema have a default value.
4. A BizTalk service needs to be re-started every time a deployment is done.