Home > BizTalk Server, ESB Toolkit > ESB Toolkit 2.1 Core Standalone Installation

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

Advertisements
  1. January 21, 2014 at 16:42

    Nice checklist Colin thanks. One minor correction for point 7, the pipeline components would be copied from C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit 2.1 rather than …\Microsoft BizTalk Server 2010\Pipeline Components

    • January 22, 2014 at 09:51

      Thanks Rob.

      Yes they could be copied from the ESBT installation directory, “E:\Program Files (x86)\Microsoft BizTalk ESB Toolkit 2.1\Bin” in this case, but I prefer to copy the assemblies that are placed in the “C:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components” folder as part of the ESBT configuration.

      Pipeline Components

      I haven’t verified whether this is still an issue in ESBT 2.2. Have you come across it?

  1. April 8, 2013 at 16:08

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: