Upgrading from Host Integrator 6.5 to 6.6

If you are upgrading to Verastream Host Integrator 6.6 from 6.5, please read this section fully to understand how to upgrade your settings and files to version 6.5.

Before you begin

Host Integrator 6.6 Setup detects the presence of 6.5 AADS, Administrative WebStations, and Host Integrator servers, and backs up and upgrades their configuration for 6.6. Always review your configuration after upgrading to verify that the migration was successful.

You must install 6.6 in the same directory as version 6.5 to have the upgrade work as described below.

Additional resources

If you are upgrading to version 6.6 from an earlier version, check the support site for further information. See What's New in Version 6.6 for a list of new features. See Linux/UNIX upgrade notes if you have Host Integrator servers for these platforms.

Upgrade Sequence

Upgrade your components in this order:

  1. Authentication, Administration, and Directory Services (AADS)

    You must upgrade your AADSs to version 6.6 before you install Host Integrator 6.6 Administrative WebStations or servers. The Host Integrator 6.6 Setup program can detect the presence of a 6.5 AADS and back up and upgrade its configuration to AADS 6.5.

  2. Administrative WebStation

    Upgrade your Administrative WebStations after you upgrade AADS. Because the Administrative WebStation is not compatible with an AADS of a different version, you should keep at least one 6.5 version of the Administrative WebStation if you plan to keep a 6.5 AADS.

  3. Host Integrator Session Servers

    Upgrade your Host Integrator Session Servers to version 6.6 after you upgrade your AADSs and Administrative WebStations.

  4. Host application models

    Your deployed models from previous versions will continue to function on a new session server. No manual upgrade is required.

    To upgrade a model, open and save a 6.5 model in the Design Tool. Once you convert a model file to version 6.6, it can no longer be loaded on a 6.5 server. Save the model only after you have verified that it behaves as you expect. For example, in certain cases it may be necessary to delete a pattern and re-add it. You should also verify that other aspects of the model, such as operations, recordsets, and procedures, behave correctly before you save the model.

    Changes in Host Integrator that could affect your model upgrade are disabled in a series of compatibility settings.

  5. Client applications

    It is recommended that you install the new AppConn connector files on machines running client applications. You may be able to continue to use the old connector; however, if you see an "Undefined error message," this indicates that a connector upgrade is required. The error message may also include an error number that can provide further information. Open the error messages topic and look for the listed error number.

    If you install the 6.6 AppConn connector on machines running client applications, allow the Setup program to complete the installation and create registry entries (if necessary). In general, your current client applications will work seamlessly with 6.6 models and servers because the support libraries you link to will be updated by Setup. Be aware that the 6.6 API may contain new methods, so upgrading your client code is to your advantage.

Notes:

Upgrading AADS, Administrative WebStations, and Host Integrator Servers

Under Windows, the Setup program will detect the presence of AADS, Host Integrator Session Servers, and Administrative WebStations and offer to backup the configuration information. To upgrade Host Integrator AADS and Servers from version 6.5 to 6.6 under Windows, follow the steps below.

For UNIX instructions, review the installation instructions and search for "Migrating from VHI" on the Tech Support site for articles that explain how to back up and convert your AADS, server, and Administrative WebStation configuration files so they are compatible with the new version of VHI.

Notes:

To upgrade AADS and Host Integrator Session Servers on a Windows system:

  1. Log in to Windows with Administrative privileges and close all running applications.

  2. Insert the Host Integrator product CD into your CD-ROM drive or locate your e-delivery folder.

    If you are uninstalling from another machine on the network and using the CD, you must map a drive to the Host Integrator product CD.

  3. To start the Setup program, click Run on the Start menu, type or browse to the path to the installation program (for example, D:\Setup.exe), and then click OK.

    The Setup program evaluates your system for the presence of any earlier components and lists these in the Legacy Component Migration dialog box. Click Next.

  4. Select the components whose settings files will be backed up and migrated to version 6.6 and then click Next.

  5. Select a backup directory where the settings files to be migrated will be saved and then click Next.

  6. Save the settings files for the components you selected and then click Exit.

  7. Use Add/Remove Programs from the Control Panel to uninstall previous versions of Verastream Host Integrator.

  8. Install Verastream Host Integrator version 6.6.

    For each group of previous settings that you selected to upgrade, the Host Integrator 6.6 Setup program will detect the presence of the backed up files and ask if you want to restore the settings for your 6.6 installation. Follow the prompts.

    Any model you open and save in the Design Tool will automatically upgrade to 6.6. Deployed models from earlier versions will also continue to function after the Host Integrator server is upgraded to 6.5.

Web Builder Projects

The first time you open Web Builder 6.6, it automatically updates any previous projects so you can continue to run the applications or use the Web services or Java beans. This automatic project update occurs only if you install Web Builder 6.6 in the same folder where you installed previous versions of Web Builder. You can deploy, undeploy, or delete previous Web projects, but you cannot modify these projects in Web Builder 6.6.

Some earlier options are no longer available for creating new projects. Instead of .NET and Java procedure-based or screen-based Web applications, you can create .NET or Java Web applications that incorporate the functionality of screen-based or procedure-based project types. This functionality was introduced in version 6.5.

.NET 1.1 Projects

Verastream Host Integrator now supports projects using a .NET 2.0 framework. If you have a project created with a .NET 1.1 and Visual Studio version 2003, you can continue to build and deploy it.

.NET Error Message "Type Library not registered"

If you have an existing .NET project (such as C# Web service) used with a prior version of Verastream AppConn for COM (appconn.dll), after upgrading to version 6.5, the Microsoft Visual Studio .NET development environment may show the appconnlib reference is invalid and/or the type library is not registered (even though no runtime incompatibility occurs with the 6.0 connector used with a 6.5 server). To allow your project to re-compile, delete the invalid reference and re-add the COM reference to appconncom.dll (now named Attachmate Verastream Host Integrator 6.5 in the list of COM libraries).

Web Builder and _HIDE, _SHOW model strings

In previous versions, Web Builder used the naming convention of _SHOW or _HIDE appended to rejuvenation (screen-based) models with attributes, recordsets, or procedures to control the display of these elements. These naming conventions are no longer applicable. In version 6.6, you can control the display of these elements by selecting that option on the Project Properties dialog box in Web Builder. You can continue to use existing models.

New Settings and Requirements

Compatibility Settings for Previous Versions

When you open a model created in an earlier version of the Design Tool, you'll see the following message, "This model was created with a prior version of the Verastream Host Integrator." The compatibility settings described below are enabled to allow your models to maintain the same behavior as they had in an earlier version of Host Integrator.

Review the compatibility settings and consider disabling these settings in order to take full advantage of current product functionality. In most cases, you will not see any changes in the behavior of your model. If you notice a change, use the guidelines included in the settings descriptions to make any necessary modifications. You can also re-enable a compatibility setting at any time. To view compatibility settings, select View Settings from the Settings menu, then open the Compatibility category.

 

 

 

  Attachmate