Jtest can run on either a local or a network license. The license type can be configured in the .
properties configuration file in the
INSTALL_DIR (or another location; see Configuration Overview for details).
Typically, the the network license is stored on the same DTP server that you configured for your development testing workflow (see Connecting to DTP). There are two types of the network license:
dtp: This type of license is stored directly in DTP. Your DTP license limits analysis to the number of files specified in your licensing agreement.
ls: This type of license is stored in License Server deployed on your DTP. This is a "floating" or "machine-locked" license that limits usage to a specified number of machines. This is the default type when
license.use_networkis set to
Network licenses are available in three editions that determine what functionality is available:
desktop_edition: Functionality is optimized for desktop usage.
server_edition: Functionality configured for high-performance usage in server command line mode.
custom_edition: Functionality can be customized.
- Ensure that the connection with DTP is configured; see Connecting to DTP.
Advanced Network License Configuration
You can configure Jtest to obtain the network license from another instance of DTP or a standalone License Server.
Enable the connection by configuring the following settings:
Configure the following settings to use a license from a standalone License Server or from another DTP:
license.network.host=<hostname where DTP is deployed>
license.network.port=<port number for your DTP server>– typically, a HTTPS port, for example 443 or 8443
license.network.user=<username for DTP authentication>
license.network.password=<password for DTP authentication>
license.network.host=<hostname where License Server is deployed>– typically, a Tomcat HTTP port, for example 8080
license.network.port=<port number for your License Server>If your server uses the HTTPS protocol, precede the hostname with
To configure the local license, specify the following settings in the
jtest.license.local.passwordproperty with your password.
Obtaining the Machine ID
If you are using a local license, you will need your machine ID to request a password from Parasoft. Run the following command from the command line to obtain your machine ID:
Machine ID for Cloud Environments
If you are using Azure or AWS services, you need to configure the
cloudvm option in the
.properties configuration file to ensure that your machine ID is properly calculated. You can set the option to one of the following values:
azure- Enables integration with Azure
aws- Enables integration with AWS
true- Enables integration with the automatically detected cloud computing platform
false- Disables integration (the default value)
If you set the value to
false or if the option is not configured, integration with Azure or AWS is disabled.