Last updated: August, 2010
This document contains information about installing Microsoft® Host Integration Server 2010.
You must have the following minimum hardware on the computer on which you want to install Host Integration Server.
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.
You must also have the following additional software installed to install Host Integration Server.
Feature Installation Prerequisites
The following table lists the feature and software requirements for Host Integration Server Setup.
Feature Configuration Prerequisites
The following table lists the software required to configure Host Integration Server Configuration (post-Setup).
The following table lists supported host systems.
The following features have been removed from Host Integration Server 2010.
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.
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
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.
Follow these instructions to upgrade subsequent computers.
Installing HIS and Enterprise Single Sign-on (ESSO)
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.
Once the HIS installation is complete, perform the following steps to restore the ESSO configuration.
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.
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.
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.
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.
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.
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.
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.
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
You can use the following commands and options for unattended installation.
The following table describes the command options.
Unattended Removal of HIS
Use the following command for unattended uninstall:
Note that Setup.exe must have the installation location appended to the beginning to ensure that the correct Setup.exe program is started.
Removing Host Integration Server does not remove Enterprise Single Sign-On. To remove this feature, follow these steps.
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
ESSO - Client Features
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.
Binaries with Missing Information
The following table lists Interop binaries that have missing product name, company and copyright information.
The following Policy binary has missing product name and company information (no product name or company).
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.
Host Integration Server Custom Actions with Documentation
The following table lists custom actions available in Host Integration Server, with a description of each.
Enterprise Single Sign-on Custom Actions with Documentation
The following table lists custom actions available in ESSO, with a description of each.
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.