ESB Toolkit 2.2 Itinerary Designer Installation

Brian Loesgen has a post on his blog describing an issue he ran into performing a clean build of BizTalk Server 2013 and ESB Toolkit 2.2, where the Itinerary Designer extension is not registered in Visual Studio 2012 after the ESB Toolkit 2.2 installation step.

I experienced this also so it may be more widespread than first thought. I’d be interested to hear how many other people run into it; it might be the case that this step will need to be added to installation instructions.

Before Brian pointed me to his post I had resolved this inadvertently when I installed the latest Visual Studio 2012 update, which would have resulted in a similar command being executed with the same outcome.

ESB Toolkit 2.1 Installation Checklists

Overview

One of the biggest barriers to ESB Toolkit adoption I have come across is the installation and configuration overhead. This is a genuine concern, especially when you need to deviate from the standard configuration. If project timelines are tight, this can result in the ESB Toolkit being overlooked.

Through working on a number of ESB Toolkit based solutions for different customers I have compiled some high level installation checklists that cover the most common environment configurations. I will cover each of these in this blog series with a view to removing the initial barrier to building solutions based on the ESB Toolkit.

The Installing BizTalk 2010 ESB Toolkit 2.1 guide and Installing the BizTalk ESB Toolkit MSDN library topic should be used as a reference for drilling down into the detail of the steps included in the checklists.

If there is anything you have come across that you feel should be included in the checklist please get in touch and we can look at adding it.

Checklists

1. ESB Toolkit 2.1 Core Standalone Installation Checklist

ESB Toolkit 2.1 Core Standalone Installation

Environment

The environment configuration covered under this checklist is as follows:

• 1 x 64-bit Windows Server 2008 R2 Enterprise Edition
• BizTalk Server 2010 Developer Edition
• SQL Server 2008 R2 Developer Edition
• ESB Toolkit 2.1
• All programs are installed on a drive isolated from the OS, an E drive in this case

Checklist

1. Install the BizTalk ESB Toolkit 2.1-x64.msi
2. Install the Microsoft.Practices.Services.Itinerary.DslPackage
3. Import and install the Microsoft.Practices.ESB.CORE64.msi
4. Create a 32-bit Host, Host Instance and assign the SQL send and receive handlers to it
5. Configure the All.Exceptions send port in the Microsoft.Practices.ESB application to use the 32-bit SQL send handler
6. Launch the ESB Configuration Tool and configure the toolkit
7. Copy the following ESB Toolkit pipeline components from the “C:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components” folder to the “E:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components” folder:
   • Microsoft.Practices.ESB.ExceptionHandling.PipelineComponents.dll
   • Microsoft.Practices.ESB.Itinerary.PipelineComponents.dll
   • Microsoft.Practices.ESB.Namespace.PipelineComponents.dll
   • Microsoft.Practices.ESB.PipelineComponents.dll
8. Copy the ItineraryDescription.xsd from the “E:\Program Files (x86)\Microsoft BizTalk ESB Toolkit 2.1\Web\ESB.ItineraryServices.Response.WCF\App_Data” folder to the “E:\Program Files (x86)\Microsoft BizTalk ESB Toolkit 2.1\Web\ESB.ItineraryServices.Generic.Response.WCF\App_Data” folder
9. Add the SQL Server Service Analysis account as a User to the BAMStarSchema database and grant it the db_datareader role
10.   Deploy the BAM activities
11.   Configure Tracing
12.   Restart host instances and perform an IISRESET
13.   Verify all services are browse-able

Download OneNote Checklist