For installing ESB Toolkit 2.0 in a single machine 32 bit environment you should look at this link Quick Learn.
I recently installed and configured ESB Toolkit 2.0 on Windows 2003 SP2 64 bit OS. I am sharing my install notes with you so you can benefit from my experience. Use these instructions to install and configure ESB Toolkit in development environment only. Before installing the ESB Toolkit I had already installed and configured BizTalk 2009
- Set the trust level of BizTalkServerApplication and BizTalkServerIsolatedHost to “untrusted”. This is needed because all the bindings for ESB Sample expect these hosts to be untrusted.
- Run BizTalk ESB Toolkit 2.0-x64.msi
- The installer will extract all the files to C:Program Files (x86)Microsoft BizTalk ESB Toolkit 2.0
- Read the Readme file from C:Program Files (x86)Microsoft BizTalk ESB Toolkit 2.0Readme.htm
- Also read Get Started C:Program Files (x86)Microsoft BizTalk ESB Toolkit 2.0GettingStarted.htm
- Read know issues document from C:Program Files (x86)Microsoft BizTalk ESB Toolkit 2.0KnownIssues.htm
- In addition to this you should read the known issues from http://msdn.microsoft.com/en-us/library/dd897942.aspx
- Use the section “Installing the BizTalk ESB Toolkit” section from Microsoft BizTalkESBToolkit.chm file.
- Install all the Prerequisites.
- Import the C:Program Files (x86)Microsoft BizTalk ESB Toolkit 2.0Microsoft.Practices.ESB.CORE64.msi in BizTalk Server 2009 Administration Console.
- Run c:Program Files (x86)Microsoft BizTalk ESB Toolkit 2.0Microsoft.Practices.ESB.CORE64.msi and accept all defaults
- Run C:Program Files (x86)Microsoft BizTalk ESB Toolkit 2.0BinESBConfigurationTool.exe
- Follow the directions in section “Configuring Services and Components” to configure all the databases and services.
- This configuration is performed in steps. First you configure the database and then you can configure the corresponding service.
- Create c:projects
- Create c:projectsmicrosoft.practices.ESB folder
- Uncheck the read-only attribute on c:projectsmicrosoft.practices.ESB
- Extract C:Program Files (x86)Microsoft BizTalk ESB Toolkit 2.0ESBSource.zip to c:projectsmicrosoft.practices.ESB
- The previous setup will create keys and source folders. Run Visual Studio Tool Command prompt and change directory to c:projectskeys. Run the command sn -k Microsoft.Practices.ESB.snk.
- Install Management Portal.
- Open Windows PowerShell(32) command prompt
- Run the command Get-ExecutionPolicy. If the response to this command is not “RemoteSigned” you will need to run Set-ExecutionPolicy RemoteSigned This will allow you install scripts to run.
- Navigate to C:ProjectsMicrosoft.Practices.ESBSourceSamplesManagement PortalInstallScripts
- Run the command .Management_Install.ps1 1
- Open the solution C:ProjectsMicrosoft.Practices.ESBSourceSamplesManagement PortalESB.AlertServiceESB.AlertService.sln in Visual Studio.
- Change the configuration type to Release and build the solution.
- Run C:ProjectsMicrosoft.Practices.ESBSourceSamplesManagement PortalESB.AlertService.InstallReleaseSetup.exe
- When you are prompted for user name you should enter it in format domainusername format. Even if you are doing a single computer install you should enter computernameusername.
- Run UDDI Services Management Console. Right click on UDDI and select Properties. Select Security tab. Uncheck “Require SSL for publication to this site”.
- Open the solution C:ProjectsMicrosoft.Practices.ESBSourceSamplesManagement PortalESB.UDDI.PublisherService ESB.UDDI.PublisherService.sln
- Change the build configuration to “Release” and build.
- Run C:ProjectsMicrosoft.Practices.ESBSourceSamplesManagement PortalESB.UDDI.PublisherService.InstallReleaseSetup.exe
- Follow the instruction in section Configuring Exception Management InfoPath Form Template Shares of section “Installing the BizTalk ESB Toolkit” of MicrosoftBizTalkESBToolkit.chm
- Follow the Security Considerations section of section “Installing the BizTalk ESB Toolkit” of MicrosoftBizTalkESBToolkit.chm
- Install Exception Management Samples
- Start the BizTalk Application Microsoft.Practices.ESB.
- Edit the file C:ProjectsMicrosoft.Practices.ESBSourceSamplesException HandlingInstallScriptsSetup_bin.cmd. Comment out the line that executes
- Run C:ProjectsMicrosoft.Practices.ESBSourceSamplesException HandlingInstallScriptsSetup_bin.cmd
- Open Windows PowerShell(32) command prompt(You need this because the install relies on Explorer OM which does not support 64 bit)
- Navigate to C:ProjectsMicrosoft.Practices.ESBSourceSamplesException HandlingInstallScripts
- Run the command .ExceptionHandling_Install.ps1 1
- This will install the exception handling samples. Now you are all set to run the exception handling samples. You can use similar steps to install other samples.
- Create a 32 bit host and change and send and receive handler for SQL Adapter. This is needed because the SQL Adapter cannot run in 64 bit mode.
- Enable the web service extension for btshttpreceive.dll
- Configure IIS for both Kerberos and NTLM using the instructions http://support.microsoft.com/kb/215383
- Install SQLXML 4.0 SP1 from http://blogs.digitaldeposit.net/saravana/post/2009/06/10/ESB-Toolkit-20-MicrosoftDataSqlXml-issue.aspx This is needed by the exception management components to write the expection the the database. Thanks to Saravana Kumar for discovering this issue and posting a fix for it.
- Install BAM definitions by executing these commands:
cd C:Program Files (x86)Microsoft BizTalk Server 2009Tracking
Bm.exe deploy-all -DefinitionFile:”C:Program Files (x86)Microsoft BizTalk ESB Toolkit 2.0BamMicrosoft.BizTalk.ESB.BAM.Itinerary.xml”
Bm.exe deploy-all -DefinitionFile:”C:Program Files (x86)Microsoft BizTalk ESB Toolkit 2.0BamMicrosoft.BizTalk.ESB.BAM.Exceptions.xml”