Welcome to MSDN Blogs Sign in | Join | Help

WCF LOB Adapter SDK and BizTalk Adapter Pack

The BizTalk Adapter Pack, comprising of the SAP, Siebel, OracleDB, OracleEBS and SQL WCF Bindings / Adapters which can be used with BizTalk Server 2006 R2 and R3. The Windows Communication Foundation (WCF) Line Of Business (LOB) Adapter SDK.

Syndication

News

CTP4 released (Adapter Pack V2, Adapter SDK V1 SP2) on October 21, 2008

Other Blogs Related to BizTalk Adapter Pack

Introducing the Migration Tool for Microsoft BizTalk Adapters for Enterprise Applications

For customers currently using the Microsoft BizTalk Adapters for Enterprise Applications (aka the LOB adapters) and willing to migrate their existing projects to the WCF-based LOB adapters, here's a tool that will help you migrate your projects to work with BizTalk Adapter Pack 2.0.

Before we start talking about the tool and the adapter projects it can be used against, let us set the ground by laying the rules for the naming convention that we will be using here:

  • Microsoft BizTalk Adapters for Enterprise Applications adapters are referred to as non-WCF LOB adapters.

  • Adapters part of BizTalk Adapter Pack 2.0 are referred to as WCF-based LOB adapters.

What does the tool do?

The migration tool accepts BizTalk project/Solution files containing schemas generated by non-WCF LOB adapters and generates corresponding new BizTalk project/solution files having schemas corresponding to the WCF-based LOB adapters, with the maps and orchestrations modified accordingly. This tool helps you to migrate the projects for the following adapters:

  • BizTalk ODBC Adapter for Oracle Database
  • BizTalk Adapter v2.0 for mySAP Business Suite
  • SQL adapter

 Where to get the tool from?

You can download the tool from http://go.microsoft.com/fwlink/?LinkID=153328. The tool also includes a migration guide that describes:

  • How to run the tool
  • What steps to follow after the tool has finished migrating the project
  • Limitations of the migration tool.

Published Tuesday, June 16, 2009 4:03 PM by nitinme

Filed under:

Comments

# re: Introducing the Migration Tool for Microsoft BizTalk Adapters for Enterprise Applications @ Wednesday, November 11, 2009 7:41 PM

Hi

If you are interested in feedback, we have noticed the tools fails migrating maps where one of the schemas is in an external assembly.

For instance if using it to migrate a SAP project to WCF, the old SAP schema is inside the solution, but if the destination schema is in another assembly that is referenced, the tool fails to migrate the map with the error

"Destination Schema of the map was not found"

The work around we have used is to take a copy of the schemas and attach into the project, and update the maps to the local schema instead of the referenced schema, prior to using the migration tool.

The tools then runs successfully - how it is a clumsy and time consuming work around.

PeterZ

# re: Introducing the Migration Tool for Microsoft BizTalk Adapters for Enterprise Applications @ Sunday, November 15, 2009 2:52 AM

Thanks PeterZ, for your valuable feedback.

The current requirement of the tool states that all the artifacts(schemas/maps/orchestration) to be migrated should be present in the solution being migrated.

So, in the current design, for making the tool work, you can just add the project(which produces the referenced dll) to the current solution. And in the migtation wizard, specify the .sln file instead of the btproj.

The migration should work correcly.

rosing

Anonymous comments are disabled
Page view tracker