Introducing the Migration Tool for Microsoft BizTalk Adapters for Enterprise Applications

re: Introducing the Migration Tool for Microsoft BizTalk Adapters for Enterprise Applications

Rohit Singh — Sat, 08 Jan 2011 14:42:45 GMT

A new version of the tool is now available.

BizTalk Adapter Pack Migration Tool 2.0 can be downloaded from Microsoft Download: www.microsoft.com/.../details.aspx

List of changes from Biztalk Adapter Pack Migration Tool 1.0 :

1. Bug Fixes

2. Option to remember URI and Username.

2. Option to create dummy nodes in existing SAP RFC related maps, so that the new adapter can return all tables in the response message.

3. Option to promote properties in new schema corresponding to promoted properties in the old schema.

4. Added detailed error logging, when map generation for SAP RFCs and IDOCs fails.

Detailed release notes are included in the downlaod package.

re: Introducing the Migration Tool for Microsoft BizTalk Adapters for Enterprise Applications

Rohit Singh -MSFT — Thu, 11 Nov 2010 08:56:04 GMT

non-WCF LOB adapters are the old aadapters - availabe at www.microsoft.com/.../details.aspx

www.microsoft.com/.../details.aspx

the adapters from which migration is availabe are -

Microsoft BizTalk ODBC Adapter for Oracle Database

Microsoft BizTalk Adapter for Siebel eBusiness Applications

and Microsoft BizTalk Adapter v2.0 for mySAP Business Suite Service Pack 1

I think BizTalk LOB Adapters 2010 Beta would be the WCF base adapters from Biztalk Adapter Pack.

re: Introducing the Migration Tool for Microsoft BizTalk Adapters for Enterprise Applications

Saz — Tue, 26 Oct 2010 09:15:41 GMT

Hi,

I'm a bit confused. Could you confirm that BizTalk LOB Adapters 2010 Beta available recently before BizTalk 2010 RTM is referred to as non-WCF LOB adapters. It is no longer available and only BizTalk Adapter Pack 2.0 and WCF LOB Adapters SDK is available for 2010?

Thanks.

re: Introducing the Migration Tool for Microsoft BizTalk Adapters for Enterprise Applications

Saz — Tue, 26 Oct 2010 09:15:41 GMT

Hi,

Thanks.

re: Introducing the Migration Tool for Microsoft BizTalk Adapters for Enterprise Applications

rosing — Sun, 15 Nov 2009 10:52:50 GMT

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.

re: Introducing the Migration Tool for Microsoft BizTalk Adapters for Enterprise Applications

PeterZ — Thu, 12 Nov 2009 03:41:01 GMT

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.