Knowledgebase

Search:     Advanced search

Installing Helix ALM Upgrades in a Test Environment

Article ID: 527  |  Last updated: 28 Apr, 2017

Before upgrading Helix ALM to a new version in your production environment, you may want to install it in a test environment. You can use a copy of projects from your production environment in the test environment to evaluate new features, estimate downtime required to upgrade, and make sure no issues occur during the upgrade.

The following instructions assume that Helix ALM is already installed in the test environment. If it is not, install it before performing the following steps.

Note: Do not copy Helix ALM databases back into the production environment after using them in the test environment or you will lose project data.

Helix ALM native databases

  1. Stop the Helix ALM Server in the production and test environments.
  2. Copy the TTServDb directory from server computer in the production environment to server computer in the test environment. By default, the TTServDb directory is in the Helix ALM application directory. Overwrite the existing directory on the test computer.
  3. Start the production Helix Server.
  4. Upgrade Helix ALM to the new version in the test environment. See the installation help for more information.

Oracle, PostgreSQL, and SQL Server databases

  1. Stop the Helix ALM Server in the production and test environments.
  2. In the production environment, perform a full backup of the project database to use in the test environment.
  3. Copy the project directory from server computer in the production environment to server computer in the test environment. Projects are stored in the TTServDb directory, which is stored in the Helix ALM application directory by default. You can also create a new project directory in the TTServDb directory if you do not need file attachments from Helix ALM to perform your testing.
  4. Start the production Helix ALM Server.
  5. Create a new database in the RDBMS.
  6. Restore the project database backup to the new database.
  7. If you use SQL Server, create a system DSN that points to the new database.
  8. Start the Helix ALM Server in the test environment.
  9. Start the Helix ALM Server Admin Utility in the test environment.
  10. If you use SQL Server, add a new RDBMS connection using the system DSN you created. Click Server Options, select the RDBMS Connections category, and click Add.
  11. Add the projects to the test server. Click Projects and then click Add Existing.
  12. Stop the Helix ALM Server in the test environment.
  13. Upgrade Helix ALM to the new version in the test environment. See the installation help for more information.
Article ID: 527  |   Last updated: 28 Apr, 2017
Tags
upgrade test environment

Prev   Next
Helix ALM Cannot Communicate with IMAP Servers When Using...     Controlled Hyperlinks Do Not Work