You should verify that all requirements have been met before you begin installing DTP, migrating from Concerto (4.x) to DTP, or upgrading to a new version of DTP.
In this section:
Operating System
64-bit versions are required for all platforms. DTP requires 64-bit Java Runtime Environment.
Windows
The following versions are supported:
- Windows Server 2022
- Windows 10
- Windows 11
Microsoft .NET Framework 4.0 is required.
Linux
You can install DTP on Linux distributions that support 64-bit Java Runtime Environments.
A dedicated, non-root user account is recommended for installing and managing DTP on Linux.
Database Requirements
DTP supports MySQL, PostgreSQL, and Oracle databases. See Configuring the Database Connection for information setting up the database for use with DTP.
DTP does not ship with the MySQL, PostgreSQL, and Oracle JDBC drivers necessary to set up a database connection. Download the drivers and place them in the <DTP_DATA_DIR>/lib/thirdparty
directory after completing the installation.
MySQL
The following versions are supported:
- MySQL 8.0
- MySQL 5.7
If data continuously loads in an explorer view, increase the value of the read_rnd_buffer_size
variable.
If binary logging is enabled in MySQL, you must use the "ROW" or "MIXED" binary log format. The "STATEMENT" format will not work.
To perform database updates after upgrading DTP, MySQL must have sufficient disk space to write temporary files, which may be an issue for larger databases. When modifying tables or adding an index during an update, MySQL writes to temporary storage (the directory specified by the MySQL tmpdir
variable, which on Linux is the /tmp
directory by default). This temporary storage may be on a different disk partition than where it stores its database tables. For more information on how to configure where MySQL stores temporary files, see: https://dev.mysql.com/doc/refman/8.0/en/temporary-files.html.
MySQL Charset and Collation Settings
The MySQL creation script for the DTP database uses the character set utf8 and collation utf8_general_ci. DTP does not support UTF-8 4-byte character encoding ("utf8mb4").
See the MySQL documentation for more information about server character set configuration: https://dev.mysql.com/doc/refman/5.6/en/charset-server.html.
Oracle
The following versions are supported:
- 23c
- 19c
- 18c
Oracle Charset and Collation Settings
Oracle recommends setting the target character set to AL32UTF8. See the Oracle Database Migration Assistant for Unicode documentation for instructions: https://docs.oracle.com/database/121/DUMAG/ch2migrasteps.htm#DUMAG136.
PostgreSQL
The following versions are supported:
- 16
- 15
- 14
Minimum Number of Database Connections
The database server should provide at least 150 concurrent connections for DTP. If the database server does not provide sufficient connections, DTP may not be able to create a new connection to the database prior to reaching the maximum number of connections.
DTP Enterprise Pack Database
DTP Enterprise Pack, which includes Extension Designer, ships with its own embedded MongoDB. If you are installing DTP Enterprise Pack, and intend to use the embedded MongoDB, we recommend using an XFS file system in Linux or an NTFS file system in Windows, as per the MongoDB documentation and described in the excerpt below. If you are planning to use an external MongoDB instead, refer to the requirements for whatever version you intend to use.
- Linux/Unix: format your drives into XFS or EXT4. If possible, use XFS as it generally performs better with MongoDB.
- With the WiredTiger storage engine, use of XFS is strongly recommended to avoid performance issues found when using EXT4 with WiredTiger.
- If using RAID, you may need to configure XFS with your RAID geometry.
- Windows: use the NTFS file system. Do not use any FAT file system (i.e. FAT 16/32/exFAT).
Hardware
For optimal performance, it is strongly recommended that DTP and the Database be installed on different servers. The minimum hardware requirements for each are shown in the tables below. In addition, be aware of the following:
- 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.
- Using SSD will make the biggest difference for performance because DTP is an I/O write/read intensive application.
- DTP server cannot be installed on a machine with an underscore ("_") in its name.
DTP Server
Processor | 64-bit (x86_64) processor with at least eight cores. |
---|---|
Memory | At least 16 GB RAM; at least 24 GB is recommended if installing DTP Enterprise Pack. |
Hard drive | At least 200 GB; SSD is recommended. |
Database Server
Processor | 64-bit (x86_64) processor with at least eight cores. |
---|---|
Memory | At least 16 GB RAM. |
Hard drive | At least 500 GB; SSD is recommended. |
Ports
DTP might not start up properly on some Windows servers due to a port conflict on port 8005. See Reconfiguring DTP Ports for more information about changing port 8005.
Before you begin installation, you should verify that the necessary ports are available:
Default Port | Description |
---|---|
80 (Windows), 8080 (Linux) | DTP Server |
8443 (Windows and Linux) | SSL Connector |
2002 | License Server port for Insure++ |
8005 | Apache Tomcat port |
8082 | Data Collector for Parasoft analysis engines and third-party integrations |
9003 | Used by the HyperSQL database server responsible for session management data |
3306 | Default port used for sending and retrieving MySQL data |
5432 | Default port used for sending and retrieving PostgreSQL data |
1521 | Default port used for sending and retrieving Oracle data |
61617 | JMS events broker |
1883 | MQTT transport connector |
You can customize the DTP Server ports as necessary. See Reconfiguring DTP Ports.
DTP Enterprise Pack Ports
The following ports must be available if you are installing DTP Enterprise Pack:
Default Port | Description |
---|---|
8315 | Event broker in the parent process that orchestrates all of the other processes associated with Enterprise Pack. |
8314 | Extension Designer web interface |
8320-8399 | DTP Enterprise Pack services. |
8316 | Embedded MongoDB database for DTP Enterprise Pack. |
IP Address Formats
IPv4 and IPv6 addresses are supported.
Browsers
The latest versions of the following browsers are supported:
- Microsoft Edge
- Firefox
- Google Chrome
- Safari
Other Requirements
Open File Descriptor Limit
Linux imposes a limit on the number of open file descriptors per process, which 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.
ZIP Extractor
The installation machine must have a program installed that can unzip compressed folders and files.
Microsoft Visual C++ Redistributable
The Microsoft Visual C++ Redistributable package (2015 or higher) is required for the DTP Enterprise Pack database on Windows. The package is very common and may already be installed on your system. If the package is not already installed, the DTP installer will attempt to download the package.