TDM patches are available for download from the Test Data Manager (TDM) Support Patches page.
Enter your Broadcom Support Portal credentials when prompted.
To Download Files from a Broadcom Support Case:
- Login to Broadcom Support Online
- Click on the ‘Enterprise Software’ icon.
- Click on 'Case Management' icon
- Look in your ‘My Cases’ tab or search for [Your Case number] in the ‘Search Cases’ tab.
- Click on the ‘Attachments’ -> ‘Manage File Attachments’ section.
- Login to https://supportftp.broadcom.com/ (if prompted).
- Click on the ‘files_from_broadcom’ link.
- Click on the file you need to download.
Below are instructions on how to apply patches. Find the component the patch has been issued for, then follow the instructions to apply, along with any further instructions support has provided.
Prerequisites:
- User Permissions: "Local Administrator" rights are required for Windows installations.
- Environment Check: Verify that the patch version matches the base GA version before installing, unless you are intending to upgrade to a newer release. When patching TDM Portal, TDM Portal controls the GTREP schema upgrade. When the CA Test Data Manager Portal service first starts, it checks the GTREP schema version, and if needed, upgrades the schema. Therefore, if you unintentionally apply a TDM Portal 4.11 patch to a TDM 4.10 environment, and restart the service, your GTREP repository will be upgraded to a 4.11 schema. Once the repository is upgraded, there is no way to recover, unless you have taken backup before the installation.
- Impact Warning: Once the repository is upgraded by a Portal patch, older versions of Datamaker or Subset may no longer connect until they are also patched.
TDM Web Portal:
The TDMWeb patch contains a full rebuild install of the TDM Portal application. Running the installer will perform an upgrade to TDM Portal.
Note: The first time the CA Test Data Manager Portal service starts up, and connects to the GTREP repository database, TDM checks the schema version of the GTREP database. If the GTREP schema version is older than what is available from the patch, the GTREP schema is upgraded. Therefore, upgrading your TDM Portal version, may also upgrade your GTREP database schema.
- Have your DBA make a full backup of the GTREP database.
- Make sure everyone has logged off the TDM Portal application, and close the browser.
- Stop the CA Test Data Manager Portal Service, and ensure there are no orphaned java.exe tasks running in the Windows Task Manager.
- Stop the OrientDB Service.
- Take a backup copy of the following TDM Portal installation directories: By default, this is located at C:\Program Files\CA\CA Test Data Manager Portal.
- C:\Program Files\CA\CA Test Data Manager Portal (at minimum make a copy of the conf and orientdb subdirectories)
- %ProgramData%\CA\CA Test Data Manager Portal (at minimum make a copy of the orientdb subdirectory)
- Open a Windows File Explorer and navigate to %ProgramData%\CA\CA Test Data Manager Portal\logs and delete or archive all the files. This will ensure we have a fresh, clean set of logs to review in case there are any issues.
- Extract the TDMWeb-<build_release>.zip file in a temporary directory of your choice.
- As Administrator, double-click on the setup_ CA Test Data Manager Portal<build_release>.exe file to start the installation wizard.
- Follow the steps in the installation executable to upgrade the Portal.
- Re-start the Portal services. They should restart automatically, but it would be good to verify. If the services did not restart automatically, first restart the OrientDB service, then restart the CA Test Data Manager Portal service.
Note: By default, the CA Test Data Manager Portal service is configured to start under the Local System Account. If your implementation of the "CA Test Data Manager Portal" Windows service should be running under a service account, you will need to:- Stop the CA Test Data Manager Portal service
- Right-click on the CA Test Data Manager Portal service, and select Properties
- In the Properties dialog window, select the Log On tab
- Modify the properties to run the service under the appropriate service account
- Select OK, and close the dialog window.
- Restart the CA Test Data Manager Portal service.
- Open the Web browser and clear the browser cache.
- It may take several minutes for the TDM microservices to fully restart. You can monitor this by opening Task Manager and watch the CPU utilization of the machine. While the microservices are starting, you will see the CPU very high. Once the CPU utilization returns to normal, you can re-launch the Portal Page.
- Log into Portal and verify that the upgraded version is displayed in the lower left.
- Re-test issue.
Datamaker:
The GT Data Maker patch contains a full rebuild installation of the GT Data Maker application.
- Take a backup copy of your GTDatamaker directory folder. By default, this is located at C:\Program Files (x86)\Grid-Tools\GTDatamaker.
- Extract the contents of the GTDataMaker-<build_release>.zip into a temporary directory of your choice.
- As Administrator, double-click on the setup_GTDatamaker.exe to start the installation wizard.
- Follow the steps in the wizard to complete the installation.
- Open Data Maker
- Re-test the issue.
Subset:
The SubSet patch is not a full installation of the GT SubSet application, and only contains the patched files, which need to be replaced inside the GTDatamaker install directory.
- Take a backup copy of your GTDatamaker directory folder. By default, this will be located at C:\Program Files (x86)\Grid-Tools\GTDatamaker.
- As Administrator, extract the SubSet-<build_release>.zip file into the GTDatamaker directory folder.
- Restart Subset UI.
- Retest the scenario.
Note: As known issues, during any Data Maker upgrade. Subset application configuration files will be lost. It is important to back up the configuration files before any Data Maker or SubSet upgrade or patch. These subset configuration files contain: 1) Rules files that store the logical relationships. 2) Connection profiles if default location was moved to Datamaker folder
Fast Data Masker (FDM):
The FastDataMasker patch contains a full rebuild install of the Fast Data Masker application. Running the installer will perform an upgrade to Fast Data Masker.
- Take a backup copy of your FDM directory folder. By default, this will be located at C:\Program Files\Grid-Tools\FastDataMasker.
- Extract the FastDataMasker-<build_release>.zip (Windows), or FastDataMasker-<build_release>.tar.gz (Linux) file, in a temporary directory of your choice.
- As Administrator, double-click on the ‘setup_FastDataMasker.exe’ installation file.
- Continue through the installation wizard steps to complete the upgrade.
- Restart FDM.
- Retest the scenario.
Javelin:
The Javelin patch contains a full rebuild install of the Javelin application.
- Take a backup copy of your Javelin directory folder. By default, this will be located at C:\Program Files\Grid-Tools\Javelin
- Uninstall the previous release of Javelin. This can be done from the Windows Control Panel.
- Extract the Javelin-<build_release>.zip file in a temporary directory of your choice.
- As Administrator, double-click on the ‘setup_Javelin_<build_release>.exe’ installation file.
- Continue through the installation wizard steps to complete the new installation.
- Restart Javelin.
- Retest the scenario.
TestMatch:
The TestMatch patch is not a full installation of TestMatch, and only contains the patched files, which need to be replaced inside the TestMatch install directory.
- Take a backup copy of your TestMatch directory folder. By default, this will be located at C:\Program Files (x86)\Grid-Tools\GTDatamaker\TestMatch.
- Extract the TestMatch.<build_release>.zip file into the GTDatamaker\TestMatch directory folder.
- Restart Datamaker, or TDM Portal (whichever you are using for TestMatch).
- Retest the scenario