Tutorial 2: Migrating BizTalk Projects in Siebel
The previous version of the Siebel adapter that shipped with Microsoft BizTalk Server differs from the WCF-based Siebel adapter in many aspects, including:
The design-time experience of creating a BizTalk project.
The metadata retrieval experience.
Schema file name and namespace.
Data type mappings.
The operations that can be performed using the adapter.
Physical port configuration in the BizTalk Server Administration console
However, you can make changes to the BizTalk project created using the previous version of the adapter and make it work with the WCF-based Siebel adapter.
This tutorial provides instructions on the changes you should make to the existing BizTalk project created using the previous version of the adapter.
Note
In this tutorial, for the sake of brevity, the previous version of the Siebel adapter will be referred to as vPrev Siebel adapter. Similarly, a BizTalk project that uses the vPrev Siebel adapter will be referred to as vPrev BizTalk project.
Sample Used for the Tutorial
This tutorial is based upon a sample (Siebel_BussComp_Migration) that demonstrates how to migrate a vPrev BizTalk project that performs an Insert operation on the Account Siebel business component. The sample is provided with Microsoft BizTalk Adapter Pack. For more information, see Adapter Sample.
Prerequisites
You must have a vPrev BizTalk project. This tutorial involves a BizTalk project that performs an Insert operation on the Account business component.
You must have a request message to perform an Insert operation on the Account business component using the vPrev Siebel adapter. The request message must conform to the schema of the Insert operation generated using the vPrev Siebel adapter.
You must have completed the steps in Prerequisites to create Siebel applications.
Understanding a BizTalk Project Created Using the Previous Version of the Adapter
The key constituents of a vPrev BizTalk project created are:
BizTalk orchestration. This is a simple orchestration that picks request messages from a file location, sends the request message to the Siebel system using a Siebel send-receive port, receives the response, and saves it to another file location.
Schema for the operation you wish to perform on the Siebel business component. This tutorial involves a BizTalk project that performs an Insert operation on the Account business component. The schema generated for the Account business component is AccountService_Account_x5d.xsd. This schema is generated using the vPrev Siebel adapter.
Note
Unlike the WCF-based Siebel adapter, the vPrev Siebel adapter does not support generating metadata for specific operations on a business component. By default, the adapter generates schema for all the operations supported on the business component.
Request message. The request message to perform an Insert operation on the Account business component. The schema of the request message conforms to the schema of the Insert operation as surfaced by the vPrev Siebel adapter.
How to Migrate a BizTalk Project Created Using the Previous Version of the Adapter
The goal of this migration tutorial is to enable you to send a request message, which conforms to schema generated by the vPrev Siebel adapter, using a WCF-Custom port that can only process messages conforming to the WCF-based Siebel adapter. So, in short, the migration exercise involves configuring the WCF-Custom port to process messages that do not conform to the WCF-based Siebel adapter's schema.
However, to be able to configure the WCF-Custom port appropriately, you must perform the following tasks:
Generate metadata for the Insert operation on the Account business component using the WCF-based Siebel adapter.
Map the request message for performing an Insert operation using the vPrev Siebel adapter to a request message for performing an Insert operation using the WCF-based Siebel adapter.
Map the response message received using the WCF-based Siebel adapter to the response message for the vPrev Siebel adapter.
Create a WCF-Custom Siebel send-receive port in the BizTalk Server Administration console.
Configure the WCF-Custom port to use the request and response mappings.