parasoft.eula.accepted

This option sets the property to accept the Parasoft End User License Agreement (EULA). The default is false. You must accept the EULA to use the product. Please read the EULA at https://www.parasoft.com/license.

Example Usage

parasoft.eula.accepted=true

working.dir

This option specifies an absolute path to the SOAVIRT working directory. If not specified, a default working directory called ‘workspace’ is created in the <SOAVIRT_HOME> folder. We recommend changing the default directory so that the workspace is not under the <SOAVIRT_HOME> folder because upgrading to a newer version of the server could overwrite the workspace.

logging.config.file

This option changes the logging level using a built-in or custom log4j2 configuration. If not specified, the default value is /WEB-INF/default.logging.xml. 

You can specify a configuration using an absolute path or a relative path. The root for relative paths is the <SOAVIRT_HOME> directory location. The server ships with two built-in configurations available in the /WEB-INF/ folder:

• default.logging.xml: A standard log4j2 configuration that logs INFO, WARN, and ERROR messages.
• debug.logging.xml: A standard log4j2 configuration that provides verbose logging with extended details.

You can modify these built-in configurations as needed; see the log4j2 documentation for details.

Example Usage

logging.config.file=/WEB-INF/default.logging.xml

If you unzipped the WAR into c:/wars/soavirt, the server would resolve the relative location of logging.config.file to the absolute path c:/wars/soavirt/WEB-INF/default.logging.xml.

logging.config.file=d:/MyConfigurations/default.logging.xml

User Access Logging

You can enable/disable user access logs for the server by modifying default.logging.xml or debug.logging.xml (depending on which is being used). User access logging is enabled by default in WAR installations and disabled by default in desktop installations. To disable user access logging, comment out the ACCESS rolling file appender and appender reference and set the log level for the logger com.parasoft.webtool.rest.api.web.providers.access.logs from trace to off. To enable user access logging for virtualizecli, run it with the logging.config.file option and provide an xml file with these elements enabled.

By default, the log file will go into the Tomcat installation logs directory, but you can change this by editing the fileName and filePattern attributes. Note: when no username is available, an en dash ( - ) will be used as a stand-in for the username in the logs.

Example of default fileName:

fileName="${sys:catalina.home}/logs/soavirt_access.log"

Example of default.logging.xml with access logging off:

<?xml version="1.0" encoding="UTF-8"?>
<Configuration>
 
  <Appenders>
    <Console name="CONSOLE" target="SYSTEM_OUT">
      <PatternLayout pattern="%d{dd-MMM-yyyy HH:mm:ss,SSS} [%p] %m at %l%n" />
    </Console>
 
    <!-- Uncomment this appender when using access logs
    <RollingFile name="ACCESS" fileName="${sys:catalina.home}/logs/soavirt_access.log" filePattern="${sys:catalina.home}/logs/$${date:yyyy-MM}/access-%d{MM-dd-yyyy}-%i.log.gz">
        <PatternLayout pattern="%d{dd-MMM-yyyy HH:mm:ss,SSS} [%p] %m%n" />
        <Policies>
            <TimeBasedTriggeringPolicy />
            <SizeBasedTriggeringPolicy size="50 MB"/>
        </Policies>
    </RollingFile>
     -->
 
  </Appenders>
 
  <Loggers>
    <Logger name="com.parasoft" level="INFO">
      <AppenderRef ref="CONSOLE" />
    </Logger>
    <!-- Set level to "trace" to enable access logs -->
    <Logger name="com.parasoft.webtool.rest.api.web.providers.access.logs" additivity="false" level="off">
      <!-- Uncomment to direct to access log file
      <AppenderRef ref="ACCESS" />
        -->
    </Logger>
    <Logger name="com.parasoft.ptest.lic.client.internal" level="off" />
    <Logger name="com.parasoft.ptest.lic.client.validator" level="off" />
    <Root level="off" />
  </Loggers>
 
</Configuration>

scripting.timeout.minutes

This option specifies the number of minutes after which Virtualize will attempt to stop an unresponsive script and log an error message. The default is 10.

Example Usage

scripting.timeout.minutes=5

server.hostname

This option specifies the hostname that CTP will use to connect to the server. Under most circumstances, this option does not require configuration. If the server container or network infrastructure prevents the connection from being established, however, the option may be necessary if the remote host cannot determine a valid way to connect back to the server. This may be the case when working with containerized environments. 

server.port.http

This option tells CTP which port Parasoft Virtualize Server is listening to for HTTP. You must specify either server.port.http or server.port.https port. This value must match the HTTP port under which Parasoft Virtualize Server is deployed.

server.port.https

This option tells CTP which port Parasoft Virtualize Server is listening to for HTTPS. You must specify either server.port.https or server.port.http port. This value must match the HTTPS port under which Parasoft Virtualize Server is deployed.

env.manager.server

This option specifies the location of the CTP server. Be sure to specify the port and protocol (http/ https). Colons must be escaped with the backslash ( \ ) character.

Example Usage

env.manager.server=http\://em.parasoft.com\:8080/

env.manager.server=https\://em.parasoft.com\:9443/

Setting the Property with the REST API

You can also set this property after the server has been started using the REST API. Note that settings related to CTP in the .properties file are named "env.manager", which refers to the legacy name Environment Manager. The CTP object in the API, however, is labeled "ctp". These settings refer to the same component.

1. Start the server and go the endpoint for writing to the .properties file:
   
   http://<HOST>:<PORT>/soavirt/api/v5#!/preferences/preferencesPUT_config
 
2. Click Try it out and enter the Continuous Testing Platform (CTP) server settings as a JSON object into the input field.
   
3. Click Execute to update the configuration on the server.

You can copy the following example JSON, paste it into your input field, and change the values to your installation:

{
  "ctp": {
    "server": "<your-ctp-server>:<port>",
    "name": "<your-ctp-server-name>",
    "username": "<your-username>",
    "password": "<your-password>",
    "notify": false,
  }
}

env.manager.server. name

This option specifies the name that will be used to label this server on CTP. You can use any value that helps you identify this server. 

Example Usage

env.manager.server.name=MyVirtServerLabel

Setting the Property with the REST API

You can also set this property after the server has been started using the REST API. See env.manager.server for details.

env.manager.username

This option specifies the username for logging into CTP.

Example Usage

env.manager.username=me 

Setting the Property with the REST API

You can also set this property after the server has been started using the REST API. See env.manager.server for details.

env.manager.password

This option specifies the (plain text or encoded) password for logging into CTP. 

We strongly recommend encoding passwords to ensure successful authentication and a secure connection. The WAR distribution contains a script that can encode passwords. To use it, run:

<SOAVIRT_HOME>/scripts/encodepass.sh <YOUR_PASSWORD>

or

<SOAVIRT_HOME>/scripts/encodepass.bat <YOUR_PASSWORD>

as appropriate for your OS.

You can also run a command line instance of SOAtest or Virtualize with the -encodepass flag. Examples:

soatestcli.exe -encodepass <YOUR_PASSWORD> 

virtualizecli.exe -encodepass <YOUR_PASSWORD> 

Either method will generate an encoded string that you can use in place of the password property in the SOAtest and Virtualize Server configuration file. See CLI Options for additional information about command line options.  

Example Usage

env.manager.password=12345

Setting the Property with the REST API

You can also set this property after the server has been started using the REST API. See env.manager.server for details.

env.manager.notify

This option enables/disables notifications to Parasoft CTP when virtual assets are deployed.

Example Usage

The following example enables notifications:

env.manager.notify=true

Setting the Property with the REST API

You can also set this property after the server has been started using the REST API. See env.manager.server for details.

env.manager.registry.id

This is a read-only setting used by CTP. 

soatest.license.enabled

This option enables/disables the license related to SOAtest functionality. The default is true. If this option is not present in the .properties configuration file, the default is used. If this option is set to false, other license-related settings will be ignored.

Example Usage

soatest.license.enabled=true

virtualize.license.enabled

This option enables/disables the license related to Virtualize functionality. The default is true. If this option is not present in the .properties configuration file, the default is used. If this option is set to false, other license-related settings will be ignored.

Example Usage

virtualize.license.enabled=true

soatest.license.use_network

This option enables/disables licensing over a network. If you are using a network license, you must also configure either a connection to License Server or to Parasoft DTP. 

Configure the following options to connect to License Server:

• license.network.url

Configure the following options to connect to DTP:

• dtp.url
• dtp.user
• dtp.password

Example Usage

The following example enables licensing over a network:

soatest.license.use_network=true

soatest.license.network.edition

This option specifies the type of license to retrieve from License Server or DTP. You can specify either custom_edition or professional_ edition. Contact your Parasoft representative if you are unsure of which edition you should set.

Example Usage

soatest.license.network.edition=custom_edition

soatest.license.custom_edition_features

This option specifies a comma separated list of features that should be requested for a custom edition license from License Server or DTP. Contact your Parasoft representative if you are unsure of which features you should specify.

Example Usage

soatest.license.custom_edition_features=RuleWizard,Command Line,SOA,Web,Server API Enabled,Jtest Connect,Message Packs,Advanced Test Generation Desktop,Advanced Test Generation 100 Users

virtualize.license.use_network

This option enables/disables licensing over a network. If you are using a network license, you must also configure either a connection to Parasoft DTP or to License Server (deprecated). 

Configure the following options to connect to License Server:

• license.network.url

Configure the following options to connect to DTP:

• dtp.url
• dtp.user
• dtp.password

Example Usage

The following example enables licensing over a network:

virtualize.license.use_network=true

virtualize.license.network.edition

This option specifies the type of license to retrieve from DTP or License Server. You can specify either custom_edition or professional_ edition. Contact your Parasoft representative if you are unsure of which edition you should set.

Example Usage

virtualize.license.network.edition=custom_edition

virtualize.license.custom_edition_features

This option specifies a comma separated list of features that should be requested for a custom edition license from DTP or License Server. Contact your Parasoft representative if you are unsure of which features you should specify.

Example Usage

virtualize.license.custom_edition_features=Virtualize,Validate,Performance,Extension Pack,Service Enabled,Unlimited Hits/Day

dtp.url

This option specifies the URL of the DTP server. Remember to include the https:// protocol; DTP does not support http:// connections. If DTP is deployed to a location other than the root of the host server, the URL should include a context path (a relative path from the host name; for example: https://server.company.com:8443/contextPath). This may be the case if your organization uses a reverse proxy. Refer to the DTP documentation on https://docs.parasoft.com for additional information about reverse proxy server configuration and context path configuration.

Example Usage

https://10.9.1.63:8443

dtp.server (deprecated)

This option specifies the host name of the DTP server. You must also set the virtualize.license.use_network option to true (see virtualize.license.use_network). This option is deprecated.

Example Usage

dtp.server=main1.parasoft.com

dtp.port (deprecated)

This option specifies the port number of the DTP server. You must also set the virtualize.license.use_network option to true (see virtualize.license.use_network). This option is deprecated.

dtp.user

This option specifies the username for DTP authentication. You must also set the virtualize.license.use_network option to true (see virtualize.license.use_network).

Example Usage

dtp.user=admin

dtp.password

This option specifies the password for DTP authentication. You must also set the virtualize.license.use_network option to true (see virtualize.license.use_network).

Example Usage

dtp.user=mypassword

license.network.url

This option specifies the URL of the License Server. Remember to include the https:// protocol; License Server does not support http:// connections. If License Server is deployed to a location other than the root of the host server, the URL should include a context path (a relative path from the host name; for example: https://server.company.com:8443/contextPath). This may be the case if your organization uses a reverse proxy. Refer to the License Server documentation on https://docs.parasoft.com for additional information about reverse proxy server configuration and context path configuration.

Example Usage

https://10.9.1.63:8443

license.network.host (deprecated)

This option specifies the host name of the License Server. You must also set the virtualize.license.use_network option to true (see virtualize.license.use_network). This option is deprecated.

license.network.port (deprecated)

This option specifies the host port of the License Server. You must also set the virtualize.license.use_network option to true (see virtualize.license.use_network). This option is deprecated.

license.network.user

Specifies the username for authentication on the License Server specified with the license.network.url option. It requires the license.network.use.specified.server and license.network.auth.enabled options set to true.

Example: license.network.user=JohnDoe

license.network.password

Specifies the password for authentication on the License Server specified with the license.network.url option. It requires the license.network.use.specified.server and license.network.auth.enabled options set to true, and the license.network.user to be configured.

We strongly recommend encoding passwords to ensure successful authentication and a secure connection. The WAR distribution contains a script that can encode passwords. To use it, run:

<SOAVIRT_HOME>/scripts/encodepass.sh <YOUR_PASSWORD>

or

<SOAVIRT_HOME>/scripts/encodepass.bat <YOUR_PASSWORD>

as appropriate for your OS.

You can also run a command line instance of SOAtest or Virtualize with the -encodepass flag. Examples:

soatestcli.exe -encodepass <YOUR_PASSWORD> 

virtualizecli.exe -encodepass <YOUR_PASSWORD> 

Either method will generate an encoded string that you can use in place of the password property in the SOAtest and Virtualize Server configuration file. See CLI Options for additional information about command line options.  

license.network.use.specified.server

This option enables the server to connect to connect to either DTP and License Server or two instances of DTP simultaneously. 

license.network.auth.enabled

Enables or disables authentication on the License Server specified with the license.network.url option.

This option requires the license.network.use.specified.server option to be set to true.

virtualize.license.local.password

This option specifies the password for the local Virtualize license. You must also set the virtualize.license.use_network option to false (see virtualize.license.use_network).

virtualize.license.local.expiration

This option specifies an expiration for the local Virtualize license. You must also set the virtualize.license.use_network option to false (see virtualize.license.use_network).

usage.reporting.enabled

This setting enables or disables collecting anonymous usage information and sending it to Parasoft. Read our privacy statement to learn more at https://www.parasoft.com/privacy-policy.

Example Usage

The following example enables anonymous usage data reporting:

usage.reporting.enabled=true 

security.kerberos.realm

This option specifies the Kerberos realm associated with your network. By convention, this is typically your domain name in all caps (for example, PARASOFT.COM).

For more information, see "About Kerberos Authentication" in Security Settings on the Additional Preference Settings page.

security.kerberos.kdc.server

This option specifies the hostname of your Key Distribution Center (for example, kdc.parasoft.com).

For more information, see "About Kerberos Authentication" in Security Settings on the Additional Preference Settings page.

session.tag

This setting specifies a tag for signing results from the test session. The tag can be a string, one or more variables, or a combination. Reports for different test sessions should be marked with different session tags so that similar runs can be distinguished from each other. The default is session.tag=${config_name}

Example Usage

You can use the session tag to represent a specific analysis type made on a specific code branch in a specific test environment. The following configuration could identify functional tests on the master branch for different operating systems:

session.tag=ft_master_${os}

build.id

This setting specifies a build identifier used to label results. It may be unique for each build, but it may also label more than one test session executed during a specified build. The default is ${dtp_project}-${time}.

Example Usage

The default build ID includes the name of the project in DTP and the date of the build. For example, for the ATM project, the build ID included in the report may resemble the following: ATM-2017-07-07. 

The following configuration specifies the custom build ID that consists of the name of the project and the build number passed via the environmental variable BUILD:

build.id=${dtp_project}-${env_var:BUILD}

For the ABC project and the build number 114 on a CI server, this may resolve to ABC-114.

report.format

This setting specifies the report format. Use a comma separated list of format values to publish reports in more than one format. By default, an XML report containing the data and an HTML file for presenting the data are published. The following values are supported:

• xml (default)
• html (default)
• pdf  
• csv
• custom (see report.custom.extension and report.custom.xsl.file for usage)

report.custom.extension

This setting specifies the file extension for a custom report. Custom formats are defined in an XSL file. The report.format option must be set to custom and the report.custom.xsl.file option must also be configured.

report.custom.xsl.file

This setting specifies the path to an XSL file used to create a custom report format. Use double backslashes when specifying the file path on Windows.

report.developer_errors

This setting determines if details about developer errors should be included in manager reports. Set to true to include developer errors in reports or set to false to exclude developer errors in reports. The default is true.

report.developer_reports

This setting determines if detailed reports for all developers should be generated in addition to the summary report for managers. Set to true to enable generating detailed reports for developers. Set to false to disable generating detailed reports for developers. The default is true.

report.authors_details

This setting determines if an overview of the number and type of tasks assigned to each developer should be included in the report. Set to true to include types and numbers of tasks assigned to each developer. Set to false to exclude types and numbers of tasks assigned to each developer. The default is true.

report.testcases_details

This setting determines if additional test case details should be included in the report. Set to true to include additional details about test cases. Set to false to exclude additional details about test cases. The default is false.

report.associations

This setting enables or disables showing requirements, defects, tasks, and feature requests associated with a test in the report. Set to true to include requirements, tasks, and feature requests in the report. Set to false to exclude requirements, tasks, and feature requests from the report. The default is false.

report.assoc.url.[tag]

This setting generates a link to an association inside the HTML report. The URL is a query string containing an [%ID%] or ${id} placeholder for the issue identifier. Supported tags are pr, fr, task, req, and test.

Example Usage

The following example creates a link to a PR in Bugzilla in the HTML report:

report.assoc.url.pr=http://bugzilla.company.com/show_bug.cgi?id=[%ID%]

report.failed_tests_only

This setting determines if only tests that failed should be included in the report. This option is only valid for functional testing tools. Set to true to only include tests that failed in the report. Set to false to include all tests in the report. The default is false.

report.env_details

This setting turns on additional details in the XML report about the active environment used when running a tst. The default is false.

report.output_details

This setting turns on additional details in the XML report about output tools that were executed when running a tst. The default is false.

report.test_suites_only

This setting determines if summary section of the report lists only top-level suites or if it displays a tree-like view of the individual tests. Set to true to only include top-level suites in the summary section of the report. Set to false to include a tree-like view of the individual tests. The default is true.