action.skip

Upgrading from Previous Versions of Host Integrator

If you are upgrading to Verastream Host Integrator 7.8.x from a previous version read this section to determine how best to proceed with the installation.

If you are upgrading from versions earlier than 7.7.x, see the Upgrade section of the support site.

You cannot use this upgrading process to apply VHI hot fixes. See the support download page on the Technical Support for instructions on applying hot fixes.

Note

All VHI versions 7.5 and higher support SHA-256 security certificates with 2048 bits keys. When you upgrade from a previous version, existing certificates (installed with the previous version) are maintained.

Upgrading on Windows

To begin the migration process, perform the following steps:

  1. As a good practice, back up your existing project files.
  2. Run setup.exe from the current version’s install image.
  3. A message confirms that a previous installation has been detected. You are prompted to continue. Click Yes.
  4. The installation completes with a message indicating its success.

Upgrading on Linux

This process includes the following steps:

  1. Make a note of your existing administrative password set during original installation or changed in Management>Servers>Management Cluster>Change Admin Password.
  2. Back up existing files
  3. Install VHI.
  4. A message confirms that a previous installation has been detected. You are prompted to continue. Click Yes.
  5. The installation completes with a message indicating its success.

You can specify --owner user:group to install VHI as non-root. Whatever user is used, either non-root or root, that user must also be used to upgrade, uninstall, and reinstall VHI. If root needs to assume ownership of a non-root installation, VHI must be uninstalled and the directory, in this example, /opt/rocketsoftware/verastream is deleted. The new installation will be owned by root or whatever user you specify.

Upgrading Model Files and Web Applications

Your deployed models from the previous version will continue to function on a new session server. No manual upgrade is required. When you open a model from the previous version in the Design Tool, it is saved as a model for the current version. There are additional compatibility switches to allow older models to run without being affected by some newer enhancements.

However, your Java Web applications are not automatically deployed after an upgrade and you must rebuild the Web Builder project and redeploy it.