Overview

Jtest can run on either a local or a network license. The license type can be configured in the .properties configuration file in INSTALL_DIR (or another location; see Configuration Overview for details).

You must agree to the terms of the Parasoft End User License Agreement (EULA) to use Jtest. The EULA is available in the Jtest installation directory and at https://www.parasoft.com/license. To accept the EULA, enable the following setting in your jtest.properties configuration file:

parasoft.eula.accepted=true

Network License

You can configure Jtest to use a license served from Parasoft DTP or the License Server (either standalone or deployed on another instance of the DTP server).

Network licenses are available in three editions that determine what functionality is available:

desktop_edition: Functionality is optimized for desktop usage.
desktop_compliance_edition: Functionality is optimized for desktop usage and configured to support compliance with coding standards.
server_edition: Functionality is configured for high-performance usage in server command line mode.
server_compliance_edition: Functionality is configured for high-performance usage in server command line mode and includes support for compliance with coding standards.
custom_edition: Functionality can be customized. See jtest.license.custom_edition_features for details.

Configuring a DTP License

The network license can be stored in License Server deployed on the same DTP server that you configured for your development testing workflow (see Connecting to DTP). This is a "floating" or "machine-locked" license that limits usage to a specified number of machines.

To configure a DTP license:

Ensure that the connection with DTP is configured; see Connecting to DTP.
Specify the following settings in the .properties file:
1. Enable the connection by configuring the following setting:jtest.license.use_network property to true.
2. Configure the network edition: jtest.license.network.edition

Retrieving the License from the License Server

You can configure Jtest to obtain the network license from the License Server (either standalone or deployed on another instance of the DTP server). To obtain a license from the License Server, specify the following settings in the .properties file:

Enable the connection by configuring the following setting:
- jtest.license.use_network=true
Configure the network edition: jtest.license.network.edition
Configure the License Server settings:

- license.network.use.specified.server=true
- license.network.url=<URL to the License Server>

If authentication is needed:
- license.network.auth.enabled=true
- license.network.user=<username for authentication>
- license.network.password=<password for authentication>

If OpenID Connect is enabled for the License Server, configure the connection to the OpenID Connect server; see Configuring OpenID Connect.

Local License

Local licenses do not request a license token from a server on the network. Instead, they are locked to a specific machine. You will need to provide your machine ID to your Parasoft representative, who will send you a license password.

Obtaining the Machine ID

Run the following command from the command line to obtain your machine ID:

jtestcli -machineID

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.

Configuring a Local License

To configure a local license, specify the following settings in the .properties file:

Set the jtest.license.use_network property to false.
Set the jtest.license.local.password property with your license password from Parasoft.