With the release of the new version of BizTalk Server, it is time to build a new virtual environment to play with.
I have a quad core server with 12 Gb memory at my disposal for this purpose so I’m ready to create a Hyper-V image.
The first step is install the basics, in my case:
- Windows Server 2008 R2 Standard Edition
- SQL Server 2008 R2 Developer Edition
- SQL Server 2005 Notification Services
- Visual Studio 2010 Ultimate Edition
- SharePoint Foundation 2010
- Office 2010
Next, get the install files for:
If you download the BizTalk Server 2010 Developer Edition, you’ll have a packed executable. When unpacked, it is expanded into 10060(!) files. The files are split up into two folders with:
- BizTalk Server 2010 Installation files, including:
- Adapter Pack (Oracle, SAP, Siebel, SQL)
- AppFabric Connect
- BizTalk Server 2010 Accelerator files, including:
The prerequisites CAB file that is so familiar to BizTalk installations is mentioned in the documentation and is not enclosed in the installation files.
Installation and configuration of BizTalk Server 2010 are basically nothing new. However if you don’t follow the installation guide, you might run into configuration errors. One issue I ran into was that I forgot to set IIS to native 64-bit mode. This is also missing in the installation guide. You can use the following statements for this:
- cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
- C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727>aspnet_iisreg -i
This is one area where BizTalk still can be improved, because the error log text file is hard to read and understand. One thing the team did add to the documentation is a “troubleshooting” document.
Next, installation of the LOB Adapters which is an option on the setup screen of the main BizTalk setup. Just follow the steps:
- Install Microsoft WCF LOB Adapter SDK
- Install Microsoft BizTalk Adapter Pack
- Install Microsoft BizTalk Adapter Pack(x64)
- Install Microsoft BizTalk Adapters for Enterprise Applications
When BizTalk and the adapter pack are installed, then also the new AppFabric Connect is installed.
Next, the ESB Toolkit 2.1. This is just a matter of running the correct MSI. The installation documentation specifies the pre-requisites.
The ESB Toolkit 2.1 must be configured using the ESB Configuration tool, that can be found in the start menu after the toolkit is installed. There you can configure the ESB Exception and Itinerary database and services you want to use. Before you can configure the services, you first need to apply the database configuration. Finally you need to specify the type of configuration to use, File or SSO. For single server installations File is recommended, SSO is more suitable for multi server installations.
Next the individual components of the ESB Toolkit 2.1 can be deployed into BizTalk. In the ProgramFiles folder there is a Microsoft BizTalk ESB Toolkit 2.1 folder with the necessary MSI installer files that can be imported into BizTalk.
There is quite an installation document for the ESB Toolkit 2.1 you can follow. This document contains some catches like the samples depend on the fixed path “C:\Projects\Microsoft.Practices.ESB” and a call to ServiceModelReg with a not existing parameter “-y”.
The ESB portal is in the ESB Sources that can be found in the ESB Toolkit 2.1 folder. I had some difficulties setting up the ESB Portal, because the SharePoint Foundation 2010 site was in its way so I had to change the port number of the default website. The portal still runs on .NET 3.5 instead of v4.0. and I assume that not much has changed on the portal, also because the assembly info for the portal mentions “Microsoft ESB Guidance for Microsoft BizTalk 2006 R2” and the UDDI code file contains an obsolete call to the configuration namespace. The UI also looks the same.
Finally installation of AppFabric. Default the hosting services are selected but I also want the caching services to be installed. Installation is a matter of waiting and the configuration is also straight forward.
Now I have a (virtual) base image to do some BizTalk 2010 testing on. :-)
Today the long awaited release date of the 7th version of BizTalk Server was announced: October 1st, 2010
For this announcement Microsoft refreshed its BizTalk website. There you can already download the 120-day trial version. What’s interesting and new with this release is the free developer edition which was also already released. In previous BizTalk versions the developer edition cost around $500.
On the product team blog there is a nice post about the upcoming release.
Via a blog post it came to my attention that the BizTalk user groups of Australia and New Zealand organise a combined event around BizTalk Server 2010. It is called BizTalk Saturday. It looks like a very nice event, so if your in the neighbourhood you should attend.
One of the presentations I found scheduled is about the ESB Toolkit 2.1. Off course I know about the ESB Toolkit 2.0, but 2.1 hasn't had so much attention yet.
It is a release especially for the platforms supported with BizTalk Server 2010 like Visual Studio 2010. Information can be found here.
So, what is new in this release? From the Microsoft site:
The Microsoft BizTalk ESB Toolkit 2.1 extends the capabilities of BizTalk Server 2010. The following list summarizes the additional support extended in Microsoft BizTalk ESB Toolkit 2.1:
- Added support for Visual Studio 2010 Visualization and Modeling SDK for the Itinerary designer.
- Support both .NET Framework version 4 and .NET Framework 3.5.
- Supports the use of itineraries developed in Microsoft BizTalk ESB Toolkit 2.0.
- The Itinerary designer now supports copying and pasting itinerary shapes.
- A new itinerary project template, BizTalk ESB Itinerary designer, provides an easy option to create itinerary projects under BizTalk Projects.
- Opening a new project in the Itinerary designer sets the export mode to Strict by default.
- Added a new itinerary model property, Require encryption certificate, in the Itinerary designer to enable and disable encryption certificate while validating the itinerary. This flag is set to True by default.
The picture below shows the ESB Toolkit 2.1 core engine components. Although I haven't spend a lot of time on this release yet, one thing that caught my eye was the mentioning of Enterprise Library 4.0 while Enterprise Library 5 has been released for some months. Also the UDDI 2.0 is in the picture, while the toolkit requires UDDI 3.0 according to this documentation.
So althought the ESB Toolkit 2.1 download isn't mentioned as a beta download (while BizTalk 2010 is), the documentation is marked as prerelease and inconsistent in some places.