Firefox Executable Path: Specifies the path to the Firefox executable. On Windows machines, SOAtest and/or Virtualize will attempt to detect a Firefox installation automatically. Linux users will have to browse to the Firefox executable.
Chrome Executable Path: Specifies the path to the Chrome executable. Paths set here will be used in web recording wizards and other applicable areas. On Linux, choose google-chrome (e.g. /opt/google/chrome/google-chrome)—not chrome.
Safari Executable Path: Specifies the path to the Safari executable.
Anchor
proxy-port-field
proxy-port-field
Proxy port: Specifies the proxy port. See Proxy Configuration Details below for more information and tips.
Browser communication port: Specifies the browser communication port.
Browser Timeout Settings: Specifies the length of delay (in secondsmilliseconds) after which SOAtest and/or Virtualize should stop waiting for browser startup or a user action and consider it to be "timed out."
Wait Condition Default Timeout Settings: Specifies the length of delay (in seconds) after which SOAtest and/or Virtualize should stop waiting for the activity specified in the wait condition to occur and consider it to be "timed out."
Debug Options> Print debugging information: During recording of a web scenario, it is possible that an action taken is not recorded by SOAtest and/or Virtualize. Enabling this option will allow messages to be printed to the message console during recording, with information about what events SOAtest and/or Virtualize handled, any locators that may have been generated, and if applicable, any exceptions that took place during recording.
Error Reporting> Report website's scripting errors: Configures SOAtest and/or Virtualize to report scripting errors that occur during scenario execution. In Internet Explorer, the Selenium Web-Driver framework will not report JavaScript errors on the page to SOAtest and/or Virtualize; this reporting is supported only for the legacy engine.
Allowable Binary Files in Traffic Viewer and Outputs: Allows binary files with the specified extensions or MIME types to be used in the Traffic Viewer and output. By default, only text files will be allowed.

Proxy Configuration Details

When you record or run web scenarios in a browser, the proxy settings in the browser are set to an internal proxy maintained by SOAtest and/or Virtualize. All communication to and from the browser during recording and playback goes through the internal proxy, which is an intermediary used to capture traffic and otherwise facilitate execution. During recording and playback, SOAtest and/or Virtualize temporarily creates this proxy on localhost using the port specified by the Browser Playback setting’s Proxy port option.

The default host and port for the internal proxy is localhost:55555. Change the port number if this port is already in use using the controls Proxy port field. Do not change this from within the browser.

If your machine is configured to use your own proxy, you should configure SOAtest and/or Virtualize to point to that proxy. This enables SOAtest and/or Virtualize to configure its internal proxy to forward all traffic to the specified proxy configured in Proxy Settings.

Console Settings

The Console panel allows you to determine the amount of information that is reported to the Console view and whether it is automatically activated when it contains messages.

...

Browser Contents Viewer Rendering Engine: Enables you to specify what browser is used for the Browsear Contents Viewer tool(described in Browser Contents Viewer) , which can be attached to the Browser Playback tool.
- The default option (Same browser used for playback) is generally the recommended option because some web applications generate their pages differently based on the browser used. Using the same browser that was used during the playback can help ensure that pages display properly in the Browser Contents Viewer. Note that if the playback browser was Chrome, the Firefox rendering engine is used.
- When Internet Explorer is selected, the version of IE that is used depends on what version of IE is installed on the machine running SOAtest and/or Virtualize. The Internet Explorer option is available only on Windows.
- When Firefox is selected, the version of Firefox that is used depends on what Eclipse is being used to run SOAtest and/or Virtualize. It can range from Firefox 3.0.1 to Firefox 10, depending on what OS is being used.
- If the particular web application being tested does not render properly in the Browser Contents Viewer, you could try configuring this option to use either Internet Explorer or Firefox specifically (rather than use the default Same browser used for playback option) to see if using a specific rendering engine will improve how the page is shown in the Browser Contents Viewer.
HTML Content Fetch Mode: Enables you to determine whether the contents of hidden frames are displayed in the pre- and post-action HTML viewer. This can impact record and playback speed, as well as file size. It is possible to use one mode on some of your team’s SOAtest and/or Virtualize machines (e.g., desktop installation), and a different mode on others (e.g, the Server machine running in command-line mode).
- Fetch all HTML content Choose this option if you want to see the contents of hidden frames in the pre- and post-action HTML viewer (in the Browser Playback tool, Browser Contents Viewer, Browser Data Bank, and Browser Validation tool). This is desirable if you want to create validations/extractions in hidden iframes. This mode will significantly slow down recording and playback. Moreover, it will significantly increase .tst file size if your application uses hidden iframes.
- Fetch content for all content except hidden frames: Choose this option if you do not need to see the contents of hidden frames in the pre- and post-action HTML viewer.(in the Browser Playback tool, Browser Contents Viewer, Browser Data Bank, and Browser Validation tool). In this mode, the browser will still retrieve all frames from the server and it can still perform validations and extractions on the hidden iframes. However, it will not display the contents of hidden frames in the pre- and post-action HTML viewer.

Proxy Configuration Details

When you record or run web scenarios in a browser, the proxy settings in the browser are set to an internal proxy maintained by SOAtest and/or Virtualize. All communication to and from the browser during recording and playback goes through the internal proxy, which is an intermediary used to capture traffic and otherwise facilitate execution. During recording and playback, SOAtest and/or Virtualize temporarily creates this proxy on localhost using the port specified by the Browser Playback setting’s Proxy port option.

The default host and port for the internal proxy is localhost:55555. Change the port number if this port is already in use using the controls Proxy port field. Do not change this from within the browser.

If your machine is configured to use your own proxy, you should configure SOAtest and/or Virtualize to point to that proxy. This enables SOAtest and/or Virtualize to configure its internal proxy to forward all traffic to the specified proxy configured in Proxy Settings.

Internet Explorer Notes

SOAtest and Virtualize modify the global registry settings prior to starting its instance of the browser. If an instance of Internet Explorer was running on the machine prior to launching SOAtest or Virtualize (not recommended), the global registry settings will not be set in the existing browser instance.

In these cases, check the Internet Options panel in the existing browser instance while a web scenario is running to verify that the settings point to SOAtest’s or Virtualize's proxy and click OK in the Internet Options panel. If you click OK, the proxy settings are updated in the existing browser instance. If you click Cancel, or do not go to the Internet Options panel, then the existing browser instance never picks up the proxy settings and should continue to navigate fine.

Proxy settings may not be reset properly if the browser exited abnormally, if there is a hanging browser process, etc. Such issues can affect new browser instances (or other programs that connect to the internet). If this happens, you can resolve it by resetting your machine’s proxy settings to the appropriate settings or killing any hanging browser processes.

Console Settings

The Console panel allows you to determine the amount of information that is reported to the Console view and whether it is automatically activated when it contains messages.

Continuous Testing Platform Settings
Anchor
CTP Settings
CTP Settings

If you have Continuous Testing Platform (CTP) and a valid license, you can configure your connection to CTP:

Use DTP settings: Enable this option to use the connections settings specified in DTP. See Connecting to DTP.
Server Name: Specifies a name for the server you are connecting to CTP. This is the name that will be used to identify this server within CTP.
CTP URL: Specifies the location of the CTP to which you are connecting (e.g., http://emdemo:8080).
Notify CTP of virtual asset deployment: Determines whether the server notifies Parasoft CTP when virtual assets are first deployed.
Username: Specifies the username for logging into CTP.
Password: Specifies the password for logging into CTP.

Global Data Source Settings

Global data sources can be reused and shared outside of a single SOAtest project and across Virtualize deployments. The Global Data Source panel lets you determine how information about global data sources is saved. For information on how to configure global data sources, see Adding a Data Source at the Responder Suite, Project, or Global Level and Adding a Data Source at the Test Suite, Project, or Global Level.

Technical Support Settings

Use the Technical Support interface to create a zip archive containing the related files if you are experiencing issues. Send the zip file to

...

If you have Continuous Testing Platform (CTP) and a valid license, you can configure your connection to CTP:

Use DTP settings: Enable this option to use the connections settings specified in DTP. See Connecting to DTP.
Server Name: Specifies a name for the server you are connecting to CTP. This is the name that will be used to identify this server within CTP.
CTP URL: Specifies the location of the CTP to which you are connecting (e.g., http://emdemo:8080).
Notify CTP of virtual asset deployment: Determines whether the server notifies Parasoft CTP when virtual assets are first deployed.
Username: Specifies the username for logging into CTP.

Password: Specifies the password for logging into CTP.

Note
If OpenID Connect authentication is enabled, the Username and Password fields do not appear. Instead, you will see a notice that OIDC authentication is in use with a button to test that connection.

Global Data Source Settings

Global data sources can be reused and shared outside of a single SOAtest project and across Virtualize deployments. The Global Data Source panel lets you determine how information about global data sources is saved. For information on how to configure global data sources, see Adding a Data Source at the Responder Suite, Project, or Global Level and Adding a Data Source at the Test Suite, Project, or Global Level.

Technical Support Settings

Use the Technical Support interface to create a zip archive containing the related files if you are experiencing issues. Send the zip file to Parasoft's support team so that they can assist you.SOAtest/Virtualize can automatically create an archive when problems occur. Archives are approximately half a megabyte and are created in about 60 seconds.

...

By default, SOAtest treats non-text characters as white space and does not allow you to add dictionary words that contain non-text characters. If you want SOAtest to consider a designated non-text character as a valid character within a word (rather than as one unit of white space), you need to add that character to the list of allowable non-text characters. This allows you to identify spelling errors in words that contain allowed non-text characters as white space and does not allow you to add dictionary words that contain allowed non-text characters.To add non-text characters to the list of allowable non-text characters:

...

. If you want SOAtest to

...

consider a designated non-text

...

MIME Type Settings

The MIME Types panel lets you add and remove MIME types. In addition, it lets you specify the location of your preferred text and XML editors and lets you specify what editor you want to use to edit all files that have a particular MIME type.

To add, edit, or remove a MIME type:

To add a MIME type, click Add MIME Type, enter the new MIME type in the dialog box that opens, then enter the file extensions that you want to assign to this MIME type, and (optionally) indicate the implied MIME type by checking the appropriate check boxes. If you enter multiple extensions for a MIME type, separate the extensions with one space character.
To edit a MIME type’s settings, select the MIME type whose settings you want to edit, then modify the settings as needed.
To remove a MIME type, select the MIME type that you want to remove, then click Delete MIME Type.

...

The Misc panel allows you to set the following miscellaneous settings:

...

Auto Beautify: Tells SOAtest to automatically beautify XML messages in the selected tool or tools (Traffic Viewer, Diff, Editor) if the message is under the specified size (10 KB is the default setting).

Character Encoding: You can enable System default to configure SOAtest and/or Virtualize to use the default character set for the particular system being used. Enable Custom to encode characters from the list of encodings available on the JVM being used.
Save settings: Specifies what file format to use for saving project files (e.g., .pva, .pvn, .tst, .changetemplate). See Understanding the Available Project File Formats.

Default timeout (milliseconds): Allows you to enter the length of delay (in milliseconds) after which SOAtest should consider your FTP, telnet, or HTTP requests to be “timed out.” The default is 30000 milliseconds.
Report each duplicate error that occurs on the same line: Tells SOAtest to show only the first instance of duplicate errors that occur for the same line of code.
Reset Cookies: Allows you to clear the current global cookies so that next HTTP invocations start a new session.
Enable the Automatically backup project files option and specify a file size threshold for .tst and/or .pva files in the Warn on file size large than (MB) field to be notified when the size of the file exceeds the threshold. You can then reduce the size (and prevent performance problems) by dividing it into smaller files.

...

The OpenID Connect panels allows you to configure the application to authenticate users via your OpenID Connect server.

Go to Parasoft > Preferences and select OpenID Connect.
Image Removed
Check Enable.
Configure the following options:
- Issuer URI: The URI of your OpenID Connect server.
- Client ID: The ID registered on your OpenID Connect server.
- Callback host: The local callback host required to communicate with the OpenID Connect server. The following options are available:
  - localhost: The localhost address will be used for communication.
  - 127.0.0.1: The loopback IP address 127.0.0.1 will be used for communication.
- Callback port: The callback port number for communication with the OpenID Connect server. The following options are available:
  - Automatically select an open port: Automatically selects an open port (recommended).
  - Use port: Allows you to manually specify the port number.
- Callback timeout: Specifies, in seconds, the maximum time the browser will wait for user credentials.
Click Test Authentication or Apply to open the OpenID Connect authentication page in your browser.
Provide your credentials in the browser window that opens.
Close the browser window when the authentication confirmation appears and continue in the application.
Click Apply to apply the changes.

The Status panel shows the current OpenID Connect authentication status.

...

character as a valid character within a word (rather than as one unit of white space), you need to add that character to the list of allowable non-text characters. This allows you to identify spelling errors in words that contain allowed non-text characters and to add dictionary words that contain allowed non-text characters.

To add non-text characters to the list of allowable non-text characters:

Enter them in the Allowable non-text characters field. If you want to allow multiple non-text characters, list them one after the other—do not separate them with a space character, comma, or other delimiter.

MIME Type Settings

The MIME Types panel lets you add and remove MIME types. In addition, it lets you specify the location of your preferred text and XML editors and lets you specify what editor you want to use to edit all files that have a particular MIME type.

To add, edit, or remove a MIME type:

To add a MIME type, click Add MIME Type, enter the new MIME type in the dialog box that opens, then enter the file extensions that you want to assign to this MIME type, and (optionally) indicate the implied MIME type by checking the appropriate check boxes. If you enter multiple extensions for a MIME type, separate the extensions with one space character.
To edit a MIME type’s settings, select the MIME type whose settings you want to edit, then modify the settings as needed.
To remove a MIME type, select the MIME type that you want to remove, then click Delete MIME Type.

Miscellaneous Settings

The Misc panel allows you to set the following miscellaneous settings:

Show tool descriptions: Enables/disables showing tool descriptions in applicable wizards.
Auto Beautify: Tells SOAtest to automatically beautify XML messages in the selected tool or tools (Traffic Viewer, Diff, Editor) if the message is under the specified size (10 KB is the default setting).

Character Encoding: You can enable System default to configure SOAtest and/or Virtualize to use the default character set for the particular system being used. Enable Custom to encode characters from the list of encodings available on the JVM being used.
Save settings: Specifies what file format to use for saving project files (e.g., .pva, .pvn, .tst, .changetemplate). See Understanding the Available Project File Formats.

Default timeout (milliseconds): Allows you to enter the length of delay (in milliseconds) after which SOAtest should consider your FTP, telnet, or HTTP requests to be “timed out.” The default is 30000 milliseconds.
Report each duplicate error that occurs on the same line: Tells SOAtest to show only the first instance of duplicate errors that occur for the same line of code.
Reset Cookies: Allows you to clear the current global cookies so that next HTTP invocations start a new session.
Enable the Automatically backup project files option and specify a file size threshold for .tst and/or .pva files in the Warn on file size large than (MB) field to be notified when the size of the file exceeds the threshold. You can then reduce the size (and prevent performance problems) by dividing it into smaller files

...

.

Proxy Settings

The Proxy panel controls how SOAtest and/or Virtualize works with proxy servers. It does not control the separate intermediary proxy used for web scenarios (for details on this other proxy, seeProxy Configuration Details).

...

The Scripting panel allows you to specify properties used for custom scripts.

- Java: For Java, you can specify the Java home directory and the path to the javac compiler. You need to specify these parameters if you want to compile Java methods in the editor.
  Note
  title Note
  The javac compiler is not included.
  - Java home: Specifies the Java installation directory.
  - Javac classpath: Specifies the Java classpath.
- JavaScript: If you create scripts using Jython or JavaScript, you can specify a script template in the Script Template field.
  Script Template: Whatever code is specified in this field will be used as the default code for inlined scripting in the language with which the field is associated. This is

primarily
prmarily useful for setting default inputs and common global variables. Script templates apply to scripts used in Extension tools; they do not apply to JavaScript that runs in a browser context.
Jython:
If you are using Jython scripts, you can specify the Jython Path variable. Jython scripting support can be used without setting this variable by specifying a script template in the Script Template field.
Jython Path: Specifies a list of directories to search for python modules that are not already included with Jython. Separate multiple directory paths using the OS default path separator (";" for Windows and ":" for Linux and macOS). If you set the Jython path then you need to restart SOAtest or Virtualize for the change to take effect.
For Jython, you can specify the jython.home and jython.path variables. Both variables are used to locate Jython modules. Jython code that does not import any Jython modules can use the Jython scripting support without setting either variable. If you set the jython.home and jython.path variables, you need to restart SOAtest or Virtualize before the changes will take effect.
Jython Home: Specifies the Jython installation directory. This must be a single directory. Use a forward slash (/) or backslash (\) to escape special characters.
Jython Path: Used to add to your path modules that are not in your jython.home/Lib directory. Multiple paths can be listed. Use a forward slash (/) or backslash (\) to escape special characters.
Script Template:Jy thon code that does not import any Jython modules can use the Jython scripting support without setting either the jython.home or jython.path
Script Template: Code specified in this field sets a default template for Jython scripts used in the tool
.
Timeout Settings: Specify how many minutes SOAtest or Virtualize should wait before attempting to stop an unresponsive script and log an error message.

Security Settings

You can configure default security settings for clients and Responders used in your projects. In most cases, the security settings can be overridden by configurations set locally in your suites:

...

Configure global HTTP authentication properties that can be used when configuring HTTP protocols within an applicable tool.

Enable Enables the Perform Authentication option and enter the Username and Password to authenticate the request
Choose the authentication type from the drop-down menu. Supported types are Basic, NTLM, Kerberos, or Digest.
If you are using Kerberos authentication, enter the Service Principal to authenticate the request. If the correct username and password, or the correct service principal, are not used, the request will not be authenticated.
Kerberos realm: Specify the Kerberos realm associated with your network. By convention, this is typically your domain name in all caps (e.g. PARASOFT.COM).
KDC server: Specify the hostname of your Key Distribution Center (e.g. kdc.parasoft.com).
Check Ticket: This will execute a simple test to locate a cached Kerberos TGT (Ticket Granting Ticket) to grant access to the service. SOAtest and/or Virtualize will not be able to communicate with the service if it cannot first locate a valid TGT. For more information about Kerberos, see Configuring Kerberos Authentication.

...

Info

icon	false
title	Avoiding Common Kerberos Errors

For tips on common Kerberos errors and how to solve them, see http://docs.oracle.com/javase/8/docs/technotes/guides/security/jgss/tutorials/Troubleshooting.html.

...

Configuring Kerberos Authentication for Tools

Select the tool for which you intend to use Kerberos authentication.
Select the Transport tab and select Security from the left pane of the Transport tab.
Configure the following options from the security panel of the Transport tab:
Perform Authentication: Select this option to activate authentication.
Use Global Preferences: Select this option if you have authentication properties setup in Security Preferences.
Type: Select Kerberos to perform Kerberos Authentication.
Service Principal: Specify the name of the service/server as defined in the Kerberos database (e.g. HTTP/soatest.parasoft.com).

...

Click the Add button beneath the OASIS XML Catalog Locations section of the Schema Locations tab. The Location dialog box displays.
Type in the OASIS XML Catalog Location or Browse to it by clicking the Browse button.
Click OK after you have added all of the necessary locations.

Anchor
Localsettings
Localsettings
Virtualize

...

Localsettings

There are two ways to define settings localsettings files:

Enter them manually in a simple text file simple text file. There are no name or location requirements. Each local setting should be entered in a single line.
Export your GUI preferences, then adjust or extend them as needed. To export, choose Parasoft> Preferences, select Parasoft (the root element in the left tree), click the Share link, specify which settings you want to export.

Settings Localsettings files can specify the following settings.

Licensing Settings

...

the following settings.

Licensing Settings

...

Setting Purpose
`virtualize.license.use_network=true|false` Determines whether the current installation retrieves its license from License ServerLicenseServer.
`virtualize.license.network.host=[host]`
Specifies the machine name or IP address of the machine running License Server LicenseServer Configuration Manager. If your server uses the HTTPS protocol, prepend `https://` to the hostname.
Example:
`virtualize.license.network.`This setting is deprecated`host=10.9.1.63`
`virtualize.license.network.host=https://10.9.1.63`
`virtualize.license.network.port=[port]`
Specifies the License Server LicenseServer port number.
Example:
`virtualize.license.network.port=2222`This setting is deprecated
`virtualize.license.network.user=[username]`
Specifies the username for authentication on the secondary DTP server specified with the `license.network.url` option`host` and `license.network.port` options.
This options requires the `license.network.use.specified.server` and `license.network.auth.enabled` options to be set to `true`.
Example: `license.network.user`=JohnDoe
`virtualize.license.network.password=[password]`
Specifies the password for authentication on the secondary DTP server specified with the `license.network.host`and `license.network.url` option`port` options.
This option requires the `license.network.use.specified.server` and `license.network.auth.enabled` options to be set to `true` and the the `license.network.user` to be configured.
We strongly recommend encoding your password to ensure successful authentication and a secure connection. You can encode your password by running `virtualizecli` with the `-encodepass` flag.
Example:
`virtualizecli -encodepass mypassword`
The command line tool will generate an encoded string that you can use in the configuration file.
`license.network.url=[url]`
Specifies the License Server URL. Include the protocol and host name or IP address and, if appropriate, the port number and context path.
Example: `https://10.9.1.63:8443`
`license.network.context.path=[path]`
Specifies the path to the DTP License Server. The context path is a relative path from the host name specified with the `license.network.host` setting. This setting should only be configured if DTP is deployed to a location other than the root of the host server, which may be the case if your organization uses a reverse proxy.
Configuring the context path is not supported for standalone License Server.
Refer to the DTP documentation for additional information about reverse proxy server configuration and context path configuration.
This setting is deprecated.
`license.network.auth.enabled=true|false`
Enables or disables authentication on the secondary DTP server specified with the `license.network.url` option`host` and `license.network.port` options.
This option requires the `license.network.use.specified.server` option to be set to `true`.
`license.network.use.specified.server=[true|false]`
This option enables Virtualize to connect to either DTP and License Server, or two instances of DTP simultaneously.
Set to `false` if you want to retrieve a license from the DTP server specified with Parasoft DTP Settings.
If set to `true`, Set to `true` and specify a license network connection type with the `license.network.connection.type` setting. Virtualize will retrieve a license from the server specified with the `license.network.host and license.network.url` option`port` settings.
`virtualize.license.network.edition=[edition_name]`
Specifies the type of license that you want this installation to retrieve from LicenseServer.
`[edition_name]` can be `server_edition`. To use a custom edition, do not set anything after the "="; simply leaving the value empty.
Example:
`virtualize.license.network.edition=desktop_edition`
`virtualize.license.network.edition=server_edition`
`virtualize.license.autoconf.timeout=[seconds]` Specifies the maximum number of seconds this installation will wait for the license to be automatically configured from LicenseServer. Default is 10.
`virtualize.license.`
`local.expiration=[expiration]` Specifies the local license that you want this installation to use.
`virtualize.license.local.password=[password]` Specifies the local password that you want this installation to use.
`virtualize.license.wait.for.tokens.time=[time in minutes]`
Specifies the time that this installation will wait for a license if a license is not currently available.
For example, use `virtualize.license.wait.for.tokens.time=3` to configure Virtualize to wait three minutes for a license token to become available.
...
Setting Purpose
`server.startup` Determines whether the server is automatically started upon Virtualize startup.
`server.port.http` Specifies the port that the Virtualize Server uses for HTTP.
`server.port.https` Specifies the port that the Virtualize Server uses for HTTPS.
`server.port.monitoring` Specifies the port that the Virtualize Server uses for monitoring.
`system.properties.class-`
`path=[path1];[path2];[path3] ...`
Specifies which jar files and class folders are in the classpath.
For example: `system.properties.classpath=C\:\\myjars\\myLib1.jar;C\:\\myjar s\\myLib2.jar`
`scripting.timeout.minutes` Specifies the number of minutes after which Virtualize will attempt to stop an unresponsive script and log an error message.
`scripting.jython.home` Specifies the Jython installation directory. This must be a single directory.
`scripting.jython.path` Used to add a list of directories to search for python to your path modules that are not already included with Jythonin your jython.home/Lib directory. Multiple paths can be listedusing the OS default path separator (";" for Windows and ":" for Linux and macOS).
`parasoft.event.monitoring.broker.port` Specifies the port number for the event monitor. Add this setting to the JVM arguments. If you don't set this property, port 9617 is used by default. If the default number is being used by another application, the even monitor will scan for open ports incrementally starting with the default.
`parasoft.server.statistics.broker.port` Specifies the port number for the server statistics collector. Add this setting to the JVM arguments. If you don't set this property, port 9618 is used by default. If the default number is being used by another application, the statistics broker will scan for open ports incrementally starting with the default.
`parasoft.mq.environment.ccsid` Specifies a CCSID to connect ot he MQ queue manager. Contact your MQ administrator for additional information.
`datasources.jdbc.classpath=[path1];[path2];[path3] ...`
Specifies the location of JDBC driver jar files and class folders.
Special characters (spaces, slashes, colons, etc.) must be escaped; for instance:
%20 = SPACE
%3A = :
%5C = \
%7B = {
%7D = }
%24 = $
If listing multiple jars, use \n as a delimiter.
For example,
`C:\temp\with`
`space\${example}\jar.jar`
becomes
`C%3A%5Ctemp%5Cwith%20space%5C$2 4%7Bexample%7D%5Cjar.jar\n`
`traffic.wizard.xpath.ignores`
Lets you globally indicate that you want certain values (such as times-tamps) ignored whenever:
you are creating parameterized .pvas from traffic, and
request requiest body correlations are configured automatically.
Exclusions are specified in the format
`traffic.wizard.xpath.ignores=[element name 1]:[value pattern 1];[element name 2]:[value pattern 2];[element name 3]:[value pattern 3]`
For example:
`traffic.wizard.xpath.ignores=:[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0- 9]{2}:[0-9]{2}([.][0-9]{1,3})?(([+-][0-9]{2}:[0- 9]{2})|Z)?;uuid:[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}`
Note that when the backslash character (\) is used in the regular expression, it needs to be escaped. For example, the regex [\d], which represents a single digit, would be entered as [\\d].
...
Setting Purpose
`env.manager.server`
Specifies the location of the CTP server. Required*
Example: env.manager.server=http://em_hostname:8080/
`env.manager.server.name`
Specifies the name that will be used to label this server on CTP.You can use whatever value will help you identify this server. Optional
Example: env.manager.server.name=MyVirtServerLabel
`env.manager.notify`
Determines whether the Virtualize server notifies Parasoft CTP when virtual assets are deployed. Optional
Example: env.manager.notify=true
`env.manager.username`
Specifies the username for logging into CTP. Optional
Example: env.manager.username=me
`env.manager.password`
Specifies the password for logging into CTP. Optional
Example: env.manager.password=12345

Miscellaneous Settings

...

Setting Purpose
`dtp.autoconfig=true|false`
Enables autoconfiguration with Parasoft Test settings stored on the DTP server.
Default: `false`
`dtp.enabled=true|false`
Determines whether the current Parasoft Test product is connected to DTP.
Default: `false`
`dtp.url=[url]` Specifies the URL of the
DTP
server. Include protocol and host name or IP address and, as appropriate, port and context path.
.
Default: `false`
`dtp.server=[host]` Specifies the host name of the DTP server. This setting is deprecated.
`dtp.port=[port]` Specifies the DTP server port. This setting is deprecated.
`console.verbosity.level=low|normal|high`
Specifies the verbosity level for the Console view. Available settings are:
`low`: Configures the Console view to show errors and basic information about the current step’s name and status (done, failed, up-to-date).
`normal`: Also shows command lines and issues reported during test and analysis.
`high`: Also shows warnings.
`parallel.mode=Manual|Auto|Disabled`
Determines which of the following modes is active:
Auto: Allows the product to control parallel processing settings.
Manual: Allows you to manually configure parallel processing settings to suit your specific needs.
Disabled: Configures the product to use only one of the available CPUs.
`parallel.max_threads=<number>`
Specifies the maximum number of parallel threads that can be executed simultaneously. The actual number of parallel threads is determined based on the number of CPUs, available memory, and license settings.
`parallel.free_memory_limit=<percentage>` Specifies the amount of memory that should be kept free in low memory conditions (expressed as a percentage of the total memory available for the application). This is used to ensure that free memory is available for other processes.
`parallel.no_memory_limit=true|false` Indicates that you do not want to place any restrictions (beyond existing system limitations) on the memory available to the product.
`tasks.clear=true|false` Clears existing tasks upon startup in cli mode. This prevents excessive time being spent "loading existing results." The default is true.
`security.trust.all.certificates=true|false` Tells Virtualize that you want it to accept any certificate. This is useful if you want to load pages whose certificates are not "trusted."
`security.use.default.java.cacerts=true|false` Tells Virtualize that you want it to accept only certificates from the standard list of Java trusted certificate vendors.

Manually Adding the License to

...

localsetttings

To add or change license settings via settingsvialocalsettings:

If you will be using a custom edition license, define the appropriate license features in the settings localsettings as follows:
[product].license.custom_edition_features= All enabled features
Note that license feature settings apply only to custom edition licenses.

Define the main license settings in the settings localsettings as follows:

Code Block
virtualize.license.network.edition=[ Type of license edition] virtualize.license.use_network=[ Value (true or false)] license.network.host= Host name license.network.url=[URL]port= Port number

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

Here are several examples of properly-configured license settings in settings localsettings file:

Virtualize network license - desktop edition

Code Block
virtualize.license.network.edition=desktop_edition virtualize.license.use_network=true license.network.urlhost=http://main1.parasoft.com.pl: license.network.port=2222

Virtualize network license -custom edition with various features

Code Block

virtualize.license.custom_edition_features=Virtualize, Server, Message Packs, Unlimited Million Hits / Day
virtualize.license.network.edition=custom_edition
virtualize.license.use_network=true
license.network.urlhost=http://main1.parasoft.com.pl:
license.network.port=2222

Virtualize network license -custom edition with various features

...

Setting	Purpose
`virtualize.license.use_network=true\|false`	Determines whether the current installation retrieves its license from License ServerLicenseServer.
`virtualize.license.network.host=[host]`	Specifies the machine name or IP address of the machine running License Server LicenseServer Configuration Manager. If your server uses the HTTPS protocol, prepend `https://` to the hostname. Example: `virtualize.license.network.`This setting is deprecated`host=10.9.1.63` `virtualize.license.network.host=https://10.9.1.63`
`virtualize.license.network.port=[port]`	Specifies the License Server LicenseServer port number. Example: `virtualize.license.network.port=2222`This setting is deprecated
`virtualize.license.network.user=[username]`	Specifies the username for authentication on the secondary DTP server specified with the `license.network.url` option`host` and `license.network.port` options. This options requires the `license.network.use.specified.server` and `license.network.auth.enabled` options to be set to `true`. Example: `license.network.user`=JohnDoe
`virtualize.license.network.password=[password]`	Specifies the password for authentication on the secondary DTP server specified with the `license.network.host`and `license.network.url` option`port` options. This option requires the `license.network.use.specified.server` and `license.network.auth.enabled` options to be set to `true` and the the `license.network.user` to be configured. We strongly recommend encoding your password to ensure successful authentication and a secure connection. You can encode your password by running `virtualizecli` with the `-encodepass` flag. Example: `virtualizecli -encodepass mypassword` The command line tool will generate an encoded string that you can use in the configuration file.	`license.network.url=[url]`	Specifies the License Server URL. Include the protocol and host name or IP address and, if appropriate, the port number and context path. Example: `https://10.9.1.63:8443`
`license.network.context.path=[path]`	Specifies the path to the DTP License Server. The context path is a relative path from the host name specified with the `license.network.host` setting. This setting should only be configured if DTP is deployed to a location other than the root of the host server, which may be the case if your organization uses a reverse proxy. Configuring the context path is not supported for standalone License Server. Refer to the DTP documentation for additional information about reverse proxy server configuration and context path configuration. This setting is deprecated.
`license.network.auth.enabled=true\|false`	Enables or disables authentication on the secondary DTP server specified with the `license.network.url` option`host` and `license.network.port` options. This option requires the `license.network.use.specified.server` option to be set to `true`.
`license.network.use.specified.server=[true\|false]`	This option enables Virtualize to connect to either DTP and License Server, or two instances of DTP simultaneously. Set to `false` if you want to retrieve a license from the DTP server specified with Parasoft DTP Settings. If set to `true`, Set to `true` and specify a license network connection type with the `license.network.connection.type` setting. Virtualize will retrieve a license from the server specified with the `license.network.host and license.network.url` option`port` settings.
`virtualize.license.network.edition=[edition_name]`	Specifies the type of license that you want this installation to retrieve from LicenseServer. `[edition_name]` can be `server_edition`. To use a custom edition, do not set anything after the "="; simply leaving the value empty. Example: `virtualize.license.network.edition=desktop_edition` `virtualize.license.network.edition=server_edition`
`virtualize.license.autoconf.timeout=[seconds]`	Specifies the maximum number of seconds this installation will wait for the license to be automatically configured from LicenseServer. Default is 10.
`virtualize.license.` `local.expiration=[expiration]`	Specifies the local license that you want this installation to use.
`virtualize.license.local.password=[password]`	Specifies the local password that you want this installation to use.
`virtualize.license.wait.for.tokens.time=[time in minutes]`	Specifies the time that this installation will wait for a license if a license is not currently available. For example, use `virtualize.license.wait.for.tokens.time=3` to configure Virtualize to wait three minutes for a license token to become available.

Setting	Purpose
`server.startup`	Determines whether the server is automatically started upon Virtualize startup.
`server.port.http`	Specifies the port that the Virtualize Server uses for HTTP.
`server.port.https`	Specifies the port that the Virtualize Server uses for HTTPS.
`server.port.monitoring`	Specifies the port that the Virtualize Server uses for monitoring.
`system.properties.class-` `path=[path1];[path2];[path3] ...`	Specifies which jar files and class folders are in the classpath. For example: `system.properties.classpath=C\:\\myjars\\myLib1.jar;C\:\\myjar s\\myLib2.jar`
`scripting.timeout.minutes`	Specifies the number of minutes after which Virtualize will attempt to stop an unresponsive script and log an error message.
`scripting.jython.home`	Specifies the Jython installation directory. This must be a single directory.
`scripting.jython.path`	Used to add a list of directories to search for python to your path modules that are not already included with Jythonin your jython.home/Lib directory. Multiple paths can be listedusing the OS default path separator (";" for Windows and ":" for Linux and macOS).
`parasoft.event.monitoring.broker.port`	Specifies the port number for the event monitor. Add this setting to the JVM arguments. If you don't set this property, port 9617 is used by default. If the default number is being used by another application, the even monitor will scan for open ports incrementally starting with the default.
`parasoft.server.statistics.broker.port`	Specifies the port number for the server statistics collector. Add this setting to the JVM arguments. If you don't set this property, port 9618 is used by default. If the default number is being used by another application, the statistics broker will scan for open ports incrementally starting with the default.
`parasoft.mq.environment.ccsid`	Specifies a CCSID to connect ot he MQ queue manager. Contact your MQ administrator for additional information.
`datasources.jdbc.classpath=[path1];[path2];[path3] ...`	Specifies the location of JDBC driver jar files and class folders. Special characters (spaces, slashes, colons, etc.) must be escaped; for instance: %20 = SPACE %3A = : %5C = \ %7B = { %7D = } %24 = $ If listing multiple jars, use \n as a delimiter. For example, `C:\temp\with` `space\${example}\jar.jar` becomes `C%3A%5Ctemp%5Cwith%20space%5C$2 4%7Bexample%7D%5Cjar.jar\n`
`traffic.wizard.xpath.ignores`	Lets you globally indicate that you want certain values (such as times-tamps) ignored whenever: you are creating parameterized .pvas from traffic, and request requiest body correlations are configured automatically. Exclusions are specified in the format `traffic.wizard.xpath.ignores=[element name 1]:[value pattern 1];[element name 2]:[value pattern 2];[element name 3]:[value pattern 3]` For example: `traffic.wizard.xpath.ignores=*:[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0- 9]{2}:[0-9]{2}([.][0-9]{1,3})?(([+-][0-9]{2}:[0- 9]{2})\|Z)?;uuid:[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}` Note that when the backslash character (\) is used in the regular expression, it needs to be escaped. For example, the regex [\d], which represents a single digit, would be entered as [\\d].

Setting	Purpose
`env.manager.server`	Specifies the location of the CTP server. Required Example: env.manager.server=http://em_hostname:8080/
`env.manager.server.name`	Specifies the name that will be used to label this server on CTP.You can use whatever value will help you identify this server. Optional Example: env.manager.server.name=MyVirtServerLabel
`env.manager.notify`	Determines whether the Virtualize server notifies Parasoft CTP when virtual assets are deployed. Optional Example: env.manager.notify=true
`env.manager.username`	Specifies the username for logging into CTP. Optional Example: env.manager.username=me
`env.manager.password`	Specifies the password for logging into CTP. Optional Example: env.manager.password=12345

Setting	Purpose
`dtp.autoconfig=true\|false`	Enables autoconfiguration with Parasoft Test settings stored on the DTP server. Default: `false`
`dtp.enabled=true\|false`	Determines whether the current Parasoft Test product is connected to DTP. Default: `false`	`dtp.url=[url]`	Specifies the URL of the DTP server. Include protocol and host name or IP address and, as appropriate, port and context path. . Default: `false`
`dtp.server=[host]`	Specifies the host name of the DTP server. This setting is deprecated.
`dtp.port=[port]`	Specifies the DTP server port. This setting is deprecated.
`console.verbosity.level=low\|normal\|high`	Specifies the verbosity level for the Console view. Available settings are: `low`: Configures the Console view to show errors and basic information about the current step’s name and status (done, failed, up-to-date). `normal`: Also shows command lines and issues reported during test and analysis. `high`: Also shows warnings.
`parallel.mode=Manual\|Auto\|Disabled`	Determines which of the following modes is active: Auto: Allows the product to control parallel processing settings. Manual: Allows you to manually configure parallel processing settings to suit your specific needs. Disabled: Configures the product to use only one of the available CPUs.
`parallel.max_threads=<number>`	Specifies the maximum number of parallel threads that can be executed simultaneously. The actual number of parallel threads is determined based on the number of CPUs, available memory, and license settings.
`parallel.free_memory_limit=<percentage>`	Specifies the amount of memory that should be kept free in low memory conditions (expressed as a percentage of the total memory available for the application). This is used to ensure that free memory is available for other processes.
`parallel.no_memory_limit=true\|false`	Indicates that you do not want to place any restrictions (beyond existing system limitations) on the memory available to the product.
`tasks.clear=true\|false`	Clears existing tasks upon startup in cli mode. This prevents excessive time being spent "loading existing results." The default is true.
`security.trust.all.certificates=true\|false`	Tells Virtualize that you want it to accept any certificate. This is useful if you want to load pages whose certificates are not "trusted."
`security.use.default.java.cacerts=true\|false`	Tells Virtualize that you want it to accept only certificates from the standard list of Java trusted certificate vendors.

Page tree

Versions Compared

Old Version 15

New Version 16

Key

Proxy Configuration Details

Console Settings

Proxy Configuration Details

Internet Explorer Notes

Console Settings

Continuous Testing Platform Settings
Anchor
CTP Settings
CTP Settings

Global Data Source Settings

Technical Support Settings

Global Data Source Settings

Technical Support Settings

MIME Type Settings

MIME Type Settings

Miscellaneous Settings

Proxy Settings

Security Settings

Configuring Kerberos Authentication for Tools

Anchor
Localsettings
Localsettings
Virtualize

Localsettings

Licensing Settings

Licensing Settings

Miscellaneous Settings

Manually Adding the License to

localsetttings

Virtualize network license - desktop edition

Virtualize network license -custom edition with various features

Virtualize network license -custom edition with various features

Page tree

Page History

Versions Compared

Old Version 15

New Version 16

Key

Proxy Configuration Details

Console Settings

Proxy Configuration Details

Internet Explorer Notes

Console Settings

Continuous Testing Platform Settings AnchorCTP SettingsCTP Settings

Global Data Source Settings

Technical Support Settings

Global Data Source Settings

Technical Support Settings

MIME Type Settings

MIME Type Settings

Miscellaneous Settings

Proxy Settings

Security Settings

Configuring Kerberos Authentication for Tools

AnchorLocalsettingsLocalsettingsVirtualize

Localsettings

Licensing Settings

Licensing Settings

Miscellaneous Settings

Manually Adding the License to

localsetttings

Virtualize network license - desktop edition

Virtualize network license -custom edition with various features

Virtualize network license -custom edition with various features

Continuous Testing Platform Settings
Anchor
CTP Settings
CTP Settings

Anchor
Localsettings
Localsettings
Virtualize