You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

This section describes how to license the desktop instance of SOAtest and Virtualize For information about licensing the web archive (WAR) deployment of the server, see Licensing the Server

In this section:

Network Licenses

You can configure SOAtest and Virtualize to use a license served from Parasoft DTP or a standalone instance of Parasoft License Server. Contact your system administrator for information about which type of license you should use. 

DTP License

You can use a license from DTP or license configuration settings from a DTP Project. Your Parasoft DTP (or Parasoft Concerto) administrators should verify that the product and version you are licensing appears in the DTP License Server. Administrators can refer to to the DTP documentation for information about updating the tools database. Refer to Connecting to DTP for additional information. 

  1. Choose Parasoft> Preferences and click on the DTP category.
  2. Enable the Enable option and specify the DTP host, port, and your DTP login credentials.
  3. (Optional) If DTP is deployed to a location relative to the path specified in the Host name field, specify the relative path in the Context path field. DTP may deployed to a path other than the root of the host if your organization uses a reverse proxy server. 
  4. Click Test Connection to verify that the settings are correct. If you are going to use a license configuration associated with a specific DTP project, choose a project from the drop-down menu in the Project section.  
  5. Click Apply and click the Configure... link in the License section.
  6. If you have multiple Parasoft products installed, open the tab for the Parasoft product you want to license (e.g., Jtest, SOAtest, Virtualize).
  7. Enable the Network option and click the Configure... link.

  8. Enable the Use configured DTP settings option. If you are going to use a license configuration associated with a specific DTP project, enable the Use License Server settings from DTP project to use the license configuration associated with the project selected in step 3. 
  9. Click OK to close the dialog.
  10. Specify the product edition from the Edition drop-down menu. Contact your Parasoft administrator for assistance selecting an edition or custom edition features.
  11. You can enable the Borrow option and specify a length of time for which SOAtest and Virtualize will consume a license token. Licenses can be  borrowed from 1 hour to 14 days. Refer to the DTP documentation for additional information about borrowing licenses.

  12.  Apply to save your settings.

License Server

You can connect to License Server to retrieve a license token, even if you are connected to a separate instance of DTP.

  1. Choose Parasoft> Preferences and click on the License category.
  2. If you have multiple Parasoft products installed, open the tab for the Parasoft product you want to license (e.g., Jtest, SOAtest, Virtualize).
  3. Enable the Network option and click the Configure... link.

  4. Enable the Use the following License Server option and specify the host name or IP address where License Server is hosted and port. Common port numbers are 8443 or 8080  for HTTP/S and 2002 (default) for TCP.

    • If your server uses the HTTPS protocol, prepend https:// to the hostname.

  5. (Optional) Specify the context path if both of the following conditions apply:
    1. You are connecting to the License Server integrated with DTP.
    2. DTP is deployed in a location relative to the host address you provided. DTP may deployed to a path other than the root of the host if your organization uses a reverse proxy server. 
  6. Click Test Connection to verify your settings and click OK to save your changes.
  7. Specify the product edition from the Edition drop-down menu. Contact your Parasoft administrator for assistance selecting an edition or custom edition features.
  8. You can enable the Borrow option and specify a length of time for which SOAtest and Virtualize will consume a license token. Licenses can be  borrowed from 1 hour to 14 days. Refer to the License Server documentation for additional information about borrowing licenses.

  9. Click Apply to save your settings.

Deactivating License

You can deactivate/activate licenses by choosing Parasoft> Deactivate License/Active License

You can also configure the license to automatically deactivate after 30 minutes of inactivity:

  1. Choose Parasoft> Preferences from the main menu and click the License category.
  2. Enable the Start deactivated, release automatically when idle option. 
  3. Click Apply to save your changes.

When the license is deactivated:

  • Parasoft views are disabled and results are cleared from the Quality Tasks view.
  • The license token is released in DTP or License Server.

Licensed views are restored and the Quality Tasks view will display available results when the license is reactivate. 

Waiting for a License in Command Line Mode

You can configure SOAtest and Virtualize  to wait for a license token if a requested token is not currently available by specifying the  license.wait.for.tokens.time option when using the command line interface. For additional information, see 

the following pages:

Stabilizing the Machine ID

Changes in the network environment may affect the interface that is used to compute your machine ID, resulting in machine ID instability. You can use the PARASOFT_SUPPORT_NET_INTERFACES environment variable to specify a stable interface and prevent the machine ID from floating.

  1. Set up the PARASOFT_SUPPORT_NET_INTERFACES environment variable according to your operating system.
  2. Set the variable value to a stable ethernet network interface. Do not use virtual, temporary or loopback interfaces. 
    • Windows: Set the value to the MAC address of your network card, e.g.:

      SET PARASOFT_SUPPORT_NET_INTERFACES=00-10-D9-27-AC-85


    • Linux/macOS: Set the value to one of the network interfaces from the "inet" or "inet6" family, e.g.:

      export PARASOFT_SUPPORT_NET_INTERFACES=eth1

Using a Local License

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

  1. Choose Parasoft> Preferences to and select the License category.
  2. If you have multiple Parasoft products installed, open the tab for the Parasoft product you want to license (e.g., Jtest, SOAtest).
  3. Enable the Local option.
  4. If you have not already done so, note the machine ID in the Machine id field and send it to your Parasoft representative to obtain a license password. You can also run a command using the command line interface to print the machine ID to the console. Without a license, the following message will appear: Error: No valid license (MachineId: WIN32-12345678).
  5. Enter your license password from Parasoft and click Apply. The License preferences page will display the features that you are licensed to use, and the expiration date for your license.
  6. Click OK to set and save your license.


Additional Licensing Considerations for SOAtest Server

If you using the combined SOAtest/Virtualize distribution, a Virtualize license is required to run SOAtest Server. In some instances, you may only have a license for SOAtest, i.e., if you are updating to a paid license from the Community License. Contact your Parasoft representative for additional information about licensing options.

Manually Configuring the License

You can create SOAtest and Virtualize configuration file and specify your license settings. See Configuring Localsettings (SOAtest) and Localsettings (Virtualize) for details on creating and configuring the file.

Importing and Exporting License Configuration Settings

You can export your configuration settings to a .properties file and share with team members. See Configuring Localsettings or Localsettings for details. 

  • No labels