Export (0) Print
Expand All

Installation Guide

This document contains information about installing Host Integration Server 2010. It contains the following sections:

For information about known issues, see Known Issues with Host Integration Server.

Hardware Requirements

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

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

  • Microsoft .NET Framework version 3.5 SP1

  • Microsoft XML Core Services (MSXML) 6.0 SP1

Gg163914.note(en-us,BTS.70).gifNote
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

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

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.

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 Transaction Integrator Conversion Tool.

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 Migration Considerations for Earlier Versions of Windows-Initiated Processing (WIP).

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 Transaction Integrator Conversion Tool.

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.

Gg163914.note(en-us,BTS.70).gifNote
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.

  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.

Gg163914.note(en-us,BTS.70).gifNote
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.

Gg163914.note(en-us,BTS.70).gifNote
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

Gg163914.note(en-us,BTS.70).gifNote
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.

Show:
© 2014 Microsoft