Alright Folks,
I've been beating around the bush for quite some time now trying to Install ESB Toolkit 2.0 on Windows Server 2008 (32 bit) and ran into bunch of problems. Everytime I install it, something or the other doesn't work. And everytime it happens, I uninstall everything and re-intall it just to get it right. I've spent the whole of last week to make sure that every single feature works on my system so that I don't have scratch my head later on...
I am going to lay down step by step instructions to Install the ESB Toolkit. If you follow these in the order specified, rest assured, you'll have a perfectly working copy of the Toolkit!!!
Here we go:
First of all, there are a bunch of pre-requisites you've got to take care of, before you get anywhere close to installing the ESB Toolkit 2.0. Note that these instruction are for installing it on 32bit Windows 2008 server. Intalling on 64 bit server might still work but I am not sure, never tried it before...
- Install Microsoft Windows 2008 Server (32bit) operating system. Once you do that, run a Windows Update and Install all the security updates. Make sure you get SP1.
- Install .NET framework 3.5 SP1.
- Install IIS 7.0 along with IIS 6.0 extensions. ( This is used by the WebServices that come along with ESB Toolkit for processing Itineraries, Exception Management, ESB portal etc.,)
- Install Microsoft Sql Server 2008/2005. ( This is where BizTalk stores all the Application data and ESB Toolkit stores data pertaining to BAM, Itineraries, Exception Management etc). Make sure you install Reporting Services and Integration Services.
- Install Microsoft BizTalk Server 2009 Enterprise Edition. Make sure you check all the optional features including BAM components. You may not need it now immediately but eventually you will need it. So, unless space is a constraint, just go for it.
- Install Visual Studio 2008 SP1. If you are planning to develop applications on this Box, then you've got to install VS 2008 too. After this step, it might screw up some BizTalk extensions. So, put the BizTalk 2009 CD in drive and run a repair. That'll take care of things, if anything got screwed up after installing SP1 for VS 2008.
- Install Microsoft Chart Controls for .NET Framework 3.5. (This would be used by ESB Portal)
- And now, the most important thing. Install Microsoft Enterprise Library 4.1. This step is missing in the Microsoft Documentation. As a result of which, I had to uninstall it and get a fresh copy again...
Before you go ahead, make sure everything is working fine. Open up the BizTalk Administration console and check to see if the snap-in is populating defaut applications etc., fine. Make sure that Visual studio is showing a new template for creating BizTalk Projects. Actually, go ahead annd create a new test project. When I tried it on my system, creating a BizTalk project failed and I got the error messge 'BizTalk Project creation failed' or something like that... At this time, I've run the BizTalk repair... It set everything right... Once we have the pre-requisites up and running fine, get the latest MSI file for the ESB Toolkit from the Microsoft Website and install it.
This would unpack all the required files in to C:\Program Files\ESB Toolkit 2.0\
- Open up the BizTalk Admin Console, right click on the Applications node and import the C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Microsoft.Practices.ESB.CORE.msi file. After this, run the Installer too.
- Do the same thing for Microsoft.Practices.ESB.ExceptionHandling.msi file. This time check the "Overwrite resources" when importing the file in the Wizard. Run the Installer too.
- Do the same thing for Microsoft.Practices.ESB.JMS.msi file. This time check the "Overwrite resources" when importing the file in the Wizard. Run the Installer too.
Now is the time to run bunch of scripts. But to do this, you've got to set execution policy to 'Unrestricted'. This would give you complete privilages to run the power scripts.
Open up the common prompt or power shell prompt and run the following command.
set-executionpolicy Unrestricted
Extract the ESBSource.zip file to C:\Projects\Microsoft.Practices.ESB\. This would create two directories in it. Source and Keys. Source will have the source code for ESB WebSites, Managment Portal and all the samples that come along with it. The key folder is used to store the strong name keys and this would be blank initially. You need Strong Name Key files to sign the assemblies before you deploy them to Global Assembly Cache (GAC). At this point, generate a strong name key which would be used by all the applications in the source folder. Open up the Visual Studio Command Prompt, navigate to the keys folder and type
sn -k Microsoft.Practices.ESB.snk
That would create the required strong name key.
Now is the time to install the ESB Management Portal.
- Go to C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\Install\Scripts. Double click on Management_Install.cmd. This would install the portal and create all the required virtual directories in the IIS.
- Open the IIS, make sure ESB.Portal Virtual directory is created and is pointing to the correct folder. In the right pane, click on authentication and make sure that Windows Authentication is enabled for this folder.
- Open the ESB Configuration Tool located at C:\Program Files\Microsfot BizTalk ESB Toolkit 2.0\Bin\ESBConfigurationTool.exe and configure the settings for Exception Management, ESB Core Components and Configuration nodes.
Open the node Exception Management, Select Database, click on Enable Exception Management Database and click on Apply Configuration. Do the samething for ESB Core Components.
- Now, click on Configuration and make sure to save the SSO configuration information in the Configuration File instead of datastore. This would store all the information in the Esb.Config file. This would make it easy for the Itinerary Designer to pick up the changes made to configuration file on the fly.
- Once you do that, make sure all the users who are planning to use the portal are added to the following groups. BizTalk Isolated Host users, BizTalk Application Users and all the SSO related groups.
It's time to set the BAM definations. Run the following commands.
Got to the following directory in the command prompt : C:\Program Files\Microsoft BizTalk Server 2009\Tracking.
Run the following comands
- bm.exe deploy-all -DefinitionFile:"C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bam\Microsoft.BizTalk.ESB.BAM.Itinerary.xml".
- bm.exe deploy-all -DefinitionFile:"C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bam\Microsoft.BizTalk.ESB.BAM.Exceptions.xml"
Now is the time to cure the unhandled exception error that is generated when trying to access the ESB Portal. Go to C:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation and run the following command.
ServiceModelReg.exe -r -y
This should set everything right... I hope I've included every bit of information required to install the ESB Toolkit... I followed the exact same instructions and its working for me. I hope it works for you too...
And I wish you a Very Happy BizTalking. If you run into issues, do post a comment, I'll get back to you as soon as I can.
Thanks
--
Preetham Reddy Chamakura