This document contains information about the basic installation process for Microsoft® Host Integration Server 2009.

You can download the latest version of this topic at http://go.microsoft.com/fwlink/?LinkID=141188.

It is important to read the entire document before you start the installation because it contains hardware and software requirements, correct installation procedures, and other information necessary for successful installation.

Note
It is also important to read the Readme.htm file before you start installation. The Readme.htm file is located in your download folder, and contains late-breaking information and known issues that you should understand before installation.

This document contains:

Hardware and Software Requirements

In the following sections, the version numbers listed are minimum requirements. Versions later than those listed here are supported unless otherwise noted.

Hardware Prerequisites

The minimum hardware requirements for a complete installation of Host Integration Server 2009 are as follows:

  • 450 megahertz (MHz) or higher Intel Pentium-compatible CPU

  • 512 megabytes (MB) of RAM

  • 6-gigabyte (GB) hard disk

  • CD drive or DVD drive

  • Super VGA monitor (800 x 600) or higher-resolution monitor with 256 color

  • For HIS Designer only: Display Super VGA (1024x768) or higher-resolution monitor with 256 colors

  • Microsoft Mouse or compatible pointing device

Software Prerequisites

Important
Microsoft Host Integration Server 2009 will not install on a computer that already has the Microsoft OLE DB Provider for DB2 installed. If you have the OLE DB provider installed on your computer, you must uninstall it before you install Host Integration Server 2009.

Supported Operating Systems

To install Host Integration Server 2009, you must be running one of the following operating systems:

  • Microsoft Windows® XP Professional with Service Pack 2 (x86 or x64)

  • Microsoft Windows Server® 2003 Service Pack 2 (x86 or x64)

  • Windows Server 2003 R2 Service Pack 2 (x86 or x64)

  • Microsoft Windows Vista® Service Pack 1 (x86 & x64)

  • Windows Server 2008 (x86 & x64)

Product Prerequisites

Host Integration Server 2009 requires the following prerequisites:

  • .NET Framework version 3.5 SP1

  • Microsoft XML Core Services (MSXML) 6.0 SP1

Note
Setup will 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 at: http://go.microsoft.com/fwlink/?LinkID=133541.

Feature Prerequisites

If you choose to install only selected features of Host Integration Server 2009, the following tables outline which software prerequisites you will need.

Server Installation

Feature Requirement

Developer Design Tools

Microsoft Visual Studio® 2005 SP1 or Visual Studio 2008

MSMQ-MQSeries Bridge

Message Queuing with routing support

Configuration After Server Setup

You can install the Server software without running the Configuration Tool, and then run the Configuration Tool later (on the Start menu). Eventually, however, you must run the Configuration Tool. To do this, you will need the software listed in the following table. It can be installed either on the local Host Integration Server computer or on a remote computer.

Feature Requirement

DB2 Distributed Transactions

Microsoft SQL Server® 2005 SP2 or SQL Server 2008

Transaction Integrator

SQL Server 2005 SP2 or SQL Server 2008

Enterprise Single Sign-On

SQL Server 2005 SP2 or SQL Server 2008

MQ Connectors

The following are the supported versions of WebSphere MQ:

Software Requirements

You must have the following software installed before you can install the adapter.

  • MSMQ-MQSeries Bridge

    • IBM WebSphere MQ Client 6.0 with Fix Pack 6.0.1.1 or higher

    • IBM WebSphere MQ Client 7.0 with Fix Pack 7.0.0.1

    • IBM WebSphere MQ Extended Transactional Client (for transactional support)

  • WCF Channel for WebSphere MQ

    • IBM WebSphere MQ Client 6.0 with Fix Pack 6.0.1.1 or higher

    • IBM WebSphere MQ Client 7.0 with Fix Pack 7.0.0.1 (required for 64-bit)

    • IBM WebSphere MQ Extended Transactional Client (for transactional support)

Refer to your IBM documentation for additional information about how to obtain and install WebSphere MQ Extended Transactional Client or WebSphere MQ Client.

Installing the Product

The following sections contain installation information for Host Integration Server 2009.

Important Notes About Installation

If you are upgrading a Host Integration Server 2004 or Host Integration Server 2006 computer, Host Integration Server 2009 Setup will upgrade your configuration automatically.

New to the Product Installation

The product installation now includes both Server and Client components, and also a developer-only and documentation-only installation.

To Install Host Integration Server 2009
  1. In Windows Explorer, locate the installation folder in which you extracted the Setup files.

  2. Double-click Setup.exe. The Host Integration Server 2009 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.

To Uninstall Host Integration Server 2009 Using Add or Remove Programs
  1. Click Start, point to Settings, and then click Control Panel.

  2. In 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 2009 does not uninstall Enterprise Single Sign-On (SSO). To uninstall SSO, see "Uninstalling Enterprise Single Sign-On" later in this document.

Configuring Host Integration Server 2009

Host Integration Server 2009 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 the user the option of doing a Basic or Custom configuration.

Basic Configuration

To install by using the default setting, you can use the Basic configuration option. When you click Configure, the tool proceeds using the default settings, together with the minimum information supplied by the user on the Configuration - Start panel.

Custom Configuration

If you choose 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 that any settings made in the initial Configuration - Start panels are populated as defaults in the custom configuration.

Updating the Configuration

You can update the configuration later by running the Configuration Tool on the Start menu. Individual settings can 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 bulk edit the settings.

Unconfigure

A feature can be disabled by unconfiguring that feature. Select Unconfigure Feature on the menu, select the feature to be unconfigured, click OK, and then continue through the wizard. This process removes any settings (for example, services and registry keys) that were created when the configuration was previously applied.

Unattended Configuration

The Configuration Tool can 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

Unattended installation is useful for installing Host Integration Server 2009 on a large number of computers to ensure that they are all configured in exactly the same way. It is also useful if you need 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 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 you want to use on the other installations. Select Export Configuration on the File menu, and save the configuration XML file.

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

  4. On the appropriate server computer, open a command prompt 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 created in step 1. You can also use the options listed in the "Options" section.

Commands

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

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

Unattended Uninstall

Use the following command for unattended uninstall:

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

Note that Setup.exe will need to have the install location appended to the beginning to ensure that the correct Setup.exe program is launched.

Uninstalling Enterprise Single Sign-On

Uninstall

Uninstalling Host Integration Server does not uninstall Enterprise Single Sign-On. To uninstall 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 uninstall the SSO Runtime or Administration components until all dependencies are removed.

Unattended Uninstall

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

Use the following commands for unattended uninstall:

Host Integration Server 2009 Server

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

Host Integration Server 2009 Client

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 SSO Runtime or Administration components until all dependencies are removed.

Special Considerations When Installing Enterprise Single Sign-On

The following sections contain information about installation of the Enterprise Single Sign-On (SSO) feature. Because of this feature’s complex relationships to other features and systems, and because of its importance to system security, we recommend that you read these sections carefully before you install Enterprise Single Sign-On.

Installing SSO and Creating the Master Secret Server

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

To install Enterprise Single Sign-On, run the Host Integration Server 2009 or BizTalk Adapters for Host Systems Setup program and under the Server node, select Enterprise Single Sign-On and continue installation.

After installation is complete, the Configuration Wizard starts. Select the Custom Configuration mode. Because this is the Master Secret Server, select the option to “Create a new SSO System” when configuring Enterprise SSO. This creates the Master Secret Server and the SSO Credential database.

Processing Servers for Enterprise Single Sign-On

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 2009 is also installed.

The initial installation process is the same as on the first computer. Configuration, however, becomes slightly different. Because the Master Secret Server and the SSO Credential database are already in place, select “Join an existing SSO System” when configuring Enterprise SSO.

EntSSO Administration Installation Only

You can install just the Enterprise Single Sign-On Administration feature. To do this, when you run the installation program, under the Client node, select only Enterprise Single Sign-On Administration and continue installation.

Only SSO administrative components will be installed. The hardware and software requirements are the same as for a typical EntSSO installation.

Note
While the SSO Administration feature in Host Integration Server 2009 is compatible with the server version of SSO in BizTalk Server 2009, the administrative components of Enterprise SSO in BizTalk Server 2009 are not compatible with the server version of Enterprise SSO in Host Integration Server 2009.

Enterprise SSO MMC snap-ins require MMC 3.0. It is not supported on Windows 2000.

Installing the SSO Administration feature installs command-line-based utilities (ssomanage.exe and ssoconfig.exe) and an MMC snap-in that can be accessed by clicking Start, pointing to All Programs, and then clicking Microsoft Enterprise Single Sign-on. To run the SSO administrative command-line utilities after installation, you must open a command prompt and navigate to the SSO directory located at Program Files\Common Files\Enterprise Single Sign-On. You can use ssomanage.exe to specify the SSO server you want to use for management. To do this, open a command prompt and navigate to the SSO directory located at Program Files\Common Files\Enterprise Single Sign-On, and then run ssomanage -serverall <SSO server name>.

SSO Client Installation

The SSO client utility (ssoclient.exe or SSOClientUI.exe) enables end users to configure their client mappings in the Credential database. You can install the client utility from a self-extracting file (SSOClientInstall.exe), which is installed with the SSO Administration feature. This also installs the UI-based SSO client utility that can be accessed by clicking Start, pointing to All Programs, and then clicking Microsoft Enterprise Single Sign-on.

To install the SSO client utility, you must be running one of the following operating systems on the client computer:

  • Windows Server 2003 (x86 or x64), Windows Server 2003 R2 (x86 or x64)

  • Windows XP Professional with Service Pack 1

  • Windows Vista

Note
The UI-based SSO client utility (SSOClientUI.exe) requires .NET Framework 2.0.

To run the command-line-based SSO client utility (ssoclient.exe) after installation, you must open a command prompt and navigate to the SSO directory located at Program Files\Common Files\Enterprise Single Sign-On.

Password Synchronization

To install the password synchronization feature, run the installation program under Server – Enterprise Single Sign-On; select the Enterprise Single Sign-On Password Management sub-feature and continue with installation.

Password Change Notification Service (PCNS) can be obtained from the following location: http://go.microsoft.com/fwlink/?LinkID=68145.

Upgrading from an Earlier Version of SSO

Host Integration Server 2009 and the Microsoft BizTalk Adapters for Host Systems include Microsoft Enterprise Single Sign-On version 4.0. Previous Microsoft products include the following versions of Enterprise Single Sign-On:

  • Enterprise SSO v1 is included in Microsoft BizTalk Server 2004

  • Enterprise SSO v2 is included in Microsoft Host Integration Server 2004

  • Enterprise SSO v3 is included in Microsoft BizTalk Server 2009 and Microsoft Connected Services Framework Server 3.0

Upgrade Procedure

If Enterprise SSO was installed with Host Integration Server 2004, installing the BizTalk Adapters for Host Systems or Host Integration Server 2009 will automatically upgrade SSO. (Note that you must first perform the upgrade on the Master Secret Server.)

If Enterprise SSO was installed with one of the preceding products other than Host Integration Server, follow the procedure below to upgrade to this release of SSO.

To perform these operations, you must be an SSO Administrator and a computer Administrator.

  1. Make a secure backup of the SSO Credential database from your SQL Server computer before performing an upgrade.

  2. Make sure you have a secure backup of the current secret from the Master Secret Server.

  3. Upgrade Enterprise SSO on the Master Secret Server. To do this, follow these steps:

    • Run setup.exe for Microsoft BizTalk Adapters for Host Systems or Microsoft Host Integration Server 2009 package.

    • In the custom setup tree, select Enterprise Single Sign-On, and clear all other options to only install Enterprise SSO. This will uninstall the earlier version and install the new version.

    • After installation is completed, start the Configuration Wizard to configure Enterprise SSO.

    • In the Configuration Wizard, select Custom Configuration. In the left pane, select Enterprise SSO, and in the right pane, select Enable Enterprise Single Sign-On. All the settings will be unavailable. Select Apply Configuration, and then click Next to continue with the configuration. This will also upgrade the SSO database if it is required.

    • After configuration is completed, restore the secret from the backup on the Master Secret Server.

  4. Upgrade Enterprise SSO on other SSO servers. To do this, follow these steps:

    • Run setup.exe for Microsoft BizTalk Adapters for Host Systems or Microsoft Host Integration Server 2009 package.

    • In the custom setup tree, select Enterprise Single Sign-On, and clear all other options to only install Enterprise SSO. This will uninstall the earlier version and install the new version.

    • After installation is completed, start the Configuration Wizard to configure Enterprise SSO.

    • In the Configuration Wizard, select Custom Configuration. In the left pane, select Enterprise SSO, and in the right pane, select Enable Enterprise Single Sign-On. All the settings will be unavailable. Select Apply Configuration, and then click Next to continue with the configuration.

Note
Services dependent on ENTSSO may be stopped after the upgrade. Check your System and Application event log for errors and warnings. You might have to restart any services that are dependent on the ENTSSO service on the computer where the upgrade was performed.

Using Host-Initiated SSO Functionality in Enterprise Single Sign-On

Host-Initiated Single Sign-On uses the protocol transition feature of Windows Server 2003 to perform Single Sign-On for the non-Windows user. This feature requires Windows Server 2003 and must be in a domain that has its Domain Functional Level set to Windows Server 2003.

Supported Host Platforms

SNA connectivity, 3270 terminal emulation, host print service, and SNA programming interfaces
  • IBM z/OS, OS/390, MVS, VSE and VM

SNA connectivity, 5250 terminal emulation, host print service, and SNA programming interfaces
  • IBM i5/OS V5R4 & V6R1 and later

IP-DLC Link Service
  • IBM z/OS 1.8 and later

OLE DB Provider for DB2, ODBC Driver for DB2, Managed Provider for DB2, and BizTalk Adapter for DB2
  • IBM DB2 V8 and V9 for z/OS to support an SNA LU6.2 or TCP/IP network connection

  • IBM i5/OS V5R4 & V6R1 to support an SNA LU6.2 or TCP/IP network connection

  • IBM DB2 for Universal Database V8.2 and later for Windows and AIX operating systems to support a TCP/IP network connection

OLE DB Provider for AS/400 and VSAM, Host File Transfer ActiveX Control, Managed Provider for Host Files, and BizTalk Adapter for Host Files
  • IBM Distributed File Manager (DFM) V1R4, V1R5, V1R6, and V1R7 to support an SNA LU6.2 network connection (DFM is a component of IBM Data Facility Storage Management Subsystem (DFSMS) for z/OS)

  • IBM i5/OS V5R4 & V6R1 to support an SNA LU6.2 or TCP/IP network connection

AS/400 Data Queues ActiveX Control
  • IBM i5/OS V5R4 & V6R1 to support an SNA LU6.2 network connection

Transaction Integrator and BizTalk Adapter for Host Applications
  • IBM CICS Transaction Server for VSE/ESA V2R3 to support an SNA LU6.2 network connection

  • IBM CICS Transaction Server for z/OS V2.3, V3.1, and V3.2 to support an SNA LU6.2 or TCP/IP network connection

  • IBM IMS Version 9.1 & 10.1, with IMS Connect 2.2,to support an SNA LU6.2 or TCP/IP network connection

  • IBM i5/OS V5R4 & V6R1 to support a TCP/IP network connection

WCF Channel for WebSphere MQ, MSMQ-MQSeries Bridge, and BizTalk Adapter for WebSphere MQ
  • IBM WebSphere MQ for Windows V5.3 with Fix Pack 12

  • IBM WebSphere MQ for Windows V6.0 with Fix Pack 6.0.1.1

  • IBM WebSphere MQ for Windows v7.0 with Fix Pack 7.0.0.1

Copyright

Information in this document, including 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.

© 2009 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.