This technical note provides detailed steps to migrate Verastream Host Integrator (VHI) from version 6.x to version 7.0 or higher on a Linux, Solaris, or AIX system. The upgrade process includes backing up files, removing the existing installation, installing version 7.x, migrating the existing configurations and host application models, and migrating Web Builder projects.
Note: If you already have version 7.0 installed and are upgrading to version 7.1, see KB 7021582 instead. If you already have version 7.1 installed and are upgrading to version 7.1.1142 (Service Pack 1) or higher, see KB 7021586 instead.
Use the following procedure to upgrade Verastream Host Integrator (version 6.5 or 6.6) to version 7.0 or higher on a Linux, Solaris, or AIX system. Note: If you are using Java web service or web application projects generated in Web Builder, see also Web Project Migration.
- Make a note of your existing installation directory:
Note: In this document, substitute <vhi> or /usr/vhi with the output from the above command (your version 6.x installation directory).
- Log into Administrative WebStation:
- In a web browser, open <vhi>/bin/VHI_Administrative_WebStation_Login.html on the local system, or http://<hostname>:9642/apptrieve from a remote system.
- Log in as a user in the Administrator profile if security is enabled; otherwise use blank credentials.
- Make a note of any non-default configuration for the following items. Since custom security and LDAP settings are not migrated, you will need to manually restore them later (in step 11c below).
|Location in Left Navigation Tree ||Default Value |
|Security > Profiles > Administrator > Actual Group ||***** NONE ***** |
|Security > Profiles > Developer > Actual Group ||***** NONE ***** |
|Security > Profiles > User > Actual Group ||***** NONE ***** |
|Security > Domains ||Security is unchecked |
|Security > Servers ||Security is unchecked |
|Directory Services > LdapAuthentication ||Enabled is unchecked |
|Servers > [server name] > Server Configuration > Server Properties ||Model Debug Messages Directory is <vhi>/etc/reports |
|Servers > [server name] > Server Configuration > Logging Options ||Log Storage Directory is <vhi>/etc/logs/server |
- Back up your existing files
- Create a temporary directory:
- Copy the existing deployed models (including any event handler code):
cp -r /usr/vhi/deploy /tmp/vhi6
- Copy the directory containing session server configuration file, plus model debug messages and session server log (in default locations):
cp -r /usr/vhi/etc /tmp/vhi6
Note: If you are using a non-default Model Debug Messages Directory or Log Storage Directory (from step 3 above), version 7.x will continue to use your custom location (after completing step 8 below).
- If you are using SSL encryption for host connections, and the host requires a client certificate, back up your certificate.pem file:
cp -r /usr/vhi/securehost /tmp/vhi6
- Uninstall the previous version:
sh install.sh -clean
When prompted to confirm (Remove existing Verastream Host Integrator installation?), enter yes.
Note: The install.sh file was provided with version 6.6 and earlier (in the downloaded product .tar file or root of the product CD). Use the tar xvf command to unpack the original .tar file. If the install.sh file is not available, you can manually stop the services and delete the old directories:
/usr/vhi/bin/atstart -stop all
rm -fr /usr/vhi
rm -rf /etc/vhi
- Install version 7.x by expanding the downloaded .tar file (with tar xvf) and/or running the installer file (for example, sh linux/vhisrv-7.1.1142-prod-linux).
For more information on the interactive installer, command line options, or unattended install input file, refer to the Installation Guide for your product version available from https://support.microfocus.com/manuals/vhi.html.
Important: Make a note of the administrative password you create during the installation process. Blank administrative credentials are no longer supported.
In the remainder of this document, substitute /opt/attachmate/verastream with your version 7.x installation directory (basepath).
- After installation completes, stop the Host Integrator services:
/opt/attachmate/verastream/hostintegrator/bin/atstart -stop all
Note: In a multiple-server installation environment (for failover or load distribution), stop services on all servers.
- Migrate the files backed up in step 4 above:
- Copy the deployed models and session server configuration:
cp -r /tmp/vhi6/deploy /opt/attachmate/verastream/hostintegrator
cp /tmp/vhi6/etc/sesssrvr.config /opt/attachmate/verastream/hostintegrator/etc
- Copy the model debug messages and session server log (if you were using the default locations as identified in step 3 above):
cp -r /tmp/vhi6/etc/reports /opt/attachmate/verastream/hostintegrator/etc
cp -r /tmp/vhi6/etc/logs/server /opt/attachmate/verastream/hostintegrator/etc/logs
Note: AADS logs are no longer used. Beginning in version 7.0, AADS is replaced by the Management Server component.
- If you are using SSL encryption for host connections, and the host requires a client certificate, copy your certificate.pem file:
cp -r /tmp/vhi6/securehost /opt/attachmate/verastream/hostintegrator
- Using a text editor, carefully edit the sesssrvr.config file in your /opt/attachmate/verastream/hostintegrator/etc directory. If your Model Debug Messages Directory and/or Log Storage Directory were in default locations, change lines referencing the old version 6.x directory to the new version 7.x directory.
Note: An invalid directory will cause the entire session server configuration to be reset to defaults when the session server service is started.
- Start the Host Integrator services:
/opt/attachmate/verastream/hostintegrator/bin/atstart -start all
Note: In a multiple-server installation environment, complete steps 1 through 9 before starting services on each server.
- Restore previous settings and verify successful migration:
- Run Administrative Console.
Note: Administrative Console replaces the browser-based Administrative WebStation in previous versions. The Administrative Console application runs on Windows only. This component can be installed from the Windows Server Kit or Development Kit. The Windows and UNIX installations should be the same Host Integrator version.
- Connect to the management server and log in with the user name âadminâ and the administrative password created during installation (step 6).
- Restore any custom security and LDAP settings that were noted in step 3.
|Configuration Item ||Location in Administrative Console |
|Local groups for security profile authentication ||Management > Directories > Properties > Enable OS Groups |
|LDAP directory for security profile authentication ||Management > Directories > Add Directory |
|Administrator security profile ||Management > Authorization > Administrator > Add Members |
|Developer security profile ||Management > Authorization > Developer > Add Members |
|User security profile ||Management > Authorization > User > Add Members |
|Session server security ||Host Integrator > Session Server
Explorer > Servers > [server name] > Properties > General
> Security > Enable Security |
Note: For information about compatibility settings for VHI, see the "Compatibility Settings for Host Integrator Upgrades" topic in the VHI User Guide. For example, in VHI 7.6, see http://docs2.attachmate.com/verastream/vhi/7.6sp1/en/topic/com.attachmate.vhi.help/html/reference/compatibility_switches.xhtml.
Web Project Migration
Server Kit versions 7.0 through 7.1.2026 do not include Apache Tomcat and Axis. If you previously generated a Java web service project (or Java web application project) with Web Builder and deployed it to your Linux/UNIX system, choose one of the following alternatives:
- Modify your applications to reference the new automatic web service functionality embedded in the session server. This option is recommended due to significant enhancements, such as no longer needing to re-generate and re-deploy projects after model changes.
- Upgrade to Server Kit version 7.5, which does include VHI Web Server for HTML5 and Java applications generated in Web Builder.
- Install your own separate instance of Tomcat and Axis, and then re-deploy your project.