In sequence of a set of posts about installation and configuration of BizTalk 2010, I leave you here two excellent posts about:
Installing BizTalk Adapter Pack 2010 posted by Steef-Jan Wiggers:
And Microsoft AppFabric Connect in BizTalk 2010 posted by Thiago Almeida:
Installing BizTalk Adapter Pack 2010 on x64
The BizTalk Adapter Pack 2010 provides connectivity to SAP, Oracle E-Business Suite, Siebel and SQL and Oracle Databases. The BizTalk Adapter Pack can be installed in conjunction with, or separately from, BizTalk Server.
The BizTalk Adapter Pack 2010 includes support for new versions of the following line-of-business applications and databases: SAP 7, Oracle EBS 12.1 and SQL Server 2008 R2. The Adapter Pack also provides support for Visual Studio 2010 and .NET Framework 4.
It is included in both the Enterprise and Standard Editions of BizTalk. When you install the adapter pack on x64 environment you have to perform a few steps. These steps were described in earlier versions through installation guides, although for some it was not always clear (i.e. I saw couple of questions on forum about how to install or problems people had). There is documentation to install adapters pack, but now during installation one is guided through the necessary steps.
This is a definite improvement towards installing Adapter Pack on for instance x64 environment as shown on the screenshot above. So first step is installing WCF LOB Adapter SDK and by clicking on the first step an installer of SDK is launched.
By clicking next and selecting one of installation options the SDK is installed. After installation you will see that first step is completed in the overall process. Second step is installation of the Adapter Pack (x86). By clicking Microsoft BizTalk Adapter Pack needs to be installed an installer is launched again.
After installation of this pack the screen is updated again stating second step is completed successfully.
You will sometime see windows update screen or screen with question if you want to join the improvement program. Next step is installing the Microsoft BizTalk Adapter Pack(x64). Before installing this pack you have to install x86 first, which is overlooked a lot of times in past by people. Can’t happen having guidance.
Having installed the x64 Adapter Pack the final step can be performed.
By clicking on Install Microsoft BizTalk Adapters for Enterprise Applications an installer is launched.
As this installation has been successfully completed the process of installing the LOB Adapters is complete.
I recommend to always choose complete installation of SDK, Adapter Packs and Microsoft BizTalk Adapters for Enterprise Applications.You the have documentation at you disposal. Going through this process you now have full set of adapters ranging from new WCF Adapters to old (non-WCF) Adapters. Next step is adding the appropriate adapters in BizTalk Administration Console.
You have to go navigate to Platform Settings –> Adapters and then right click New –> Adapter.
Note: When installing the adapter pack you do not see a new adapter show up under the Adapters folder or in the drop down for Add new Adapter. The adapter pack installs new custom bindings.The BizTalk “adapter” for instance for the Oracle database shows up in BizTalk as the OracleDBBinding. The standard bindings are wsHttpBinding, netTcpBinding, etc. OracleDbBinding and SqlBinding are themselves custom bindings. (Ben Cline explained this on forum few weeks ago).
You can also download the interactive or normal poster of BizTalk Adapter 2010. The BizTalk Adapter Pack is included with BizTalk Server 2010 and you can download the BizTalk Server 2010 Evaluation if you want to try it out.
When completing this process you also have installed all the prerequisites for AppFabric Connect. When starting a WCF Workflow Service you will see BizTalk Mapper.
This post goes over a couple of points around the installation of Microsoft AppFabric Connect feature of BizTalk Server 2010 and a note on the licensing requirements.
The installation details of the BizTalk AppFabric Connect feature are described in detail here by Trace Young:
On a development or runtime machine where Windows Server AppFabric is already installed you can start up the BizTalk Server setup and select ‘Install Microsoft AppFabric Connect’:
Once there you can see the required installation steps: you need BizTalk Server, the Microsoft WCF LOB Adapter SDK (this is a pre-requisite for the BizTalk Adapter Pack), and the BizTalk Adapter Pack itself (this is the part that installs the actual AppFabric Connect feature proper):
There are actually two features that compose the Microsoft AppFabric Connect feature: the mapper activity; and the line of business activities.
Both [update 30/10/2010] Even though the splash screen mentions the BizTalk runtime is required, only the mapper requires the BizTalk Server runtime to be installed on the machine. The line of business activities are as they were in BizTalk 2009, you only need the WCF LOB SDK and the BizTalk Adapter Pack.
When clicking to install Microsoft BizTalk Server, the only parts needed for the [update 30/10/2010] mapper part of the AppFabric Connect feature on a development environment are the following:
Note that you only need the Developer Tools and SDK on a development environment, but the Server Runtime is needed on all environments [update 30/10/2010] for the mapper feature. This is because the mapper depends on certain core DLLs from BizTalk Server but the LOB activities don’t.
Next is the WCF LOB adapter SDK. On a development environment you need both Runtime and Tools (if you want just the mapper then just Runtime is enough). On non-development environments (UAT, Production, etc) you can install only the runtime option.
If you made it this far and all you wanted was the mapper in your workflow then you have it already. If you want the LOB feature then the last step is to install the adapters you are interested in from the BizTalk Adapter Pack. For example, if I’m only interested in the WCF-SQL and the WCF-Oracle adapters I choose them from the custom installation:
With this you can start a new .NET 4 WCF Workflow Service project or add a new workflow to an existing project. You should now be able to use ‘Add Adapter Service Reference’ from your workflow project to get the LOB activities, and of course you will find the mapper activity in your workflow’s toolbox:
[update 30/10/2010] Microsoft’s approach to this at the moment is that you need a BizTalk Server Standard or Enterprise license to use the Windows AppFabric Connect feature (even if you only need the LOB adapters and did not install the BizTalk runtime).