Many of you will have noticed or heard the buzz that the new BizTalk release will be called 2013. It was not a surprise to me or a few others in the blogosphere. Mark Burch on his blog post in July already gave hints to the name or Johan Hedberg beginning of this year Why BizTalk Server 2010 R2 should be BizTalk Server 2013. Anyways the name is now officially 2013.
What will its beta bring us? Well you can find an overview on the BizTalk Server Team Blog. Basically it aligns with the new Microsoft Platform releases like Windows Server 2012, SQL Server 2012 and Visual Studio 2012. Besides that you will find the enhancements in adapters, new adapters like the SB-Messaging, and ESB Toolkit integration (no separate download anymore).
I downloaded the BizTalk 2013 beta and installed it on a new VM. I will not detail the complete installation and configuration here as it is a pretty straight forward experience as with the previous 2010 version. Do mind that there are some slight differences when you read the documentation. For instance when installing SQL Server 2012 you will need to install SQL Server Data Tools (documentation still mentions Business Intelligence Development Studio, yet you will not find this feature in the features list of SQL Server 2012).
What I will do now is share my installation and configuration experience regarding some of the new features.
BizTalk Server 2013 has a few new adapters:
Also notice the Windows SharePoint Services adapter that is available by default. WCF-SQL or other LOB Adapters have to be installed separately through LOB Adapter Pack. This can be done through Installation Media.
ESB Toolkit Integration
ESB Toolkit is now fully integrated with BizTalk Server, which means it does not require you to download it separately. So the ESB Toolkit is now packaged by BizTalk media like adapter pack was with the BizTalk 2010 release. The ESB Toolkit configuration experience is vastly simplified to enable a quick setup. Through Installation Wizard you can install the ESB Toolkit.
A wizard starts when clicking the Install Microsoft BizTalk ESB Toolkit link.
Click Next to continue the installation.
Click Install. The Installation ESB Toolkit is a very straight forward and quick. After installation you can configure the ESB Toolkit through ESB Configuration Tool. A dialog will appear where you fill detail for configuration of the ESB.
Click Apply Configuration. The ESB BizTalk Components under the ESB BizTalk applications is new.
Default the check boxes are not checked. Check the Enable ESB Core Components in BizTalk and click Apply Configuration.
Configuration is done and Microsoft.Practices.ESB application is available in the BizTalk runtime.
The final step is installing the Exception Management Portal, which needs to be installed the same way as with version 2.1. You will find the installation guide in C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit.
Tracking Dependencies Between Artifacts in a BizTalk Server Application
In the BizTalk administration console the dependencies between artifacts can now be viewed and navigated. A BizTalk applications can have many dependencies and if for instance you need to adjust one of the artifacts. Dependency information of an artifact can be very valuable; you must know which artifacts in the dependency hierarchy must be stopped or re-deployed. The BizTalk Server Administration console displays the dependency information in modes – whether an artifact uses another artifact as well as whether an artifact is used by another artifact.
The Microsoft.Practices.ESB.Agents.Delivery has one dependency (Send Port)
Click Send Ports and you will the send port.
There are more enhancements and more new features than the ones I discussed here. I will be trying out some of the other features in the near future and share my experience.