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 2004 are:

  • 450 megahertz (MHz) or higher Intel Pentium-compatible CPU
  • 512 megabytes (MB) of RAM
  • 6-gigabyte (GB) hard disk
  • CD-ROM or DVD-ROM drive
  • Super VGA monitor (800 x 600) or higher resolution monitor with 256 color
  • For TI Designer only: Display Super VGA (1024x768) or higher resolution with 256 colors
  • Microsoft Mouse or compatible pointing device

Software prerequisites

Typical Installation

In order to install Host Integration Server 2004 you must be running one of the following operating systems:

  • Windows 2000 Service Pack 4 or later, along with Update for Microsoft Windows 2000 KB821887 hotfix, which you can download from the following location:

    http://go.microsoft.com/fwlink/?LinkId=29480

  • Windows XP Professional with Service Pack 1 or later
  • Windows Server 2003

Custom Installation

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

Server Installation

FeatureRequirementLocation
Data Access Tool.NET Framework v. 1.1http://go.microsoft.com/fwlink/?LinkId=22828
Managed Provider for DB2.NET Framework v. 1.1http://go.microsoft.com/fwlink/?LinkId=22828
Transaction Integrator.NET Framework v. 1.1http://go.microsoft.com/fwlink/?LinkId=22828
TI Designer.NET Framework v. 1.1

Visual Studio .NET 2003

http://go.microsoft.com/fwlink/?LinkId=22828

http://go.microsoft.com/fwlink/?LinkId=22837

TI RuntimeASP.NET (only required when using TI WIP .NET components)http://go.microsoft.com/fwlink/?LinkId=30968
TI ManagerASP.NET (only required when using TI WIP .NET components)http://go.microsoft.com/fwlink/?LinkId=30968
MSMQ-MQSeries BridgeMSMQ with routing supporthttp://go.microsoft.com/fwlink/?LinkId=30969
Enterprise Single Sign-OnSQL Server 2000 with Service Pack 3ahttp://go.microsoft.com/fwlink/?LinkId=22838

http://go.microsoft.com/fwlink/?LinkId=22839

Client Installation

FeatureRequirement 
Data Access Tool.NET Framework v. 1.1http://go.microsoft.com/fwlink/?LinkId=22828
Managed Provider for DB2.NET Framework v. 1.1http://go.microsoft.com/fwlink/?LinkId=22828
TI Designer.NET Framework v. 1.1

Visual Studio .NET 2003

http://go.microsoft.com/fwlink/?LinkId=22828

http://go.microsoft.com/fwlink/?LinkId=22837

Configuration Wizard after Server setup

It is possible to install the Server software without running the Configuration Wizard, and then run the Configuration Wizard later. Eventually, however, you must run the Configuration Wizard. To do this, you will need the software listed in the table below. It can either be installed on the local Host Integration Server or a remote computer.

FeatureRequirement 
DB2 Distributed Transactions

SQL Server 2000 with Service Pack 3ahttp://go.microsoft.com/fwlink/?LinkId=22838

http://go.microsoft.com/fwlink/?LinkId=22839

Transaction IntegratorSQL Server 2000 with Service Pack 3ahttp://go.microsoft.com/fwlink/?LinkId=22838

http://go.microsoft.com/fwlink/?LinkId=22839

Special Considerations when installing Enterprise Single Sign-On

The following sections contain information regarding installation of the Enterprise Single Sign-On feature. Because of this feature’s complex relationships to other features and systems, and because of its importance to system security, it is recommended that you read these sections carefully before installing 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 2004 setup program and select Custom Installation. Under the Security Integration feature, select Enterprise Single Sign-On and continue installation.

After installation is complete, the Configuration Wizard launches. Since this is the Master Secret Server, when prompted with the question, Do you want to create a new SSO system or Join an existing SSO system? select Create. This will create the Master Secret Server and the SSO Credential Database.

Note  As soon as the configuration is complete, make sure you back up the Master Secret to a safe location. To do this, open a command prompt and navigate to the SSO directory located at Program Files\Common Files\Enterprise Single Sign-On, and run ssoconfig -backupsecret <backup file>.

It is recommended that you install only the Master Secret Server on this computer. It should not be used as a processing server.

Processing Servers for Enterprise Single Sign-On

In a multi-box 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 2004 is installed as well.

The initial installation process is the same as on the first computer. Configuration, however, becomes slightly different. Since the Master Secret Server and the SSO credential database are already in place, select Join when the Configuration Wizard asks, Do you want to create a new SSO system or Join an existing SSO system?

ENTSSO Administration install only

It is possible to install just the Enterprise Single Sign-On Administration feature. To do this, when you run the install program, select Custom Installation. Under the Security Integration feature, select only the Enterprise SSO Administration sub-feature.

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

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

Installing the SSO administrative utility (ssomanage.exe) does not create shortcuts on the Start menu to access the command line utilities. To run the SSO administrative 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 the 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 run ssomanage -serverall <SSO server name>.

SSO Client install

The stand-alone SSO client utility (ssoclient.exe) allows 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.

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

  • Windows Server 2003
  • Windows 2000 Server with Service Pack 4, or Windows XP Professional with Service Pack 1
  • .NET Framework 1.1 (only necessary for the managed interoperability component of the SSO client utility)

Installing the SSO client utility does not create shortcuts on the Start menu to access the command line utilities. To run the SSO client utility 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 install program and select Custom Installation. Under the Security Integration feature, select the Enterprise Single Sign-On Password Synchronization sub feature.

To addition to this, Password synchronization adapters are necessary to send and receive password changes to the external system. You can view a list of currently available adapters at the following location: http://go.microsoft.com/fwlink/?LinkId=30101

You can also contact support aliases to obtain information on these Password synchronization adapters.

There are 3 types of password synchronization sub-features supported in this release to simplify administration of the SSO credential database and to keep passwords across user directories in sync.

The first type is Windows to External (for example, Active Directory to RACF). A Windows user's password change is captured and sent to the Enterprise SSO Server assigned to receive password changes from domain controllers. This then forwards the password change to an external system and the mapping in the SSO credential database is kept in sync with the change made on the external system.

To capture password changes made in Active Directory, in addition to installing the ENTSSO Password Sync feature, components need to be installed on the domain controllers to capture password changes.

Both the Windows Password Capture component and Password Change Notification Service (PCNS) must be installed on all domain controllers from which you will be capturing passwords. You can find these components in the following location:

<HIS CD ROOT>\Platform\PCNS

Read the accompanying documentation (also located in the folder above) before you proceed with the installation on the domain controller.

The second type is External to Windows - Full synchronization. A password is captured on the External system and sent to the Enterprise Single Sign-On server assigned for Password Synchronization which then updates the password in the SSO credential database, and also updates the Windows user's password in Active Directory.

The third type is External to Windows - Partial synchronization. A password is captured on the External system and sent to the Enterprise Single Sign-On server assigned for Password Synchronization which then updates the password in the SSO credential database.

Upgrading from a previous version of SSO

If you are installing the Enterprise Single Sign-on feature and you already have a previous version deployed on your computer (for example, from Host Integration Server 2004 Beta, or Microsoft BizTalk® Server 2004), you must complete the steps below.

  • Back up the SSODB to a secure location
  • Back up the Master Secret Key on the Master Secret Server
  • Update the Master Secret Server by running Host Integration Server 2004 setup, choosing Custom Installation, and then selecting Enterprise Single Sign-On. Select Reuse when the Configuration Wizard prompts you with the question: Do you want to reuse the existing configuration?

It is not necessary to update the other SSO Servers (non-Master Secret Servers) from your BizTalk Server 2004 installation. However, if you want the new Enterprise Single Sign-On features to be available on those servers, you must update them by using the same procedures outlined above.

If you have a Beta version of Enterprise SSO installed as part of a Host Integration Server 2004 Beta release, you can use the same mechanism to upgrade those servers.

Note  These considerations also apply if you are installing Microsoft BizTalk Server 2004 on a computer with an existing installation of Host Integration Server 2004 Enterprise Single Sign-On, and wish to update the servers.

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.

Compatibility with earlier Host Integration Server products

SNA Server 2.0-SNA Server 3.0

Host Integration Server 2004 supports neither upgrade nor interoperability with SNA Server versions 2.0 – 3.0 inclusive.

SNA Server 4.0 and Host Integration Server 2000

Interoperability

Host Integration Server 2004 supports limited interoperability with SNA Server 4.0 and Host Integration Server 2000.

Host Integration Server 2004 clients will connect through SNA Server 4.0 servers and Host Integration Server 2000 servers.

SNA Server 4.0 clients will connect through Host Integration Server 2004 servers and Host Integration Server 2000 servers.

Neither SNA Server 4.0 servers nor Host Integration Server 2000 servers can act in the role of member or backup to a primary Host Integration Server 2004 server. Instead, you must upgrade the servers to Host Integration Server 2004 while running against the older SNA Server 4.0 or Host Integration Server 2000 primary server. Once all backup computers are upgraded to Host Integration Server 2004 , the remaining primary server computer can be upgraded to Host Integration Server 2004.

To deploy Host Integration Server 2004 as a backup in an existing Host Integration Server 2000 or SNA Server 4.0 domain, it is necessary to make the following configuration changes:

  • Create a COMLOGS share pointing to <installdir>\system. Grant the service account and HIS Administrators group Read access. This share is used by the SNA Manager when creating link services on remote computers.
  • Add any users who need to perform administrative tasks to the local Host Integration Server Administrators group on the Host Integration Server 2004 computer.
  • Add any users who will create link services to the Local Administrators group on the computer where the link services will be created.
  • Use the same service account for the Host Integration Server 2004 server that was used for the Host Integration Server 2000 or SNA Server 4.0 servers. This ensures that all components have the appropriate rights to perform their necessary functions.

Note  New features on Host Integration Server 2004 will not be available until all servers in the subdomain have been upgraded.

Upgrade

This release supports the upgrade of Host Integration Server 2000 Service Pack 1 and SNA Server 4.0 Service Pack 4.

Note that when you upgrade from SNA Server 4.0 to Host Integration Server 2004, it is necessary to reboot your computer. After the reboot has completed, you must then finish the installation by running the Configuration Wizard. The tables below outline possibilities in upgrading from previous versions.

Server Upgrades

This versionCan be upgraded to this version
SNA Server 4.0 SP4HIS 2004 Enterprise Edition

HIS 2004 Standard Edition

HIS 2004 Evaluation Version

HIS 2004 Developer Edition

HIS 2000 SP1HIS 2004 Enterprise Edition

HIS 2004 Standard Edition

HIS 2004 Evaluation Version

HIS 2004 Developer Edition

HIS 2004 Standard EditionHIS 2004 Enterprise Edition
HIS 2004 Evaluation VersionHIS 2004 Standard Edition

HIS 2004 Enterprise Edition

Client Upgrades

This versionCan be upgraded to this version
SNA Server 4.0 SP4 (Windows 9x)HIS 2004 Client
SNA Server 4.0 SP4 (Windows NT)HIS 2004 Client
HIS 2000 SP1 (End User)HIS 2004 Client
HIS 2000 SP1 (Admin)HIS 2004 Client

Client to Server Upgrades

This versionCan be upgraded to this version
SNA Server 4.0 SP4 (Windows NT)HIS 2004 Enterprise Edition

HIS 2004 Standard Edition

HIS 2004 Evaluation Version

HIS 2004 Developer Edition

HIS 2000 SP1 (Admin)HIS 2004 Enterprise Edition

HIS 2004 Standard Edition

HIS 2004 Evaluation Version

HIS 2004 Developer Edition

Build-to-Build Upgrades

For build-to-build upgrades, use the same backup and restore procedures as you would in preparing for Backup and Disaster Recovery. These procedures are listed below.

Back up your SNA Server configuration

  1. Right click the SNA domain name in the SNA Manager and choose Backup configuration….
  2. Record the settings for the installed link services.

Back up your configuration using the Configuration Wizard

  1. Re-run the Configuration Wizard from Start menu.
  2. Proceed through the wizard screens to the Summary screen.
  3. Choose Save…. to save your configuration.

Back up your Transaction Integrator configuration

  1. Back up the HIP configuration by backing up the HIP database.
  2. Backup the Remote Environments by saving a copy of the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cedar

  3. Export COM+ applications (Right-click application/Export…/Server Application).
  4. Save Web Site or virtual directories individually to an XML file (Right-click Web Site or VD/All tasks/Save configuration to a file).
  5. Back up the web site/virtual directory files/structure.

Back up your Data Integration Configuration

  1. Backup any UDLs, HCDs or File DSNs. User and System DSNs can be converted to UDLs with the Data Access Tool and backed up.

Upgrade and restore your configuration

  1. Launch the unattended setup using the XML file created in Step 3 of Back up your configuration using the Configuration Wizard.

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

  2. Restore the HIP database which you saved in Step 1 of Back up your Transaction Integrator configuration.
  3. Launch the unattended configuration using the XML file created in Step 3 of Back up your configuration using the Configuration Wizard. This file will need to be updated with the service account password.

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

  4. Launch SNA Manager.
  5. Re-create your link services using the information recorded in Step 2 of Back up your SNA Server configuration.
  6. Right click the SNA domain name in the SNA Manager and choose Restore configuration….
  7. Start TI Manager. This will automatically recreate the HIP application from the database.
  8. Restore TI and Data artifacts as appropriate.

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 OS/400 V2R3 or later
  • IBM AS/400 Advanced 36 System Support Program Release 7.5

IP-DLC Link Service

  • IBM Communications Server for OS/390 V6 or later
  • IBM OS/390 2R6 (with APAR OW36113) or later

Security Integration

  • Computer Associates eTrust CA-ACF2 Security for z/OS and OS/390
  • Computer Associates eTrust CA-Top Secret Security for z/OS and OS/390
  • IBM RACF Security for z/OS and OS/390
  • IBM AS/400 Security

OLE DB Provider for DB2, ODBC Driver for DB2, and Managed Provider for DB2

  • IBM DB2 V6 and later for OS/390 and z/OS to support an SNA LU6.2 or TCP/IP network connection
  • IBM OS/400 V5R1 and later to support an SNA LU6.2 or TCP/IP network connection
  • IBM DB2 for Universal Database V7.1 and later for Windows and AIX operating systems to support a TCP/IP network connection

The following table provides a feature-by-feature view of the DB2 platforms and versions supported by Host Integration Server 2004.

Key Features for DB2DB2MVSDB2400DB2AIXDB2NT
Network Connections over SNAV6V5R1n/an/a
Network Connections over IPV6V5R1V7.1V7.1
Distributed Transactions over SNAV6V5R1n/an/a
Distributed Transactions over IPV6V5R1V8.1V8.1
Default SchemaV6V5R1V7.1V7.1
Session PoolingV6V5R1V7.1V7.1
Single Sign-On (SNA and IP)V6V5R1V7.1V7.1
Client Application NameV6V5R1V7.1V7.1
Stored Procedure Multiple ResultsV6V5R1V7.1V7.1
Default Qualifier (CURRENT SCHEMA)V6V5R2V7.1V7.1
UNICODE DataV7V5R1V7.1V7.1
SQL Long IdentifiersV8V5R1V7.1V7.1

OLE DB Provider for AS/400 and VSAM

  • IBM Distributed File Manager (DFM) V1R2 and later to support an SNA LU6.2 network connection (DFM is a component of IBM Data Facility Storage Management Subsystem (DFSMS) for OS/390 and z/OS)
  • IBM V5R1 and later to support an SNA LU6.2 or TCP/IP network connection
  • IBM AS/400 Advanced 36 SSP (System Support Program) Release 7.5 to support an SNA LU6.2 network connection

Host File Transfer

  • IBM Distributed File Manager (DFM) V1R2 and later to support an SNA LU6.2 network connection (DFM is a component of IBM Data Facility Storage Management Subsystem (DFSMS) for OS/390 and z/OS)
  • IBM OS/400 V5R1 and later to support an SNA LU6.2 or TCP/IP network connection

AS/400 Data Queues

  • IBM OS/400 V5R1 and later to support an SNA LU6.2 network connection

Transaction Integrator

  • IBM CICS (Customer Information Control System) for MVS V3R3 or later to support an SNA LU6.2 network connection
  • IBM CICS Transaction Server for VSE/ESA V2R1 or later to support an SNA LU6.2 network connection
  • IBM CICS Transaction Server for OS/390 Version 1 or later to support an SNA LU6.2 or TCP/IP network connection
  • IBM CICS Transaction Server for z/OS Version 2 or later to support an SNA LU6.2 or TCP/IP network connection
  • IBM CICS Transaction Server for z/OS Version 2 Release 2 or later to support an Enhanced Listener for TCP/IP network connection
  • IBM IMS (Information Management System) Version 4 to support an SNA LU6.2 network connection
  • IBM IMS Version 5 to support an SNA LU6.2 network connection
  • IBM IMS Version 6 or later to support reliable 2PC transactions across an SNA LU6.2 network connection
  • IBM IMS Version 6 to support an SNA LU6.2 or TCP/IP network connection
  • IBM IMS Version 7 to support an SNA LU6.2 or TCP/IP network connection
  • IBM IMS Version 8 to support an SNA LU6.2 or TCP/IP network connection
  • IBM OS/400 Version 4 Release 1 or later to support a TCP/IP network connection.

To download updated Host Integration Server 2004 Help from www.microsoft.com, go to http://go.microsoft.com/fwlink/?linkid=29507.

Copyright © 2004 Microsoft Corporation.
All rights reserved.
Show: