Geeks With Blogs

Paul's Petrov Whiteboard [BizTalk, Enterprise Application Integration, Business Process Automation, SOA, .NET]

I just installed Microsoft Enterprise Service Bus Guidance framework (November 2007 version for BizTalk 2006 R2). Although lengthy installation process is well documented in the accompanying help file I ran into multiple issues and it took a couple of days to sort everything out. I'd like to mention here major problems/solutions in case somebody decides to go through the same. First, if you install on other than default location (C:/%PROGRAM_FILES% and C:/Projects) make sure to update all scripts and command files as well as bindings. Second, I had issue with UDDI service configuration. It wouldn't install until I enabled NTLM authentication for IIS. It is done by executing IIS utility script per this MS article. But this command worked only when I dropped quotes around Negotiate,NTLM contrary to MS KB article. Also, make sure the default web site ID is "1". Some of my computers had it set to different numbers so I had to change command line appropriately.  In the end command that worked looks like this:

cscript adsutil.vbs get w3svc/<Default Web Site ID>/root/NTAuthenticationProviders Negotiate,NTLM

Another problem is that assemblies in MSI packages are signed with different key comparing to source projects. So even if you install all ESB components from source you will run into this issue because some of the projects  reference assemblies from packaged installation. Solution is to go through all project references, remove them and add new to ones generated from source code. The same applies to sample applications. Don't install them from MSI if you chose source code based ESB installation. Open project, update references, rebuild and deploy.

Posted on Friday, February 20, 2009 6:58 PM BizTalk , EAI | Back to top

Comments on this post: Microsoft ESB Guidance installation

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Paul Petrov | Powered by: