Upgrading to Host Integrator 6.6 in a Linux/UNIX Environment
Technical Note 40030
Last Reviewed 11-Sep-2008
Applies To
Verastream Host Integrator version 6.6
Summary
This technical note provides detailed steps to upgrade Verastream Host Integrator to version 6.6 in a Linux/UNIX environment. The upgrade process includes backing up files, removing the existing installation, installing version 6.6, and migrating the existing configurations and host application models.
Note: For information about upgrading to Host Integrator 7.0, see Technical Note 10094.
Overview
In the Linux/UNIX environment, upgrading Host Integrator requires these steps.
The procedure below assumes the following.
- All Host Integrator components are installed on the same Linux/UNIX machine.
- The Authentication, Administration, and Directory Services (AADS) is not linked to any other Host Integrator servers. (For example, you are not using Session Server load balancing as described in Technical Note 10052.)
- The models can be migrated first and upgraded in the Design Tool at a later time. (For more information on updating models, see Technical Note 40023.)
- Although you can install the Host Integrator files to a directory of your choice, the steps assume an install directory of /usr/vhi.
I. Back up the existing files
- Log in as root on your Linux/UNIX machine.
- Copy the /usr/vhi/etc directory to a temporary directory. (In this example, the temporary directory is /tmp/vhi.)
mkdir /tmp/vhi
cp -r /usr/vhi/etc /tmp/vhi
- If you are upgrading an Administrative WebStation, look for the console.install file in /usr/vhi/lib/java. This file exists only if the Administrative WebStation was run locally in a browser on the machine where the Host Integrator server is installed. If console.install is present, then copy it to the temporary directory. For example:
cp /usr/vhi/lib/java/console.install /tmp/vhi
If console.install is not present, skip this step.
- Copy the deploy directory, /usr/vhi/deploy, to a location outside of the existing Host Integrator installation directory, such as the following:
cp -r /usr/vhi/deploy /tmp/vhi
- Before you uninstall the existing Host Integrator components, make a note of the current settings:
On the Linux/UNIX machine: The location of the existing Host Integrator installation
In the Administrative WebStation:
- Host Integrator domain server settings
- LDAP settings (Note: LDAP settings cannot be migrated; you will need to restore these after the upgrade.)
- Security: enabled/disabled
II. Remove the existing installation
Run the Verastream Host Integrator 6.6 setup command as shown below to uninstall Host Integrator. Answer Yes when you are prompted to remove the existing Verastream Host Integrator Installation.
III. Install all Host Integrator 6.6 components except the Session Server
When upgrading in the Linux/UNIX environment, the AADS must be installed and the AADS settings migrated before the Host Integrator server is installed.
- Install version 6.6 into the same directory where the previous version was installed. This technical note assumes /usr/vhi.
- Use the command below to install all components except the server.
sh install.sh -installdir /usr/vhi -componentsaads:apicpp:apijava:help:hostemul:logutils:smonitor:webstation
The components specified in the command above are:
aads
|
AADS server
|
apicpp
|
AppConn Connector for C
|
apijava
|
AppConn Connector for Java
|
help
|
Product Help
|
hostemul
|
Host Emulator
|
logutils
|
Log Viewer and Export Utility
|
smonitor
|
Session Monitor
|
webstation
|
Administrative WebStation
|
- Accept the defaults and proceed with the installation. When prompted, do not start the AADS.
- When Setup is complete, confirm that all of the components are stopped:
/usr/vhi/bin/atstart -stop all
IV. Migrate the AADS settings
To preserve the AADS configuration, copy the saved files that you created above into the new installation directory.
Note: Some of these files may not exist in your installation.
cp /tmp/vhi/etc/aads/.bindings /usr/vhi/etc/aads
cp /tmp/vhi/etc/aads/.keystore /usr/vhi/etc/aads
cp /tmp/vhi/etc/aads/.cert.fingerprint /usr/vhi/etc/aads
cp /tmp/vhi/etc/aads/aads.properties /usr/vhi/etc/aads
cp /tmp/vhi/etc/aads/domains/.bindings /usr/vhi/etc/aads/domains
cp /tmp/vhi/etc/aads/servers/.bindings /usr/vhi/etc/aads/servers
cp /tmp/vhi/etc/aads/profiles/.bindings /usr/vhi/etc/aads/profiles
V. Install the Host Integrator Session Server
- Start AADS before installing the server:
/usr/vhi/bin/atstart -start aads
- To install the Verastream Host Integrator 6.6 server, use this command:
sh install.sh installdir /usr/vhi components server
- Do not start the server when prompted. If the server starts before the model files are migrated, errors will be logged.
- Restore the session server configuration file:
cp /tmp/vhi/etc/sesssrvr.config /usr/vhi/etc
- If you did not install an Administrative WebStation, skip to VII. Migrate the deployment directory.
VI. Migrate the Administrative WebStation
- Restore the Administrative WebStation configuration file:
cp /tmp/vhi/console.install /usr/vhi/lib/java/console.install
- Start the Administrative WebStation:
/usr/vhi/bin/atstart -start webstation
VII. Migrate the deployment directory
Restore the deployment directory:
cp -r /tmp/vhi/deploy /usr/vhi
VIII. Start all components and verify the upgrade
- Use this command to start all components, including the Host Integrator server:
/usr/vhi/bin/atstart -start all
To verify the server components are running, see Technical Note 10054.
- At this point, the Host Integrator Server recognizes the original model file/directory structure and upgrades the models in the 6.6 deploy directory.
- Open the Administrative WebStation.
Local Linux/UNIX installation: Use a web browser to open <vhi>/bin/VHI_Administrative_WebStation_Login.html where <vhi> represents your Verastream Host Integrator installation directory.
Remote system: In a web browser, open http://<hostname>:9642/apptrieve where <hostname> represents the system running the Verastream Host Integrator Administrative WebStation service.
The first time you run version 6.6 Administrative WebStation, you may need to assign the AADS, or possibly remove and re-add the AADS.
- Confirm that your models are activated and confirm or restore the settings that you noted earlier in this process (section I. above):
- Host Integrator domain server settings
- LDAP authentication settings
- Security: enabled or disabled
IX. Update Session Monitor Directory Server
As of version 5.5, the Session Monitor creates a default security certificate when connecting. This certificate may still be present after uninstalling the previous version of Host Integrator and reinstalling the new version. After the upgrade, the Session Monitor will attempt to use a certificate that is now out of date. When attempting to connect, you'll see messages such as "SSL connection failed. Certificates don't match." To correct this problem, select Remove Directory Server from the Configure menu. You can ignore additional error messages while doing this operation. Next, select Add Directory Server to add it again with an appropriate security certificate.
Related Technical Notes
| 10030 |
Supported Platforms and Systems Requirements for Verastream Host Integrator |
| 10048 |
Configuring Verastream AADS Failover on UNIX |
| 10052 |
Configuring Verastream Host Integrator 6.x Server Load Balancing |
| 10054 |
How to Verify Verastream Servers are Running |
| 10061 |
Features Introduced in Verastream Host Integrator 6.0 |
| 10069 |
Features Introduced in Verastream Host Integrator 6.5 |
| 10080 |
New Features in Verastream Host Integrator 6.6 |
| 10094 |
Upgrading to Host Integrator 7.0 in a Linux/UNIX Environment |
| 40023 |
Compatibility Settings in Verastream Host Integrator |
| 40031 |
Upgrading to Host Integrator 6.6 in a Windows Environment |
| 40999 |
Verastream Host Integrator Technical Notes |