Overview

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).

Terms of Parasoft End User License Agreement

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

Typically, the network license is 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. 

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.


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

  1. Set the jtest.license.use_network property to true.

  2. Set the jtest.license.network.edition.

  3. Ensure that the connection with DTP is configured; see Connecting to DTP.

Retrieving License from Secondary DTP or Standalone License Server

You can configure Jtest to obtain the network license from another instance of DTP or a standalone License Server.

  1. Enable the connection by configuring the following setting:

    - jtest.license.use_network=true


  2. Configure the following settings to use a license from a standalone License Server or from another DTP:

DTP
- license.network.use.specified.server=true
- license.network.auth.enabled=true
- license.network.url=<URL to a DTP server>
- license.network.user=<username for DTP authentication>
- license.network.password=<password for DTP authentication>

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

Connecting via OpenID Connect

If OpenID Connect is enabled for your secondary DTP server or standalone License Server, configure the connection to the OpenID Connect server; see Configuring OpenID Connect.

Local License

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

  1. Set the jtest.license.use_network property to false.

  2. Set the jtest.license.local.password property 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: 

jtestcli -machineID

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.

  • No labels

Need assistance? Visit our support page