Share via

Operating System and Applications

  • Article
Retired Content

This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

The following list describes the Windows operating system and core services and features required by the ESB Guidance:

  • Microsoft Windows Server 2003 with Service Pack 2 installed
  • Microsoft .NET Framework 3.0
  • Hot fix KB923028 (this fixes the "Unhandled Exception: System.AccessViolationException" error when you run a .NET Framework 2.0 Remoting application, see https://support.microsoft.com/kb/923028)
  • Internet Information Services (IIS) 6.0 (used for Web services and the ESB Management Portal)
  • SQL Server 2005 SP2 including the Database Service, Analysis Services, and Integration Services; or SQL Server 2000 including the Database Service and Data Transformation Service, and with Service Pack 3 or later installed
  • Visual Studio 2005 (C# for most projects; C++ for the JMS pipeline component) with Service Pack 1 or later installed
  • InfoPath 2003 or InfoPath 2007 (used to render exception details generated by the ESB Exception Management Framework)
  • Enterprise Library 3.1 (this is required only for the ESB Management Portal)

BizTalk Server 2006 R2

The Microsoft ESB Guidance integrates with Microsoft BizTalk Server 2006 R2. The following list shows the minimum version and optional features that you must install:

  • Microsoft BizTalk Server 2006 R2, including Business Activity Monitoring (BAM)
  • BizTalk MQ Series Adapter installed and configured using the default name (only if using the Microsoft ESB Guidance JMS component or the samples that require MQSeries)
  • BizTalk Server 2006 R2 Hotfix KB943871, which adds support for new BizTalk Error Reporting properties (ErrorReport.FailureTime, ErrorReport.FailureAdapter, ErrorReport.FailureMessageID, ErrorReport.FailureInstanceID)

Microsoft UDDI Service

The ESB Guidance makes extensive use of, and integrates with, UDDI registries. If you intend to perform UDDI resolutions, you must install and configure a UDDI service such as Microsoft UDDI. Use the Add/Remove Windows Components feature in Windows Server 2003 to install this service.

Note

If you try to run the UDDI administrative interface under .NET Framework 2.0, you will discover a class ambiguity error because the TreeNode class also exists as part of the UDDI system, as within the .NET Framework 2.0. You must edit the Explorer.aspx page in both the UDDI\webroot\edit and UDDI\webroot\admin folders to change the TreeNode class references to UDDI.Web.TreeNode.