parasoft/dtp repository overview

⁠Quick reference

Maintained by: Parasoft⁠

Where to get help: Parasoft Documentation⁠, Parasoft Forums⁠, or Parasoft Support and Technical Services⁠

⁠What is Parasoft DTP?

Parasoft DTP is a powerful reporting and analytics dashboard designed to centralize and visualize software testing results. It aggregates data from various testing practices across a project, enabling intelligent, continuous monitoring and delivering greater visibility into software development progress and quality. For more information see:

• Parasoft web page⁠.
• Parasoft DTP documentation⁠.
• Parasoft DTP release notes⁠.

⁠How to use this image

⁠Prerequisites

⁠Parasoft DTP data directory

You will need to create a Parasoft DTP data directory for the persistent storage volume so it can be mounted to the container. This directory will contain configuration files, extensions, and other dynamic components that determine how Parasoft DTP runs. Where you create this directory is at your discretion. For example, to create it in the /home/user directory, execute:

mkdir /home/user/dtp_data

This directory will be referred to as DTP_DATA_DIR below.

⁠Database and JDBC Client Jar

Parasoft DTP needs to connect to an external database. Supported databases are MySQL, Oracle, and PostgreSQL. You will need:

• The specific database instance. See versions of the supported databases in the Parasoft DTP documentation⁠. You can use one of the MySQL, Oracle, or PostgreSQL Docker images available on Docker hub.
• The JDBC client jar for your selected database:

Go to DTP_DATA_DIR directory:

cd DTP_DATA_DIR

Create lib/thirdparty directory and download the driver jar file for the database you are going to use. For example, for MySQL:

mkdir -p lib/thirdparty
cd lib/thirdparty
wget https://repo1.maven.org/maven2/mysql/mysql-connector-java/8.0.28/mysql-connector-java-8.0.28.jar

• For PostgreSQL, use https://jdbc.postgresql.org/download/postgresql-42.5.0.jar⁠
• For Oracle, use https://download.oracle.com/otn-pub/otn_software/jdbc/1918/ojdbc8.jar⁠

⁠Start Parasoft DTP instance in Docker

Create a Docker volume called "parasoft-volume":

docker volume create parasoft-volume

Start the Parasoft DTP Docker container. Note: Replace DTP_DATA_DIR below with the real directory path which you have created in the Prerequisites step above.

docker run --name dtp -p 8080:8080 -p 8082:8082 -p 8443:8443 --user root:root -v /var/run/docker.sock:/var/run/docker.sock -v parasoft-volume:/mnt/parasoft -v DTP_DATA_DIR:/usr/local/parasoft/data -d parasoft/dtp

Parameters description:

• /var/run/docker.sock and /mnt/parasoft are required for the machineId to remain the same when new containers are started
• -p 8080:8080 and -p 8443:8443 - exposes ports used to access Parasoft DTP via HTTP and HTTPS
• -p 8082:8082 - exposes the port used to access Parasoft DTP Data Collector
  
  For information about mapping this port to something other than the default value, see Configuring DTP Data Collector in Reverse Proxy Environment⁠. For example, using the settings described there, you would change the Docker port mapping from the default (8082) to another port (e.g., 9082), by setting <dc-reverse-proxy-port> to 9082 and <dc-reverse-proxy-host> to localhost.
• user root:root - required for Docker images deployed on Linux; the root user must be specified so that appropriate permissions can be applied

⁠Configure Parasoft DTP instance

1. Once the Docker container is started, access the Parasoft DTP dashboard on your web browser by going to http://<host>:8080 or https://<host>:8443.
2. Login, accept EULA agreement, etc.
3. Enter a license for Parasoft DTP by following the directions found here in the Parasoft DTP user manual⁠. Note: The license needs to be obtained from a Parasoft representative.
4. You will be redirected to the Database Settings page.

• This step assumes that you have a MySQL, PostgreSQL, or Oracle instance running and available for Parasoft DTP to use.
• Follow the "Preparing the Database via UI" section in the Parasoft DTP user manual⁠.

⁠Restart Parasoft DTP instance

Once the database schema creation process is completed, restart the DTP container:

docker container restart dtp

Parasoft DTP is now ready to use at http://<host>:8080 and https://<host>:8443

⁠Notes

Docker Desktop is not supported. If you run the Parasoft DTP container in Docker Desktop, the Parasoft machineId will be 0.

Docker Swarm–based deployments are not supported.

Upgrading docker may result in the Parasoft machineId changing.

⁠Advanced Options

⁠Parasoft DTP Internal Variables

It is possible to inject the Parasoft DTP environment variables JAVA_CONFIG_ARGS and JAVA_DC_CONFIG_ARGS into the Parasoft DTP docker container. For example:

-e JAVA_CONFIG_ARGS="-Dcom.parasoft.sdm.storage.managers.admin.enable.delete.project.data=true" -e JAVA_DC_CONFIG_ARGS="-Dcom.parasoft.sdm.dc.traffic.max.length=250000"

For more information, see the "Configuring JVM Arguments Using Environment Variables" section in the Parasoft DTP user manual⁠.

⁠Automating the Download of JDBC Driver

It is possible to automate the download of the JDBC Driver at DTP startup time by injecting an environment variable. For example, for MySQL:

-e JDBC_DRIVER_URL=https://repo1.maven.org/maven2/mysql/mysql-connector-java/8.0.28/mysql-connector-java-8.0.28.jar

⁠Creating the Database Schema via Command Line

• See the "Preparing the Database via Command Line" section in the Parasoft DTP user manual⁠.

⁠Overriding Tomcat Configuration

Parasoft DTP runs on Tomcat. Tomcat and its configuration files are embedded in the Docker image. If you need to customize the Tomcat settings or provide your keystore or truststore, here are two ways to do it:

• Use a reverse proxy to configure ports and keystore. This eliminates the need to make changes to the default Tomcat settings and keystore in the container.

• Save your configuration files to a persistent storage directory and mount them when starting the container. The files are located in the following locations in the Parasoft DTP docker container:

  • server.xml - /usr/local/parasoft/dtp/tomcat/conf/server.xml
  • keystore - /usr/local/parasoft/dtp/tomcat/conf/.keystore
  • truststore - /usr/local/parasoft/dtp/jre/lib/security/cacerts

  Save these files to your persistent storage directory and mount them when starting the Parasoft DTP container by adding the following arguments:

  • -v /<persistent_storage>/.keystore:/usr/local/parasoft/dtp/tomcat/conf/.keystore
  • -v /<persistent_storage>/server.xml:/usr/local/parasoft/dtp/tomcat/conf/server.xml
  • -v /<persistent_storage>/cacerts:/usr/local/parasoft/dtp/jre/lib/security/cacerts

⁠License

You need to view and agree to the Parasoft End User License Agreement (EULA)⁠ for the software contained in this image. As with all Docker images, these likely also contain other software which may be under other licenses. As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.