The DTP installer (Windows) and installation script (Linux) perform most migration processes without additional action, but some tasks must be performed manually. This chapter describes how to run the installer/script and how to perform the manual processes necessary for accessing data that was previously available in Concerto. In this section:

Prerequisites

Before migrating to DTP from Concerto, make sure you read the following chapters and make all necessary adjustments:

• Requirements
• Backing Up Your System
• Enabling SSL

Migrating on Windows

1. Stop Parasoft services. See Stopping Concerto Services.
2. Run the DTP installation file.
3. Accept the license agreement when prompted.
4. Choose installation directory and set the short-cut option when prompted. By default, DTP installs in the C:\Parasoft\DTP directory. If you plan to install DTP Enterprise Pack (see next step) and want to install install to the Program Files directory, you will need to start DTP Enterprise Pack using the console as administrator (see Getting Started with DTP Enterprise Pack).
5. Review the installation settings and click Install when prompted. A dialog will take you through the process of uninstalling Concerto. 
   • Your files will be migrated to DTP. 
   • You may be prompted to delete data related to Concerto. Choosing Yes deletes everything in the Concerto installation directory. Data not stored in the directory, such as database content, is unaffected. 
   • Configuration files are copied to DTP during the installation prior to deleting Concerto files, but you should make sure that you’ve backed up your Concerto installation as a precaution.
6. Choose Remove when prompted to Uninstall Concerto.

Migrating on Linux and Solaris

1. Stop Parasoft services. See Stopping DTP Services.
2. Run the DTP installation script with the -u option:
   

   ./DTP.sh -u DTP_HOME where DTP_HOME is the installation directory of the current Concerto installation.

   You must type the full, non-relative path.

   Example: /home/parasoft/dtp but not ./parasoft/dtp

   If you are upgrading to the DTP distribution that includes an embedded database server, the installer will confirm the status of the database server service.

3. The installer will prompt you to install DTP Enterprise Pack in the [DTP_INSTALL]/dtpservices directory.  If you want to install Parasoft DTP Enterprise Pack, choose [y] and press Enter when prompted. Enterprise Pack includes Extension Designer and Policy Center, which are additional applications that enable you to derive sophisticated SDLC data analytics and implement granular programming policies. A valid DTP Enterprise license is required to use Extension Designer and Policy Center functionality. You can install Enterprise Pack later by re-running the DTP installer. 
4. When the DTP.sh script finishes, run dtpconsole.sh to start DTP and Data Collector. If you are installing the DTP distribution that includes an embedded database server, services will start automatically and you can immediately begin using DTP.

Updating the Database

DTP introduces the new DTP database schema for Report Center. After performing the migration from Concerto to DTP, follow the instructions in Installing MySQL Database Server for Windows to create this new schema.

Deploying Legacy Assets

In order to view data associated with Concerto, you must deploy the legacy.zip archive shipped in the installation directory. The archive contains deprecated assets, including the legacy default dashboard and widgets that provide access to 9.x data (see About 9.x Tools and DTP).

See Deploying Legacy Assets for instructions on how to deploy the assets.

About 9.x Tools and DTP

DTP is optimized to work with data sent by the 10.x series of code analysis and test execution tools (i.e., Jtest, C++test, and dotTEST DTP Engines), as well as functional test data sent by SOAtest 9.10.x. The 9.x series of Jtest, C++test, and dotTEST generate data isn't compatible with DTP 5.3.3 and later and can not be viewed in widgets and reports. Any data currently in the database can only be accessed with legacy components, such as Project Center, deprecated dashboard templates, and deprecated widgets.