Upgrade Product Components

This section provides an overview on how to upgrade an existing  installation. The following upgrade paths are supported:
tdm47
This section provides an overview on how to upgrade an existing 
Test Data Manager
 installation. The following upgrade paths are supported:
  • 3.1.1 to 3.1.2
  • 3.1.2 to 3.1.3
  • 3.1.3 to 3.2
  • 3.1.3 and 3.2 to 3.2.1
  • 3.1.3 and 3.2.1 to 3.2.2
  • 3.1.3 and 3.2.2 to 3.5
  • 3.2.2 and 3.5 to 3.6
  • 3.5 and 3.6 to 3.8
  • 3.6 and 3.8 to 4.0
  • 3.8 and 4.0 to 4.1
  • 4.0 and 4.1 to 4.2
  • 4.1 and 4.2 to 4.3
  • 4.2 and 4.3 to 4.4
  • 4.3 and 4.4 to 4.5
  • 4.4 and 4.5 to 4.6
  • 4.5 and 4.6 to 4.7
When upgrading from CA TDM 4.2 or later, you should also upgrade the vTDM Appliance. For more information about upgrading the vTDM Appliance, see Upgrade the vTDM Appliance.
Follow a supported upgrade path to avoid repository and licensing compatibility issues.
This article provides a high-level upgrade process due to the sheer number of variables involved when implementing
Test Data Manager
. Variables include the number of systems with
Test Data Manager
 components, the repository database type, and the number of enabled configuration editors. This article applies specifically to upgrades to the current release but does have a broader applicability to other supported upgrade paths.
Follow these steps to upgrade your 
Test Data Manager
 installation:
Prepare for Upgrade
To prepare for the upgrade, ensure that all necessary data is backed up and enter your license request, if necessary. If you have already migrated to the new licensing scheme introduced in 
Test Data Manager
 3.1.2, you do not require a new license. You can simply reload the license after upgrade until it expires.
Starting with 3.2.2, the upgrade process automatically backs up all product configurations before the upgrade and restores those configurations during upgrade. Therefore, Step 2 is not required for upgrades to 3.5 and later unless you want to create your own backups for extra security.
  1. Back up your repository database.
    This process varies depending on your database. Check with your DBA.
  2. (Optional) Back up all enabled 
    Test Data Manager
     configurations as follows, using the TDoD Config Editor as an example:
    1. Navigate to TDM_HOME\Grid-Tools\TDoD\TDoD_Config Editor and run TDoDConfigEditor.exe.
    2. On the Configure Server tab, click Backup.
      The config editor creates a backup of the configuration file, and a confirmation message appears.
    3. Back up other enabled config editors using the same process.
    If enabled, other config editors that support backup are:
    • Remote Publish Engine
    • Rally Batch Service
    • HP ALM Service
    • Group Job Process Executor
    • HP ALM Batch Configuration Service
  3. (Optional) Request a license for your upgrade using a Customer Care Case Request: https://support.ca.com/irj/portal/anonymous/customercare.
    This request is only necessary if you are upgrading from an older version or if your license is expiring. Licenses from 3.1.2 and later are reusable with your upgraded software until they expire.
    Provide your Enterprise Site ID, Product Name (
    Test Data Manager
    ), and release number.
    When the request is processed, you receive an activation key. If needed, we recommend that you request the license before performing the upgrade to account for the license turnaround time.
  4. Before upgrading to CA TDM 4.3, remove all vTDM clones that you created with CA TDM 4.2.
Perform the Upgrade
Perform the upgrade by downloading the software and installing it on the systems where 
Test Data Manager
 components exist. This process varies depending on the nature of your installation. If you have 
Test Data Manager
 components that are installed on multiple systems, run the upgrade on each system.
  1. Download the latest release from the Download Center on CA Support Online.
  2. Extract the downloaded zip file on the systems where you want to perform the upgrade.
  3. Run setup_GTServer_
    version
    .exe:
    • The GT Server installer detects the existence of all prerequisites and clears all prerequisite check boxes.
    • For components, select all 
      Test Data Manager
       components that exist on the current system.
    • The GT Server installer upgrades each component by running the different component installers. Retain all default selections. For components that store configuration settings, the installer automatically takes a backup of your current settings and restores those settings after the upgrade.
  4. Repeat Step 3 on all systems that contain 
    Test Data Manager
     components.
The GT Server installer creates installation logs in the Temp folder (%TEMP%). You can find the log files during both fresh installation and upgrade cases. A typical log file name has the following format:
<componentname_version.log>
For example, the GT HP ALM Service version 1.2.3.4 creates a file named GT HP ALM Service_1.2.3.4.log in the Temp folder during installation.
Upgrade the Repository
After the 
Test Data Manager
 upgrade completes, upgrade the repository by renaming the rep.xml file, performing the upgrade, and renaming the file again.
Note:
 The rep.xml lets you store repository credentials so you do not have to connect every time. If you do not use a rep.xml file, you can skip the steps related to the file.
  1. Launch Datamaker using the Desktop icon or through the file system (TDM_HOME\Grid-Tools\GTDatamaker\gtdatamaker.exe).
    The following message appears:
    DB version specified in database (3.2E) is invalid. 
    This version of the software can work with DB version 3.2G only. 
    You are connecting with pre-distributed details (rep.xml) - no upgrade is allowed. 
    Please contact support.
    This message means that you have to upgrade the repository before proceeding.
  2. Navigate to the TDM_HOME\Grid-Tools\GTDatamaker directory, and rename the rep.xml file to rep-old.xml.
  3. From the Windows Explorer dialog, type %appdata% into the file path and select the Grid-Tools folder in the results. Rename the rep.xml to rep-old.xml in this folder. If the rep.xml file does not exist at this location, skip to step 4.
  4. Launch Datamaker again with Administrator permissions by right-clicking the desktop icon and selecting 
    Run as Administrator
    .
    The Test Data Repository log in for 
    Test Data Manager
     dialog opens. It includes the repository profile that you selected in the last installation.
  5. Click the green database connection button.
    The following message appears:
    Test Data Repository version specified in database (3.2H) is invalid. 
    This version of the software can work with Test Data Repository versions 3.2I and above only. 
    In order to run the upgrade you will need to know the user name and password of a user in the ADMIN group. 
    Would you like to attempt an upgrade?
    Note that if you do not see this message, it is most likely that the user that installed the product is not performing the upgrade. If this is the case, you will need to create a new repository profile and provide the appropriate connection details. Check the entry for the new profile and click the green database connection button. You should then see the above message.
  6. Click Yes.
    The login page opens.
  7. Log in with administrator credentials.
    The 
    Test Data Manager
     - Datamaker Repository Schema - Updates Required message opens.
  8. Click Yes.
    The main Datamaker window opens.
  9. Select Settings, Enter Activation Key.
  10. Enter the activation key that you received from you license request, and click the Save button.
    A confirmation opens. Click OK, and you should see a full listing of all connection profiles.
  11. Close Datamaker.
  12. Rename the rep-old.xml files to rep.xml in the TDM_HOME\Grid-Tools\GTDatamaker and %appdata%\Grid-Tools directories.
  13. Launch Datamaker again.
    You should be able to connect successfully to any connection profile.
  14. Repeat the process described in Perform Repository Maintenance to verify that no further repository maintenance is required.
    The upgrade is complete.
Reconfigure the ‘Data Assistant’ Rule Sets
You only need to reconfigure Data Assistant rule sets if you upgrade Datamaker from version 4.1 or lower, where you had Data Assistant rule sets configured. You can determine whether you have configured Data Assistant rule sets by examining the project tree. If the project 'DM Internal Project' exists in the project explorer, then Data Assistant rule sets have been configured, and you need to reconfigure them.
Follow these steps:
  1. Launch Datamaker.
  2. From the Project Explorer, remove the project ‘DM Internal Project’.
    Note: Follow the standard steps to remove a project, that is, remove the lowest levels of the project first, and backwards. Start with removing data pools, then data sets, data groups, project versions, and then the project 'DM Internal Project'.
  3. Close Datamaker.
  4. Delete the row from the gtrep_system_settings table of your repository using the following command:
    delete FROM [dbo].[gtrep_system_settings] WHERE ss_name = 'DM Internal Project'
  5. Log back into Datamaker as admin.
  6. Click
    Settings, Maintain Schemas
    . For more information, see Perform Repository Maintenance.
  7. On  the
    Maintain Connections
    dialog, Click ‘CA Test Data Manager – Datamaker Connection maintenance', then click ‘DM Internal Project – Data Assistant Rule Sets’.
  8. Click 
    Process
    .
  9. Click
    Yes
    when prompted "Would you like to configure the assistant for the first use?"
  10. Wait until the processing is finished and displays the following messages:
    Inserted <number> column values.
    Reloaded Standard Rules
    Reloaded XML Rules
    Reloaded Cloning Rules
    Reloaded Subset Rules
  11. Close the
    Maintain Connections
    dialog.
    You have reconfigured your Data Assistant rule sets and have completed the upgrade.