Additional Upgrade Details

This section provides details on how to perform an in-place upgrade of .  For an in-place upgrade, run the installer for ldt 10.3 and specify the same directory as the existing installation.
dts103
This section provides details on how to perform an 
in-place upgrade
 of 
DevTest Solutions
.  For an 
in-place upgrade
, run the installer for 
DevTest
10.3 and specify the same directory as the existing installation.
This section assumes that the earlier version is 8.0 or later.
If you have any questions, contact CA Support
before
you attempt the upgrade.
2
Product Changes
For information about how the functionality has changed since the version of your existing installation, see the Release Notes.
Licensing
The
devtestlic.xml
file contains the license details.
To upgrade from DevTest 10.2 or earlier, you must request a new license file. For more information, see License Administration and How License Activation Works.
Enterprise Dashboard and Registry
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.
For both registry and Enterprise Dashboard, you do not need to create a new database. You cannot change the type of database during the upgrade process. For example, you cannot switch from Oracle to SQL Server.
The database user must have DBA privileges. Otherwise, the Enterprise Dashboard and registry will fail to start after the upgrade. A permissions check is performed at the beginning of the database upgrade. This checks the appropriate permission level to avoid making modifications to the database.
To remain in compliance with your license agreement, you must retain all usage data that is in your Enterprise Dashboard database.
 
 The installer does not upgrade the registry database. After finishing the upgrading processes by the installer, the first invocation of the registry will upgrade the registry database.
If the database is terminated abnormally by the user or by the system, the registry will check for the last installed version on the next database start. This information might not be available due to the abnormal termination. The way to resolve this is to either restart the database and the initialization or disable the migration check in the LISA properties file.
  • In
    DevTest
    9.1 and later, Enterprise Dashboard properties are kept in the
    dradis.properties
    file. 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 example:
 
'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'.
  • 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 command:
    docker run –d –p 2003:2003 --name=dradisCIC devtest-licensed:latest /opt/devtest/bin/EnterpriseDashboardCIC
  • If the EnterpriseDashboardCIC service is running under Docker, see Docker Containers.  
  • For more details on backward compatibility with older registries, see Maintain Registries.
Using DDL Scripts to Upgrade Enterprise Dashboard
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 10.2.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-10.2.0.jar -ud 9.0.0
    This code creates registry upgrade scripts from release 9.0.0 under the current folder.
    To specify a destination folder, add more arguments as follows.
    Java.exe -jar C:\DevTest\lib\core\lisa-core-10.2.0.jar -ud 9.0.0 C:\ddl
  • For Enterprise Dashboard schema upgrade scripts, execute:
    Java.exe -jar C:\DevTest\lib\dradis\dradis-10.2.0.jar -ud 9.0.0
    This code creates Enterprise Dashboard upgrade scripts from release 9.0.0 under the current folder.
    To specify a destination folder, add more arguments as follows.
    Java.exe -jar C:\DevTest\lib\dradis\dradis-10.2.0.jar   -ud   9.0.0  C:\ddl
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 10.2 can accept connections from 8.0 and 8.4 registries. Enterprise Dashboard 8.4
cannot
accept connections from a 10.2 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 10.2 version.
  • The
    _local.properties
    file of the existing installation is replaced with the 10.2 version.
  • The
    _site.properties
    file of the existing installation is replaced with the 10.2 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.
Database Safeguards
A permissions check is performed at the beginning of the database upgrade. This checks the appropriate permission level to avoid making modifications to the database.
: If the database is terminated abnormally by the user or by the system, the registry will check for the last installed version on the next database start. This information might not be available due to the abnormal termination. The way to resolve this is to either restart the database and the initialization or disable the migration check in the LISA properties file.