You should verify that all requirements have been met before you begin installing Development Testing Platform (DTP), migrating from Concerto (4.x) to DTP, or upgrading to a new version of DTP.
In this section:
64-bit versions are required for all platforms. DTP requires 64 bit Java Runtime Environment. The following operating systems are supported.
Microsoft .NET Framework 4.0 is required
Distributions that support Linux 64 bit Java Runtime Environment.
A dedicated non-root user account for installing and managing DTP is recommended.
A non-root user account is required for installing and managing DTP distributions that include an embedded database server.
|Solaris (SPARC only)|
A dedicated non-root user account for installing and managing DTP is recommended
If you are installing DTP on a virtual machine (VM), make sure to allocate enough resources. Running DTP on a physical machine may result in greater performance.
- Quad core processor (or higher) with 2GHz CPU
- 8GB memory (10GB recommended if using MySQL). By default, 4GB are allocated to DTP Server and Data Collector.
- If you are installing MySQL with Development Testing Platform, two hard drive partitions are required, as well as 100GB for the database and 60GB for programs.
- For heavy usage (more than 100,000 tests per day), you should install the database on a dedicated database server (physical machine) to ensure optimal performance of I/O writes.
- DTP server cannot be installed on a machine with an underscore ("_") in its name.
Before you begin installation, you should verify that the necessary ports are available:
|80 (Windows), 8080 (Linux)||DTP Server|
|8443 (Windows and Linux)||SSL Connector|
|8082||Data Collector for Parasoft analysis engines and third-party integrations.|
|8787||Used by the embedded database server shipped with distribution; this port is non-configurable.|
|3306||Default port used for sending and retrieving MySQL data Report Center and Project Center data.|
|32323||Data Collector for Parasoft 9.x code analysis and testing products.|
|61617||JMS events broker|
|1883||MQTT transport connector|
|8000||Policy Center; access to Policy Center depends on your license. See DTP Enterprise Pack for additional information.|
|8314||Extension Designer; accessing Extension Designer depends on your license. See DTP Enterprise Pack for additional information.|
|8315||Extension Designer; accessing Extension Designer depends on your license. See DTP Enterprise Pack for additional information.|
|8316||Embedded MongoDB database for DTP Enterprise Pack. See DTP Enterprise Pack for additional information.|
|8320-8399||DTP Enterprise Pack services. See DTP Enterprise Pack for additional information.|
You can customize the Development Testing Platform Server ports as necessary. See Reconfiguring DTP Ports (Optional).
The latest version of the following browsers are supported:
- Internet Explorer (compatibility view must be disabled)
- Microsoft Edge
- Google Chrome
Open File Descriptor Limit
You may run up against a limit imposed on Linux or Solaris platforms on the per-process number of open file descriptors. The limit affects the number of allowable concurrent open connections that DTP can safely support. If many concurrent users will interact with DTP components, such as Report Center Dashboard or REST APIs, you should increase the open file descriptor limit before starting DTP.
Parasoft recommends setting the limit to approximately 100 times the number of concurrent users logged in. For example, if you expect 100 concurrent users, an open file descriptor limit of 10,000 should be sufficient.
Server behavior is inconsistent across operating systems, so you should use discretion when determining the proper limit for your environment. Methods for increasing the limit vary widely for different distributions. Consult your operating system documentation to determine whether it is possible to increase the limit and how to do so.