Share via

Create or Modify a Windows Installer Package for the Exception Management Samples

  • 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.

This section describes how you can create or edit a Windows Installer package for the Microsoft ESB Guidance Exception Management samples.

To create or modify a Windows Installer package for the ESB Exception Management samples

  1. Before you create or modify a Windows Installer package for the ESB Exception Management samples, ensure that the BizTalk application hosting the samples (the application named GlobalBank.ESB) is successfully installed and deployed by following all the steps in the procedure Install the ESB Exception Management Samples from the Solution Project.

  2. Open the \Source\Samples\Exception Handling\Install\Scripts folder in Windows Explorer, and then double-click the script named 2.ALL_AddResoucesGenerateBindingandArtifactList.cmd.This script adds the following artifact to the existing GlobalBank.ESB BizTalk application:

    • Binding file with the TargetEnvironment set to DEV_EXC

    Note

    This script produces two artifact files named GlobalBank.ESB.ExceptionHandling_Artifacts.xml and GlobalBank.ESB.ExceptionHandling_Artifacts_NOBINDINGS.xml in the \Source\Samples\Exception Handling\Install root folder. These files define the contents of the Windows Installer packages created in the following step. By default, the two artifact files are identical, and they list the artifacts to install in the BizTalk application resources folder. Before continuing to the next step, you MUST edit these to determine which BizTalk application resources will be included in the .msi files. You can remove assemblies, bindings, or Web directories, and thereby control exactly what the .msi file will contain.
    If the installation process uses a binding file, this script will export a NEW binding file that will overwrite the original one. Therefore, you should back up the original binding file before you run this script. Also, be prepared to edit the newly exported binding file so that it can be imported as part of the Windows Installer package when you run the UpdateBindingExportMSI script.

  3. In Windows Explorer, open the \Source\Samples\Exception Handling\Install\Scripts folder, and then double-click the script file named 3.ALL_UpdateBindingExportMSI.cmd to create the .msi installer files. This process uses the two artifact files created in the previous step to create two Windows Installer packages, one for each file.