System Requirements

Hardware Requirements

Software Requirements

Feature Installation Prerequisites

Feature Configuration Prerequisites

Supported Host Systems

Removed Features

Product Installation

Upgrading from previous versions of Transaction Integrator

Installing HIS and Enterprise Single Sign-on (ESSO)

Upgrading from an Earlier Version of Enterprise Single Sign-on

Configuring HIS and ESSO

Unattended Installation of HIS

Removing HIS

Unattended Removal of HIS

Removing ESSO

Unattended Removal of ESSO

Known Issues with Host Integration Server

Host Integration Server Custom Actions with Documentation

Enterprise Single Sign-on Custom Actions with Documentation

Copyright

Last updated: August, 2010

This document contains information about installing Microsoft® Host Integration Server 2010.

System Requirements

Hardware Requirements

You must have the following minimum hardware on the computer on which you want to install Host Integration Server.

  • 6-gigabyte (GB) hard disk space

  • VGA (800 x 600) or higher-resolution with 256 colors  

  • Developer Design Tools require VGA (1024x768) or higher-resolution with 256 colors

Software Requirements

Operating Systems

You must have one of the following operating systems (32-bit x86 or 64-bit x64) running on the computer on which you want to install Host Integration Server.

  • Windows Server 2003 R2 SP2

  • Windows Vista® SP2

  • Windows 7

  • Windows Server 2008 SP2

  • Windows Server 2008 R2

  • Virtualization with Hyper-V

Other Software

You must also have the following additional software installed to install Host Integration Server.

  • Microsoft .NET Framework version 3.5 SP1

  • Microsoft XML Core Services (MSXML) 6.0 SP1

Note

You can use setup to install redistributable prerequisites automatically from the Web or from a pre-downloaded CAB file. Automatically installing from the Web or downloading the CAB file requires Internet access. You can download the CAB file from http://go.microsoft.com/fwlink/?LinkID=133541.

Feature Installation Prerequisites

The following table lists the feature and software requirements for Host Integration Server Setup.

Feature

Requirement

Developer Design Tools (Transaction Integrator, Host Files, Host Data Conversion)

Visual Studio® 2008 SP1 (with C++ and C#) or Visual Studio 2010 (with C++ and C#)

Developer Design Tools (Message Queue)

Visual Studio 2010 (with C++ and C#)

WCF Channel for WebSphere MQ

.NET Framework 4

BizTalk Adapters and Pipeline Component

BizTalk Server 2009 or BizTalk Server 2010

Feature Configuration Prerequisites

The following table lists the software required to configure Host Integration Server Configuration (post-Setup).

Feature

Requirement

DB2 Distributed Transactions

SQL Server® 2008 SP1 or SQL Server 2008 R2

Transaction Integrator

SQL Server 2008 SP1 or SQL Server 2008 R2

Enterprise Single Sign-On

SQL Server 2008 SP1 or SQL Server 2008 R2

BizTalk Adapter for WebSphere MQ

IBM WebSphere MQ Client 6.0 with Fix Pack 6.0.1.1

IBM WebSphere MQ Client 7.0 with Fix Pack 7.0.0.1

IBM WebSphere MQ Extended Transactional Client 6.0 with Fix Pack 6.0.1.1

IBM WebSphere MQ Extended Transactional Client 7.0 with Fix Pack 7.0.0.1

WCF Channel for WebSphere MQ

IBM WebSphere MQ Client 6.0 with Fix Pack 6.0.1.1

IBM WebSphere MQ Client 7.0 with Fix Pack 7.0.0.1

IBM WebSphere MQ Extended Transactional Client 6.0 with Fix Pack 6.0.1.1

IBM WebSphere MQ Extended Transactional Client 7.0 with Fix Pack 7.0.0.1

IBM WebSphere MQ Server 6.0 with Fix Pack 6.0.1.1

IBM WebSphere MQ Server 7.0 with Fix Pack 7.0.0.1

Top of page

Supported Host Systems

The following table lists supported host systems.

Host System

Product and Version

Operating Systems

IBM z/OS V1.9, V1.10 and V1.11

IBM zVSE V4.1 and V4.2

IBM zVM V5.4 and V6.1

IBM i5/OS V5R4 and V6R1

Transaction Processing Systems

IBM CICS for z/OS V3.1, V3.2 and V4.1

IBM IMS V10 and IMS V11

IBM i5/OS V5R4 and V6R1

Message Processing Systems

IBM WebSphere MQ for z/OS V 6.0, V7.0 and V7.0.1

IBM WebSphere MQ for z/VSE V3.0

IBM WebSphere MQ for iSeries V5.3 and V6.0

Relational Database Management Systems

IBM DB2 for z/OS V8.1 and DB2 for z/OS V9.1

IBM DB2 for i5/OS V5R4 and V6R1

IBM DB2 for Windows, AIX, HP-UX, Solaris, Linux V9.1, V9.5, V9.7

Files Systems

IBM DFSMS DFM z/OS V1.9, V1.10 and V1.11

IBM i5/OS V5R4 and V6R1

Top of page

Removed Features

The following features have been removed from Host Integration Server 2010.

  • Microsoft Data Link Control (DLC) network protocol and the DLC 802.2 Link Service have been removed from Host Integration Server. You should use the Internet Protocol-Data Link Control (IP-DLC) Link Service that is based on the industry-standard High Performance Routing over Internet Protocol (HPR/IP).

  • NetView Run Command (NVRunCmd) Service has been removed from Host Integration Server. You should use File Transfer Protocol (FTP) over TCP/IP as an alternative to the NVRunCmd feature.

  • Microsoft ODBC Driver for DB2 has been removed from Host Integration Server. You should use the Microsoft ADO.NET Data Provider for DB2, Microsoft OLE DB Provider for DB2, or Microsoft BizTalk Adapter for DB2.

  • Microsoft Host File Transfer ActiveX Control has been removed from Host Integration Server. You should use the Microsoft ADO.NET Data Provider for Host Files or Microsoft BizTalk Adapter for Host Files.

  • Microsoft AS/400 Data Queues ActiveX Control has been removed from Host Integration Server. The HIS team would like feedback from customers who require direct access to AS/400 data queues to prioritize work on a replacement technology. You can provide feedback about the Host Integration Server on the Microsoft Connect site listed below.

  • Microsoft Message Queue to MQ Series Bridge (MSMQ Bridge) has been removed from Host Integration Server. You should use Microsoft BizTalk Server 2010 together with one of the two Microsoft BizTalk Adapters for IBM WebSphere MQ (MQ Series), or the Microsoft WCF Channel for WebSphere MQ.

  • Transaction Integrator support for Component Object Model (COM) libraries has been removed from Host Integration Server. You should use the Transaction Integrator Designer to convert COM type libraries to .NET assemblies, and then re-deploy the components.

  • Transaction Integrator support for .NET Remoting has been removed from Host Integration Server. You should use the HIS support for direct .NET calls.

Top of page

Product Installation

Existing Product Upgrade

This release supports an in-place upgrade of earlier versions of HIS. The Host Integration Server 2010 setup automatically upgrades your existing configuration. The following releases are supported for automatic upgrade.

  • Host Integration Server 2006

  • Host Integration Server 2006 SP1

  • Host Integration Server 2009

  • BizTalk Adapters for Host Systems 1.0

  • BizTalk Adapters for Host Systems 1.0 SP1

  • BizTalk Adapters for Host Systems 2.0

HIS 2010 has limited interoperability with earlier versions of Host Integration Server. Earlier versions of HIS and SNA Server will not automatically upgrade. You will need to manually migrate configuration information for those versions.

Upgrading a Host Integration Server Subdomain

When upgrading an existing Host Integration Server subdomain, all secondary configuration servers should be upgraded first. Once all the secondary configuration servers have been upgraded to the new release, you can upgrade the primary configuration server.

Upgrading from previous versions of Transaction Integrator

In HIS 2010, support for COM Type Libraries (TLBs) has been dropped for both Windows-initiated processing (WIP) and Host-initiated processing (HIP). After an upgrade has been performed, existing deployed TI COM objects will no longer function. You can convert the TI type libraries (TLBs) to .NET assemblies using the Transaction Integrator Conversion Tool. For more information, see the Transaction Integrator Conversion Tool topic in Host Integration Server online Help.

For Host Initiated Processing, the use of a standalone TI metadata file (TIM) has been discontinued. Metadata is now included as part of the implementing assembly, or pristine assembly. All currently deployed HIP objects must be converted using the Transaction Integrator Conversion Tool or the Designer.

The version HIS that was used to create the Type Library or .NET assemblies, as well as the programming and hosting model, determine the steps that need  to be performed during the upgrade.  For more information, see the Migration Considerations for Earlier Versions of Windows-Initiated Processing (WIP) topic in Host Integration Server online Help.

Upgrading previous versions of Transaction Integrator HIP

Follow these steps to upgrade single and multiple computers.

Single Computer HIP Database

  1. Upgrade the computer to HIS 2010.

  2. Run the TIConversionTool against the TIM files to create HIS 2010 HIP assemblies. Place the generated HIS 2010 HIP Assemblies in the same location that the TLB files were located.

  3. In TI Manager HIP Objects folder, right click and select Reload Metadata Files.

For more information, see the Transaction Integrator Conversion Tool topic in Host Integration Server online Help.

Multiple Computer HIP Database

Follow these instructions to upgrade the first computer to HIS 2010.

  1. Upgrade the computer to HIS 2010.

  2. During configuration, point the TI configuration to the common HIP database.

  3. From TI Manager on the HIS 2010 computer, export the HIP configuration.

  4. Run HIS 2010 configuration again. In the Transaction Integrator configuration options, specify a new HIP Database.

  5. From TI Manager on the HIS 2010 computer, import the HIPExportConfig.xml file that you created with the Import Computer and Globals option.

  6. Run the TIConversionTool against the TIM files to create HIS 2010 HIP assemblies.

  7. Place the generated HIS 2010 HIP assemblies in the same location that the TIMs are located in.

  8. In TI Manager HIP Objects folder under All Tasks, right-click and select Reload Metadata Files.

Follow these instructions to upgrade subsequent computers.

  1. Upgrade the computer to HIS 2010.

  2. During configuration, point the TI configuration to the new HIP database created during the upgrade of the first computer.

  3. From TI Manager on this HIS 2010 computer, import the HIPExportConfig.xml file using the Import Computer Only option.

  4. Run the TIConversionUtility against the TIM files to create the HIS 2010 HIP assemblies.

  5. Place the generated HIS 2010 HIP assemblies in the same location that the TIMs are located in.

  6. In TI Manager HIP Objects folder under All Tasks, right-click and select Reload Metadata Files.

Installing HIS and Enterprise Single Sign-on (ESSO)

  1. In Windows Explorer, locate the installation folder in which you extracted the Setup files.

  2. Double-click Setup.exe. The Host Integration Server Installation panel appears.

  3. Click the product name to start installation.

    The Installation Wizard appears and guides you through the rest of the installation process.

  4. Click Finish when you are finished.

Upgrading from an Earlier Version of Enterprise Single Sign-on

Host Integration Server 2010 (HIS) includes an updated version of Enterprise Single Sign-On (ESSO). If you are installing this release on a computer with an earlier release of Host Integration Server, ESSO will be automatically updated during setup. You should perform the following steps prior to upgrading.

  1. Verify that a current version of the SSODB is backed up to a secure location.

  2. Verify the current master secret key is backed up to a secure location.

  3. Record the name of the SQL Server and the name of the database being used by ESSO. This information is displayed in the SSO Administration tool when the System folder is selected. Save this information in a secure location.

Once the HIS installation is complete, perform the following steps to restore the ESSO configuration.

  1. In the Configuration Tool, select Custom Configuration. In the left pane, select Enterprise SSO, and in the right pane, select Enable Enterprise Single Sign-On.

  2. Select Join an existing SSO system, and then enter the SQL Server name, database name and Windows service credentials.

  3. Select Apply Configuration, and then click Next to continue with the configuration.

  4. After the configuration is complete, restore the secret on the Master Secret Server using the SSO Administration tool or the command-line utility, ssoconfig –restoresecret backupfile.bak.

You must upgrade all the servers that share an ESSO database to the same release. This requirement also applies to a standalone Master Secret Server.

Upgrade using Enterprise Single Sign-On standalone setup

Follow these steps to perform an upgrade on computers that have a standalone Enterprise Single Sign on installation, such as dedicated Master Secret Servers.

  1. Verify that the current master secret key is backed up to a secure location.

  2. Verify that a current version of the SSODB is backed up to a secure location.

  3. Run the ESSO Setup.exe from the Host Integration Server 2010 media. The default installation folder is \Platform\SSO.

  4. In the Autorun dialog box, select Microsoft Enterprise Single Sign-On.

  5. In the Summary dialog box, select Upgrade.

Configuring HIS and ESSO

Host Integration Server contains an update to the Configuration Tool that is used during setup to complete the initial installation. On first use of the Configuration Tool, a Configuration – Start panel gives you the option of doing a Basic or Custom configuration.

Basic Configuration

To install Host Integration Server with the default settings, you can use the Basic configuration option. When you click Configure, the tool uses the default settings and the minimum information you supplied in the Configuration - Start panel.

Custom Configuration

If you select Custom configuration and then click Configure, you are presented with a list of configuration panels based on the features selected during installation. Selecting an item in the left pane displays its associated settings in the right pane. After you have entered your configuration settings, you can click Apply Configuration in the toolbar to implement those settings.

Note

Any settings made in the initial Configuration - Start panels are populated as defaults in the custom configuration.

Configuring ESSO as the Master Secret Server

Initial installation of Enterprise Single Sign-On must be completed on the server that you will use as the Master Secret Server. This is also the only Master Secret Server allowed in the entire ESSO system.

  1. After installation is complete, the Configuration Wizard starts.

  2. Select the Custom Configuration mode.

  3. Because this is the Master Secret Server, select the option Create a new ESSO System when configuring ESSO.

    The Master Secret Server and the ESSO Credential database are created.

Configuring ESSO as a Process Server

In a multi-computer environment, after the Master Secret Server and Credential database have been created, you can install Enterprise Single Sign-On on subsequent computers. These are typically the computers on which Host Integration Server is also installed. You complete the initial installation process with the same steps that you performed on the first computer. Configuration, however, varies from the original steps that you performed. Because the Master Secret Server and the ESSO Credential database are already in place, select Join an existing ESSO System when you configure ESSO.

Updating the Configuration

You can choose to update the configuration later by running the Configuration Tool on the Start menu. You can select individual settings to be changed on each panel. To update the service account or database settings for all panels, click the View menu and then select Service Accounts or Databases. In these dialog boxes you can multi-select all the rows by using the CTRL key, and you can bulk edit the settings.

Unconfigure

You can disable a feature by selecting it and then clicking Unconfigure Feature. Click OK, and then continue through the wizard. This process removes any settings (for example, services and registry keys) that were created when the feature was originally configured.

Unattended Configuration

You can use the Configuration Tool to export a configuration file that can be used to perform an unattended installation and configuration. Select Export Configuration on the File menu. The unattended installation consists of two steps: setup and configuration.

Unattended Installation of HIS

You can use the unattended installation to install Host Integration Server on a large number of computers which ensures that they are all configured in the same way. It is also useful if you want to change or update the existing configuration of a large number of computers.

You perform an unattended installation by creating a “model” installation on one computer, which you then apply to the other computers.

To perform unattended installations

  1. Using the standard Windows-based installation program, perform a full installation on a single computer. Because the installation parameters you choose will be saved as a model, make the selections that you want to use on the other installations.

  2. When setup is complete, run the Configuration Tool on the same computer. As in step 1, make the selections that you want to use on the other installations. Select Export Configuration on the File menu, and then save the configuration XML file.

  3. If you want to update the configuration XML file, select Import Configuration, open a saved file, and make your changes. This option is available only until you have completed configuration. If you need to make an update after configuration, you will have to configure the system again.

  4. On the appropriate server computer, open a command prompt window and run the Unattended Installation command (see the following sections). Where the command calls for the configuration file, use the name and location of the HISServerConfig.xml file that you created in step 1. You can also use the options listed in the "Options" section.

Commands

You can use the following commands and options for unattended installation.

Setup.exe /InstallPlatform /L c:\HISInstall.log /S c:\HISServerConfig.xml /INSTALLDIR C:\HIS

Configuration.exe /L c:\ConfigFramework.Log /S c:\HISServerConfig.xml

Options

The following table describes the command options.

Option

Description

/InstallPlatform

This flag causes the installation program to install any platform prerequisites.

/L c:\HISInstall.log

This flag determines the log file location that is created during setup.

/S C:\HISServerConfig.xml

This flag specifies the configuration file (list of features) that is used on installation. The file "HISServerConfig.xml" contains information about which features to install and how they should be configured. Sample copies of these files are located in the Support\Unattended_Installs directory of the installation folder. This file can also be created during setup by clicking Save in the summary panel of the Configuration Tool.

/INSTALLDIR

This option tells Setup where to install the product.

Top of page

Removing HIS

  1. Click Start, point to Settings, and then click Control Panel.

  2. In the Control Panel, open Add or Remove Programs, select the name of the product, and then click Change/Remove. The Add or Remove Application dialog box appears.

  3. Click Remove, and then click Next. The Uninstall Wizard appears and automatically starts the uninstall process.

  4. When the wizard has completed the process, click Finish.

Note

Uninstalling Host Integration Server does not uninstall Enterprise Single Sign-On (SSO). To uninstall SSO, see "Uninstalling Enterprise Single Sign-On" later in this document.

Unattended Removal of HIS

Use the following command for unattended uninstall:

Setup.exe /l C:\UninstallLog.txt /REMOVE ALL /Product HIS

Note that Setup.exe must have the installation location appended to the beginning to ensure that the correct Setup.exe program is started.

Removing ESSO

Removing Host Integration Server does not remove Enterprise Single Sign-On. To remove this feature, follow these steps.

  1. Click Start, point to Settings, and then click Control Panel.

  2. Double-click Add or Remove Programs.

  3. In the Add or Remove Programs dialog box, click Microsoft Enterprise Single Sign-On, and then click Remove.

  4. Click Yes when you are prompted to confirm removal of Microsoft Enterprise SSO.

Note

If you have BizTalk Server Runtime, Development, or Administration features installed, or Host Integration Server Administration features installed, you cannot remove the ESSO Runtime or Administration components until all dependencies are removed.

Unattended Removal of ESSO

You will need the original installation media to perform unattended uninstalls of Enterprise Single Sign-On Server or Client versions.

You can use the following commands for unattended uninstall:

ESSO - Server Features

MSIEXEC /X <Drive>\Platform\SSO\SSO.msi\SSO.MSI

ESSO - Client Features

MSIEXEC /X <Drive>\Platform\SSO\CLIENT\SSOClient.msi

Note

If you have BizTalk Server Runtime, Development, or Administration features installed, or Host Integration Server Administration features installed, you cannot uninstall the ESSO Runtime or Administration components until all dependencies are removed.

Top of page

Known Issues with Host Integration Server

The following files are not signed

The following table lists text files that contain information used by the Host Integration Server demo link service. This service allows customers to demo features of BizTalk Server 2010 Host Integration Server without the need of a live IBM Host. These files also have incomplete publisher, product name and version file information.

3270flsh.scr

Ft1k.scr

Mailjfish.scr

3270log.scr

Ft1k.scr

Mainloop.scr

5250log.scr

Ft1k.scr

Snaoledb.scr

5250loop.scr

Ft1kstrt.scr

Ft1k.scr

Db2oledb.scr

Mainflsh.scr

wgbmaps.scr

Demo5250.scr

Binaries with Missing Information

The following table lists Interop binaries that have missing product name, company and copyright information.

DTCWrapper.dll (Works in conjunction with the Microsoft.HostIntegration.TI.DTCWrapper.Interop.dll)

Microsoft.HostIntegration.TI.HIPAdminClasses.Interop.dll

Microsoft.HostIntegration.Help.dll

Microsoft.HostIntegration.TI.HIPHostEnvironment.Interop.dll

Common.ProductSKU.Interop.dll

Microsoft.HostIntegration.TI.LocalEnvironment.Interop.dll

Microsoft.HostIntegration.TI.DCGen.Interop.dll

Microsoft.HostIntegration.TI.mgddtcob390.Interop.dll

Microsoft.HostIntegration.TI.DTCWrapper.Interop.dll

Microsoft.HostIntegration.TI.mobase.Interop.dll

Microsoft.HostIntegration.TI.ESSOHelper.Interop.dll

Microsoft.HostIntegration.TI.TICorePkg.Interop.dll

Microsoft.HostIntegration.TI.Oldtadtlb.Interop.dll

Microsoft.HostIntegration.TI.TIHostSource.Interop.dll

Microsoft.HostIntegration.TI.Tracing.Interop.dll

Microsoft.HostIntegration.TI.TIHostSource.Interop.dll

Microsoft.HostIntegration.TI.ConvertPrimEx.Interop.dll

Microsoft.HostIntegration.TI.TIHostSource.Interop.dll

The following Policy binary has missing product name and company information (no product name or company).

policy.6.0.Microsoft.HostIntegration.TI.ClientContext.dll

The following sample SDK binary has missing product name and company information

PL_GetBal.dll (Created by Designer development tool to show example usage)

Registry Value persists after uninstalling Host Integration Server

If your SNA print sessions are configured to use a unique file extension when printing to a file, the resulting registry key used to track the filename will be left behind on uninstall. The registry key will match the name of the SNA Print session.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SNA Print Server\Sessions\SessionName]

Executable Binary Privileges Required

The following table lists applications that need Privilege of highest available, or require administrative privileges to launch.

Executable Binary Privilege Required

addschema.exe

Require Administrator

configuration.exe

Require Administrator

linkcfg.exe

Require Administrator

linkutil.exe

Require Administrator

Microsoft.HostIntegration.TI.ImportSelfHostedDotNet.exe

Require Administrator

Microsoft.HostIntegration.TI.ImportWipObjects.exe

Require Administrator

Microsoft.HostIntegration.TI.StartMMC.exe

Require Administrator

perfutl.exe

Require Administrator

Setup.exe

Require Administrator

SimHost.exe

Require Administrator

ddmserv.exe

Highest Available

display.exe

Highest Available

dlsstat.exe

Highest Available

linksnif.exe

Highest Available

Microsoft.HostIntegration.DataAccessTool.exe

Highest Available

mngagent.exe

Highest Available

mngcli.exe

Highest Available

qryipdlc.exe

Highest Available

RunAdmin.exe

Highest Available

snacfg.exe

Highest Available

snapopup.exe

Highest Available

snashmem.exe

Highest Available

snatrace.exe

Highest Available

snaver.exe

Highest Available

ssoclient.exe

Highest Available

SSOClientUI.exe

Highest Available

ssoconfig.exe

Highest Available

ssomanage.exe

Highest Available

SSOPS.exe

Highest Available

sysctblj.exe

Highest Available

sysctblk.exe

Highest Available

sysctbls.exe

Highest Available

System.ServiceModel.Channels.WebSphereMQ.Hosting.Service.exe

Highest Available

tpsetup.exe

Highest Available

tpstart.exe

Highest Available

Host Integration Server Custom Actions with Documentation

The following table lists custom actions available in Host Integration Server, with a description of each.

Custom Action Description

ActiveDirectoryUninstall

Uninstall HIS Active Directory objects using snaadsi.dll.

AddActiveDirectoryOU

Add Configured Active Directory Organizational units.

CA_RemovePatches

Remove all updates installed to the Product.

CleanupRegistryEntriesUninstall

Delete all the Registry Entities on uninstall.

CleanupServiceRegistryKeys

Delete all the Service Registry keys.

DB2ODBCUninstall

Uninstall ODBC Driver for DB2.

DB2ODBCUpgrade

Upgrade ODBC Driver for DB2 for WindowsNT.

DetectRedistributables

Detects whether various Redistributables are Installed (e.g. MSI, MQMQ etc).

AddVssWriter

Add Hisvsswriter.exe to Win2k and above.

EnableSNABaseService

Enable the SnaBase Service in the service control manager.

BroadcastSystemChanges

Broadcast global windows environment changes.

CA_DummyForHXDS_DLL.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help Custom Actions.

CA_ExportTempHxDs.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help Custom Actions.

GenerateInitialXID

Generate the value for the InitialXID registry key used for eval Timeout.

CA_RemoveRootKey

Delete root HIS registry key if exists.

GetCurrentInstallData

Set MSI Properties for upgrade from Registry Values.

CA_RemoveUsersKeys

Remove HIS Registry keys for All Users.

GetWindowsInformation

Get Domain Controller, Advanced Server, RAS information etc.

InitializeFeatureStates

Initialize Feature Install States (Installed\Absent).

CleanupDirectories

Remove Directories during uninstall or reinstall.

CleanupDirectoriesUninstall

Delete HIS Directories during uninstall.

CleanupRegistryEntries

Cleanup HIS Registry Entries.

RemoveAllLinkServices

Remove all installed Link services.

RemoveNetworkShares

Delete 3 Network Shares created by our installer.

CleanupStartMenuFolders

Cleanup the Start Menu Folders.

COMTIUninstall

Upgrade COM Transaction Integrator.

COMTIUpgrade

Uninstall COM Transaction Integrator.

CreateNetworkShares

Create the 3 network shares used by HIS.

RemoveNullSessions

Remove NullSessionPipes and Shares Reg Keys from LanmanServer.

RemoveUserRegistryValues

Remove user registry key values.

SetCurrentSNAServerProperties

Set Current SNA Server Properties (Server name, server role, TCP/IP etc).

DetectDotNetFramework

Detect the dot Net Framework version installed.

SetInstallDirectory

Set the Install Directory for unattended install.

SetNTDomainProperty

Set NT Domain Name Property.

SetServicesStartType

Set the start type for services in the service control manager.

SetUpgradePath

Set the Upgrade path from Registry Values.

FinalizeUpgrade

Finalize Upgrade, restore config files and Reg keys.

ShutDownProcesses

Shutdown all HIS processes during cleanup.

StartMQBridgeService

Start the MQBridge Service (Does nothing).

StopMQBridgeService

Stop the MQBridge Service (Does nothing).

VssWriterUninstall

Stop and Delete the HISVssWrtier Service.

InitializeInstallProperties

Initialize all MSI properties from INF file.

WriteUserRegistryValues

Write user registry key values.

ValidatePID

Validate the Product ID code.

InstallVSWizards

Updates .vsz and .vsdir with the installation directory.

MQBridgeUninstall

Uninstall MSMQ-MQ Series Bridge.

MQBridgeUpgrade

Upgrade MSMQ-MQ Series Bridge.

PrepareForUpgrade

Prepare for Upgrade, backup config files and Reg keys.

SetRootDirProperty

Set the Root Directory Property for HIS.

WriteSQMSettings

Enable SQM on the machine.

CA_RemoveTempHxDs.3643236F_FC70_11D3_A536_0090278A1BB8

MSHelp Custom Action.

CA_RegisterMicrosoftHelp.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help Custom Actions.

CA_UnRegisterMicrosoftHelp.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help Custom Actions.

CADwSensSchedule.F0DF3458_A845_11D3_8D0A_0050046416B9

Creates Watson logs when setup fails

LaunchConfigFramework_SlashR

Not Used.

LaunchConfigFramework_SlashU

Not Used.

AddCOMTIPerfmonCounters

Loads the Performance counter for COM Transaction Integrator.

AddDB2PerfmonCounters

Loads the Performance counter for MsDB2 Provider.

AddHIPPerfmonCounters

Loads the Performance counter for Host-Initiated Processing.

AddMQBridgePerfmonCounters

Loads the Performance counter for the MQ Bridge.

AddNodePerfmonCounters

Loads the Performance counter for SNA.

AddTN3270PerfmonCounters

Loads the Performance counter for TN3270.

AddTSSPerfmonCounters

Loads the Performance counter for Session Integrator.

CleanupBridgeCluster

Cleanup the Bridge Cluster.

DeleteHISNameSpace

Delete HIS from the WMI namespace.

InstallMgdWIPDefinitions

Install managed Window Initiated Processing Definitions.

InstallSCWExtension

Install Secure Configuration Wizard Extensions.

LaunchOptionalConfigurationWizard

Launch Optional Configuration Wizard.

MofcompWmiHIS

Compile the WMI provider for HIS.

MofcompWmiSna

Compile the WMI provider for SNA.

MofcompWmiSnaLinkServices

Compile the WMI provider for SNA Link Services.

MofcompWmiSnaStatus

Compile the WMI provider for SNA Status.

MofcompWmiSnaTrace

Compile the WMI provider for SNA trace.

RegisterBizTalkMQClient

Register the managed BizTalk adapter for WebSphere MQ on the machine.

RegisterBizTalkMsDb2

Register the managed BizTalk MsDb2 Adapter on the machine.

RegisterBizTalkMsHostFile

Register the managed BizTalk MSHostFile adapter on the machine.

RegisterBizTalkMsTI

Register the managed BizTalk adapter for Transaction Integrator on the machine

RegisterMsDb2Client

Configure the managed BizTalk MSDb2Client on the machine.

RegisterMsHostFileClient

Configure the managed BizTalk MSHostFileClient on the machine.

RemoveCOMTIPerfmonCounters

Unloads the Performance counters for COM Transaction Integrator.

RemoveDB2PerfmonCounters

Unloads the Performance counters for DB2 providers.

RemoveHIPPerfmonCounters

Unloads the Performance counters for Host-Initiated Processing.

RemoveHIPServices

Unloads the Performance counters for Host-Initiated Processing Services.

RemoveMQBridgePerfmonCounters

Unloads the Performance counters for MQ Bridge.

RemoveNodePerfmonCounters

Unloads the Performance counters for SNA.

RemoveTN3270PerfmonCounters

Unloads the Performance counters for TN3270.

RemoveTSSPerfmonCounters

Unloads the Performance counters for COM Transaction Integrator.

SetupVSMenus8

Setup VS 2005 Designer components.

SetupVSMenus9

Setup VS 2008 Designer Components.

SetupVSMenus10

Setup VS 2010 Designer Components.

SetupVSMenusExp

Test Setup for VS Designer Components.

LaunchConfigFramework.2019B40E_3DED_479F_BA3C_B800F1EDE254

Not Used.

TBExpired.DC06F67C_93BD_4f99_B665_7D60B6738E3B

Check if the Time Bomb has expired.

CA_ERROR.DC06F67C_93BD_4f99_B665_7D60B6738E3B

MS Help Custom Actions.

BrandSKU.DC06F67C_93BD_4f99_B665_7D60B6738E3B

Update the value of the Brand SKU.

LaunchConfigFramework_SlashR.2019B40E_3DED_479F_BA3C_B800F1EDE254

Run Configuration tool to uninstall all components.

LaunchConfigFramework_SlashU.2019B40E_3DED_479F_BA3C_B800F1EDE254

Run Configuration tool to uninstall selected components.

RemoveSKU.DC06F67C_93BD_4f99_B665_7D60B6738E3B

Delete the value of the Brand SKU.

RemoveDLC.D3583150_24D6_11D3_A6A2_00C04F68DB21

Unconfigure the DLC.

DevenvSetupUninstall8

Uninstall VS 2005 Designer components.

DevenvSetupUninstall9

Uninstall VS 2008 Designer Components.

RemoveSKURollback.DC06F67C_93BD_4f99_B665_7D60B6738E3B

Rollback the value of the Brand SKU.

CA_BeginHelpTransaction.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help System Custom Actions.

CA_RegisterFilter.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help System Custom Actions.

CA_RegisterHelpFile.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help System Custom Actions.

CA_RegisterNamespace.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help System Custom Actions.

CA_RegisterPlugIn.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help System Custom Actions.

CA_RemoveHelpFile.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help System Custom Actions.

CA_RemoveNamespace.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help System Custom Actions.

CA_CommitHelpTransactionNoRB.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help System Custom Actions.

CADwSens.F0DF3458_A845_11D3_8D0A_0050046416B9

Not Used.

CA_RollbackHelpTransaction.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help System Custom Actions.

CA_RollbackTempHxDs.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help System Custom Actions.

CA_CommitHelpTransaction.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help System Custom Actions.

CA_HxMerge_HIS_2006.B2376911_F73C_421F_8E23_AA1EB2F3BE63

MS Help System Custom Actions.

CA_HxMerge_VSIPCC_VSCC.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help System Custom Actions.

CA_HxMerge_VSIPCC_VSExpCC.3643236F_FC70_11D3_A536_0090278A1BB8

MS Help System Custom Actions.

Enterprise Single Sign-on Custom Actions with Documentation

The following table lists custom actions available in ESSO, with a description of each.

Custom Action Description

CA_CheckForDependentProducts

Check for dependent products for ESSO installation.

CA_ResolveWellKnownNames

Resolve localized names of well-known accounts.

CA_StopServices

Stop all ESSO Services.

CA_RestartServices_commit

Restarts the stopped services.

CA_RestartServices_rollback

Restarts the stopped services.

CA_RemoveENTSSOKey

Remove the ESSO registry key.

ReadComplusData.8E665C9D_5561_45FC_AAA0_3878B87F3B86

Reads custom COM+ tables, creates XML document, and saves it in the Complus_XML_Data property.

CleanupComplus.8E665C9D_5561_45FC_AAA0_3878B87F3B86

Remove all applications that don't contain any components.

RollbackComplus.8E665C9D_5561_45FC_AAA0_3878B87F3B86

Sets up XML fragment to the data used by the COM+ actions.

InstallComplus.8E665C9D_5561_45FC_AAA0_3878B87F3B86

Installs COM+ applications and components.

CA_RemovePatches

Enumerates through all the installed updates for ESSO and uninstalls them.

CA_ResolveWellKnownNames

Resolve localized names of well-known accounts.

CA_CheckForDependentProducts

Check for dependent products for ESSO installation.

Top of page

Copyright

Information in this document that includes URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2010 Microsoft Corporation. All rights reserved.

Microsoft, BizTalk, Visual Studio, Windows, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.

Top of page