In this section:

Introduction

Before upgrading from previous versions of DTP, make sure that your system meets the system requirements.

The installer automatically backs up your data as part of the upgrade process, but you can manually back up your system as an extra precaution.

If you intend to install DTP Enterprise Pack and are on Windows, you may be prompted to download the Microsoft Visual C++ Redistributable package during the installation process. See Microsoft Visual C++ Redistributable for additional information.

Upgrading with DTP Enterprise Pack

You can not upgrade directly to the latest version of DTP with Enterprise Pack if you are upgrading from 2020.1 or older. For older installations, upgrade to 2020.1, then incrementally upgrade to the latest version. Upgrading incrementally ensures that the mongoDB shipped with DTP Enterprise Pack functions as expected. Consult the table below for upgrade paths:

Current VersionUpgrade to
5.4.3 or older2020.1
2020.12020.2
2020.22021.1
2021.12021.2 or newer

Upgrading without DTP Enterprise Pack 

If you are upgrading from 5.3.3 or older, you must upgrade to 5.4.0, 5.4.1, 5.4.2, or 5.4.3 in order to upgrade to the latest version. Upgrading from Concerto is only supported by upgrading to 5.4.0 prior to upgrading to the latest version. Refer to your version in the Upgrading chapter of the DTP 5.4.3 documentation for details. Consult the table below for upgrade paths:

Current VersionUpgrade to
Concerto5.4.0
5.3.3 or older5.4.0, 5.4.1, 5.4.2, or 5.4.3
5.4.0 to 5.4.12021.2
5.4.2 or newer2022.1

Windows 

Starting with DTP 2020.1, DTP is installed in two directories. The main installation directory contains application files, such as the web server and other executables. The DTP data directory contains application configuration files, as well as data sent to DTP from connected tools. By default, DTP application files will be installed in the C:\Program Files\Parasoft\DTP directory and DTP data files will be installed in the C:\ProgramData\Parasoft\DTP directory. See Installation Overview for additional Information.

Follow these instructions if you are upgrading from the most recent version of DTP and DTP Enterprise Pack:

  1. Stop all Parasoft services, including DTP Enterprise Pack if applicable. See Stopping DTP Services. 
  2. Run the installer and choose the Reinstall DTP option when prompted. The DTP installer automatically handles all upgrade processes. If you intend to install DTP Enterprise Pack, you may be prompted to download the Microsoft Visual C++ Redistributable package before the wizard starts. See Microsoft Visual C++ Redistributable for additional information. 
  3. Click Finish to complete installation and start DTP and Enterprise Pack (if installed) processes.

If you are upgrading from DTP 5.4.2 or older, you can remove the GRS database as an optional step (see the DTP 5.4.3 release notes for additional information). Refer to the documentation for your database server software for instructions on how to delete the database.

If you did not install Enterprise Pack during the initial DTP installation process, you can re-run the latest DTP installer to install DTP Enterprise Pack at any time. 

Linux 

Starting with DTP 2020.1, DTP is installed in two directories. The main installation directory contains application files, such as the web server and other executables. The DTP data directory contains application configuration files, as well as data sent to DTP from connected tools. See Installation Overview for additional Information.

Follow these instructions if you are upgrading from the most recent version of DTP and DTP Enterprise Pack:

  1. Open a command prompt and navigate to the current DTP installation.
  2. Stop all Parasoft services, including DTP Enterprise Pack if applicable. See Stopping DTP Services.

  3. Run the DTP installation script with the -u option to specify the DTP installation directory to update and the -d option to specify where DTP data files should be installed:

    ./DTP.sh -u <DTP_INSTALL> -d <DTP_DATA_DIR>

    You must type the full, non-relative path.

    For example: ./DTP.sh -u /home/<user>/dtp -d /home/<user>/dtp_data

    If you want to modify crontab entries for DTP during the upgrade, turn on the --setup-cron flag:

    Example with --setup-cron flag activated
    ./DTP.sh -i /home/<user>/dtp -d /home/<user>/dtp_data --setup-cron

    Activating the --setup-cron flag will cause a menu of options to appear during the upgrade process from which you can choose to either append DTP entries to the current crontab or overwrite it.

  4. The installer will check the specified DTP installation directory for DTP Enterprise Pack. If Enterprise Pack is detected, you will be prompted to either remove or update the pack. If Enterprise Pack is not detected, you will be prompted to install it in the <DTP_INSTALL>/dtpservices directory. 

  5. When the DTP.sh script finishes, run dtpconsole.sh to start DTP and Data Collector. 

  6. Navigate to the <DTP_INSTALL>/dtpservices directory and run the dtpservices.sh script with the start argument to start Enterprise Pack. 

    ./dtpservices.sh start

If you are upgrading from DTP 5.4.2 or older, you can remove the GRS database as an optional step (see the DTP 5.4.3 release notes for additional information). Refer to the documentation for your database server software for instructions on how to delete the database.

If you did not install Enterprise Pack during the initial DTP installation process, you can re-run the latest DTP installer to install DTP Enterprise Pack at any time. 

Upgrading the Database Structure

DTP verifies the database structure when you log in with administrator credentials after upgrading. You may be prompted to update the database.

 After the initial installation, the default administrator user/password was admin/admin. However, this might have been changed when your DTP was customized.

To upgrade the database structure, click Run Update. A message is displayed when the database schema upgrade process is finished and DTP is ready to use.

Post-Upgrade Steps

After an upgrade, you may need to manually recreate certain configurations previously made in the <DTP_HOME>/bin/variables file. Configurations you may have made include:

Additional Notes

When upgrading DTP, a backup is automatically created in the same parent directory. For example, a DTP installation at /home/test/dtp would result in a backup at /home/test/dtpYYMMDD_HHmmSS, where YYMMDD_HHmmSS represents the date and time when the backup and upgrade were created. When crontab has been modified by your DTP upgrade script, the old crontab is backed up to a <DTP_INSTALL>/bin/cronguard.cron~ file.

Upgrading DTP in Docker

The process for upgrading DTP in Docker is described below. You will need to back up your current DTP data directory and run the new container using the same volumes that your old container did. More information about the volumes used when the DTP container was created can be found under "Deploying DTP in Docker" on the Deploying DTP to Docker and Cloud Environments page.

  1. Back up your DTP data directory.
  2. Download the latest DTP container image from Docker Hub: https://hub.docker.com/r/parasoft/dtp.

  3. Stop your current DTP container.

    docker stop <name-of-container>
  4. Using the DTP image downloaded in Step 2, run a new container with the same configuration of your old container.
    • If you want to keep the old DTP container, make sure the new container has a different name or it will not start.
  • No labels

Need assistance? Visit our support page