Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2021.1

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 Virtualize Server

In this section:

Table of Contents
maxLevel1

...

  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.

...

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

      Code Block
      languagepowershell
      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.:

      Code Block
      languagebash
      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.  

...

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.

...

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