CA Test Data Manager has the following installation prerequisites:
CA Test Data Manager supports the following hardware:
A centralized server that supports multiple simultaneous terminal servers (RDS) simplifies maintenance. Alternatively, each user can install the software on a laptop or workstation and can connect to a shared repository. For production environments, a DBA managed centralized database server is best for the test data repository. For training and trial purposes, you can use a locally managed database.
The following list shows system requirements for various CA Test Data Manager server types:
The CA TDM Portal is tested on the following operating systems:
The Portal may work on other versions, but they have not been tested.
CA Test Data Manager requires a repository to store product metadata. You can also use the repository to store test data. The repository can be on the same server as CA Test Data Manager, or can be a remote server. For production environments, we recommend a dedicated database server for the repository that is backed up and monitored.
CA Test Data Manager supports the following databases for the repository:
The repository database and server also requires the following:
For database access from a remote system, Oracle databases require an Oracle client with the TNSNAMES.ora file. All other database platforms require an ODBC driver software and system DSN entries.
Oracle 12c can be installed in one of two ways, as a plain database instance similar to 11g, or as a container database.
A container database is used to create a multi-tenant database system. A container contains a set of “pluggable” databases which can be run inside the container as if they are separate instances. DBAs can move pluggable databases from container to container in a simple manner when they need to move to different hardware or storage. It also simplifies administration in various ways. See Introduction to the Oracle Multitenant Architecture for more details.
Always install CA TDM databases and the repository in a pluggable database and not in the “root” or container database itself. From the point of view of CA TDM, a pluggable database is a regular instance of Oracle with its own service name. For example, if you create a pluggable database called “plug1” then it will appear as a service called “plug1.mydomain.com” with a tnsname of “plug1”. The container itself has a tnsname of “orcl” by default. To install gtrep on plug1, edit the install script (repository.bat) and set the destination (environment variable GT_TNS) to “plug1.mydomain.com”. Similar considerations apply to the sample databases and scramble.
CA Test Data Manager supports additional databases as source and target connections to connect to and publish test data.
The following software is required for CA Test Data Manager installation.
GT Server requires a 64-bit instance of Microsoft Silverlight. If a 32-bit Silverlight higher than version 5.1.3 is installed, uninstall it manually before proceeding.
All software prerequisites are listed in the GT Server installer. The installer checks your system for each prerequisite and installs any software that is not present.
Test Data on Demand
The Test Data on Demand Web UI supports any browser that can embed Microsoft Silverlight applications. The necessary plug-in must be installed on the browser for Microsoft Silverlight.
CA TDM Portal
The CA TDM portal supports the following browsers:
For more information, see Supported Data Sources.
Integration with the following versions of different applications is supported:
CA Service Virtualization
CA Agile Requirements Designer
HP Application Lifecycle Management (HP ALM)
CA Agile Central
The minimum resolution for the CA TDM UI, including CA TDM Portal and Fast Data Masker, must be greater than 1600x900 pixels.
The following privileges are required to manage CA Test Data Manager servers:
CA Test Data Manager supports the use of data in any language that can be represented in UTF-8 character encoding. UTF-8 support requires that the repository is configured for UTF-8 encoding instead of ASCII.