Skip to content
DevTest Solutions - 9.5
Documentation powered by DocOps

Upgrading DevTest

Last update November 9, 2017

This section describes how to upgrade an earlier version of DevTest Solutions to the latest version.

The type of upgrade that this section describes is an in-place upgrade. You run the installer for DevTest 9.5 and specify the same directory as the existing installation.

This section assumes that the earlier version is 7.5 or later.

Important! If you have any questions, contact CA Support before you attempt the upgrade.

Product Changes

The products were renamed in version 8.0.

Old Name New Name
CA LISA Service Virtualization CA Service Virtualization
CA LISA Test CA Application Test
CA LISA Pathfinder CA Continuous Application Insight

For information about how the functionality has changed since the version of your existing installation, see the release notes for each newer release.

Licensing

In DevTest 8.0, the license policy changed from component-based licensing to concurrent user-based licensing. The devtestlic.xml file contains the license.

For more information, see How License Activation Works and License Administration.

Enterprise Dashboard

In LISA 7.5.x, the Enterprise Dashboard was an optional component and had a separate installer.

In DevTest 8.0, the Enterprise Dashboard became a required component and was integrated into the DevTest installer.

CA Technologies does not need you to preserve the data from a 7.5.x installation of the Enterprise Dashboard. If you want to preserve the data for your own purposes, contact CA Support for assistance.

When you do an in-place upgrade from DevTest 8.0 or later, the schema of the Enterprise Dashboard database is updated and the existing data is maintained. You do not need to create a new database.

To remain in compliance with your license agreement, you must retain all usage data that is in your Enterprise Dashboard database.

The database user must have DBA privileges. Otherwise, the Enterprise Dashboard will fail to start after the upgrade.

You cannot change the type of database during the upgrade process. For example, you cannot switch from Oracle to SQL Server.

The registry database is not upgraded by the installer. After finishing the upgrading processes by the installer, the first invocation of registry will upgrade the registry database.

After you upgrade from a previous DevTest version, you will have DevTest and Enterprise Dashboard schema upgrade scripts in the LISA_HOME\database\upgrade folder with all supported databases for previous releases. For example, if you upgrade from 9.0.0 to 9.5.0, you see ten DDL files.

  • db2_enterprisedashboard_upgrade_9.0.0.ddl
  • db2_upgrade_9.0.0.ddl
  • derby_enterprisedashboard_upgrade_9.0.0.ddl
  • derby_upgrade_9.0.0.ddl
  • mysql_enterprisedashboard_upgrade_9.0.0.ddl
  • mysql_upgrade_9.0.0.ddl
  • oracle_enterprisedashboard_upgrade_9.0.0.ddl
  • oracle_upgrade_9.0.0.ddl
  • sqlserver_enterprisedashboard_upgrade_9.0.0.ddl
  • sqlserver_upgrade_9.0.0.ddl

To generate upgrade DDLs for other DevTest versions, you must execute with a command-line utility.

  • For DevTest schema upgrade scripts, execute:

    Java.exe -jar C:\DevTest\lib\core\lisa-core-9.5.0.jar -ud 8.5.0

    This creates registry upgrade scripts from release 8.5.0 under the current folder.

    To specify a destination folder, add more arguments as follows.

    Java.exe -jar C:\DevTest\lib\core\lisa-core-9.5.0.jar -ud 8.5.0 C:\ddl

  • For Enterprise Dashboard schema upgrade scripts, execute:

    Java.exe -jar C:\DevTest\lib\dradis\dradis-9.5.0.jar -ud 8.5.0

    This creates Enterprise Dashboard upgrade scripts from release 8.5.0 under the current folder.

    To specify a destination folder, add more arguments as follows.

    Java.exe -jar C:\DevTest\lib\dradis\dradis-9.5.0.jar   -ud   8.5.0  C:\ddl

In DevTest 9.1 and later, Enterprise Dashboard properties are kept in the dradis.properties file. In order to avoid confusion in the future, consider removing the "dradis" properties from your local.properties and site.properties files, as they no longer impact Enterprise Dashboard processing.

With DevTest 9.1 and later, configuration of the Enterprise Dashboard URL has changed. Therefore, the parameters that are passed when starting a registry must change also, to something similar to this:

'docker run -d -p 1505:1505 –p 1528:1528 –p 2010:2010 --name=Registry -e LISA_MORE_VM_PROPS="-Ddevtest.enterprisedashboard.host=10.141.66.40 -Ddevtest.enterprisedashboard.port=1506 -Ddevtest.enterprisedashboard.https.enabled=false" devtest/registry-broker-base /opt/devtest/bin/Registry -n tcp://10.141.66.40:2010/Registry'.

For details see Reactive a Registry or Enterprise Dashboard.

To support pre-9.1 DevTest registries, the EnterpriseDashboardCIC service provides backwards compatibility and must be started (on an image where dradis-CIC is available). Use a command similar to the following:

docker run –d –p 2003:2003 --name=dradisCIC devtest-licensed:latest /opt/devtest/bin/EnterpriseDashboardCIC

 For more details on backward compatibility with older registries, see Maintain Registries.

Registry

When you do an in-place upgrade, the schema of the registry database is updated and the existing data is maintained. This data includes reports, custom users, custom roles, CVS monitors, and CAI paths. The LISA_HOME\Projects folder is also maintained. You do not need to create a new database.

The database user must have DBA privileges. Otherwise, the registry will fail to start after the upgrade.

You cannot change the type of database during the upgrade process. For example, you cannot switch from Oracle to SQL Server.

Mixing Component Versions

The registry and all the underlying components, including DevTest Workstation, must belong to the same release. Mixing component versions under a registry is not supported.

The Enterprise Dashboard is backward compatible through version 8.0 and supports connections from registries of multiple versions. However, the Enterprise Dashboard itself must be the most recent version. For example, Enterprise Dashboard 9.0 can accept connections from 8.0 and 8.4 registries. Enterprise Dashboard 8.4 cannot accept connections from a 9.0 registry.

Property Files

The following list describes what happens to the main property files in an in-place upgrade:

  • The lisa.properties file of the existing installation is replaced with the 9.5 version.
  • The _local.properties file of the existing installation is replaced with the 9.5 version.
  • The _site.properties file of the existing installation is replaced with the 9.5 version.
  • A _dradis.properties file is created. Any customized properties for Enterprise Dashboard in your local.properties or site.properties file are migrated to a dradis.properties file.
  • If you created a local.properties file, the file is preserved as is.
  • If you created a site.properties file, the file is preserved as is.

You are not supposed to modify the lisa.properties file. If you did make changes to the lisa.properties file, the upgrade process overwrites the changes.

Custom Folders

If the existing installation contains any custom folders, the folders are preserved as is.

Custom JAR Files

If the existing installation contains any custom JAR files in the LISA_HOME\lib directory, the JAR files are preserved as is.

Memory Allocation Settings

If the existing installation contains any modified .vmoptions files in the LISA_HOME\bin directory, the files are preserved as is.

Was this helpful?

Please log in to post comments.