Installing the ESB Management Portal

This section describes the process for installing the ESB Management Portal from the solution project included with the Microsoft BizTalk ESB Toolkit.

To install the ESB Management Portal

  1. Install either the BizTalk ESB Toolkit Core or the ESB Exception Management Framework as described in previous topics, and then confirm correct installation and configuration before you install the portal.
  2. Create a folder named Projects in the root of your C: drive, and create a subfolder named Microsoft.Practices.ESB within this folder.
    In the current release, the supported installation is for the files to reside in the folder C:\Projects\Microsoft.Practices.ESB. The BizTalk binding files that ship with the samples depend on this path.

  3. When you install the download, it includes a .zip file called in the installation location you specified (by default, C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0). Uncompress the file into the C:\Projects\Microsoft.Practices.ESB folder. This will create folders named Keys and Source that contain the sample key and the samples with source code. The Source folder contains the source code for the sample application, and the Keys folder contains the public keys used to sign the assemblies in the sample applications.
  4. Before you run the samples, remove the read-only attribute on the C:\Projects\Microsoft.Practices.ESB\ folder so that the samples install correctly.
  5. If you have not used PowerShell scripts before, you must open PowerShell as an Administrator and run the following command:
    set-executionpolicy unrestricted
    For more information about PowerShell, see the Windows PowerShell Blog and Windows PowerShell on MSDN.

  6. Open a command prompt as an administrator and run the following command to ensure WCF script maps are registered:
    C:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation>ServiceModelReg.exe -r -y
  7. Run the UDDI Publisher tool (you can install it at %ESB Install Folder%\Bin\Microsoft.Practices.ESB.UDDIPublisher.exe).
  8. Navigate to \Samples\Management Portal\Install\Scripts, and then run ManagementInstall.cmd from the command prompt.

To verify that the ESB Management Portal has been configured

  1. Verify that the new IIS virtual directory for the portal Web application has been created by the install script and has the following settings:
    • Alias: ESB.Portal
    • Directory: C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal
    • Allow the following: Read, Run Scripts (such as ASP)
    • Allow anonymous access: No
    • Application Pool: EsbPortalNetworkAppPool
  2. Verify that the following IIS virtual directories were created by the install script:
    • ESB.Exceptions.Service. This service provides access to BizTalk ESB Toolkit Exception Management database.
    • ESB.BAM.Service. This service provides access to BizTalk ESB Toolkit BAM information.
    • ESB.UDDI.Service. This service provides UDDI 3 query and publishing functionality.
  3. Open the Visual Studio solution named ESB.Portal.sln from the C:\Projects\Microsoft.Practices.ESB\Samples\Management Portal\ESB.Portal folder, and then make sure that the <connectionStrings> section of the Web.config file contains the correct connection strings for the ESBAdmin database.
  4. Check the portal for authentication, authorization, and general configuration settings as described in the following sections.
The ESB Management Portal is not compatible with Internet Explorer 8.0. You will need to run Internet Explorer 8.0 in compatibility mode to see the menus.

Now continue to the next task: Checking Portal Configuration Settings.

Community Additions