My quick scribble on how the WCF Adpater works from an architectue view point:
Ø Adapter Pack v2.0 can be used on BizTalk 2006 R2 – unless the software assurance has not expired before 1st May 2009 (Lucky we got this one
)
Ø Can use it outside BizTalk – via .Net application (License per processor)
Ø Behind the scene SOAP messages are transformed into ADO.net calls
Ø Improvements:
o Query Notification is introduced (used Service broker behind the scenes)
o Has the Composite transaction capability i.e, Bunch up your SQL command messages and execute all of them in one transaction
Ø The workflow on the above diagram (non-shaded section) is described by the steps on the right
o Interesting aspect is mentioning the “WCF Service (Proxy)” – generated by the adapter –> Hosted in IIS –> Can be consumed from other clients

Migration tool for existing adapters to the Adapter Pack
Description: 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
Location: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=e68b8fd1-5c8a-499a-8237-4dc23a8342c5&displaylang=en