In this section:


DTP Enterprise Pack is an installation option when you install DTP. See New DTP Installations for instructions or Upgrading if you are upgrading to the latest version of Enterprise Pack.


See Requirements.

Installation Directory and User Account

You should use the same local user to install enterprise pack with DTP. This is to enable full integration and avoid potential issues in some environments. The user should have a local home directory, not a network shared directory. 

The <DTP_HOME>/dtpservices directory is the installation directory for DTP Enterprise Pack. If you are upgrading from a previous version, your DTP and Enterprise Pack deployment should conform to this directory structure. Installing DTP and DTP Enterprise Pack on different servers or according to a directory structure other than <DTP_HOME>/dtpservices is not supported.

Setting Default Ports for Connected Services

You can specify a default host and port for applications connecting to DTP using the services API. This enables you to redirect users to the appropriate URL if you need to enforce SSL, for example. DTP Enterprise Pack applications, for example, use the services API to communicate with Report Center. 

  1. Open the DTP_HOME/conf/PSTRootConfig.xml configuration file in an editor.
  2. Locate the <default-server-url> element and provide a valid URL:

  3. Save the file.

Enabling SSL

SSL is not enabled in DTP Enterprise Pack by default. You will need to enable SSL if you need to secure the data transported between applications in your infrastructure. If you are using an SSL-enabled reverse proxy server, you do not need to enable SSL for Parasoft applications (see Reverse Proxy Support).

To enable SSL, you must first obtain an authority-signed certificate (CA) from a provider, such as VeriSign, Symantec, or GlobalSign.

Do Not Use a Self-signed Certificate

 Unless you are implementing a reverse proxy infrastructure, only use authority-signed certificates when enabling SSL.

  1. If you have the CA, open the ssl.config.js file in an editor. This file is located in the <DTPSERVICES>/shared directory.
  2. Change the value of the enabled property to true and set the options to use your certificate. See the node.js documentation for a complete list of options. If the certificate was created with a passphrase, then be sure to include it in your configuration.
  3. Save the file.

The same ports are used when SSL is enabled for DTP Enterprise Pack, but they will all use the HTTPS protocol. DTP Enterprise Pack will also use SSL-enabled ports to communicate with DTP. If you want to send data between DTP and Enterprise Pack applications over HTTPS, you must enable SSL for both systems to make sure they work properly.

If you enable SSL for Enterprise Pack, you must also enable SSL for the DTP interface (DTP APIs always run under SSL) so that Report Center and Extension Designer use the same protocol (HTTPS). If you disable SSL and are not using an SSL-enabled reverse proxy server, then passwords and other important information will transmit over the network unencrypted.

  • No labels