You can configure Parasoft Virtualize Server using a properties file. The default location of the properties file is <SOAVIRT_HOME>/WEB-INF/config.properties.
When editing Windows file paths in config.properties, be sure to use forward slashes, not backslashes.
Several options can be specified in the config.properties file. The following is a list of the most commonly-specified options. See Advanced Virtualize Server Configuration Options for additional options.
In this section:
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.
This option changes the logging level using a built-in or custom log4j 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:
You can modify these built-in configurations as needed; see the log4j documentation for details.
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.
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 minutes.
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.
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.
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.
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.
This option specifies the username for logging into CTP.
This option specifies the (plain text or encoded) password for logging into CTP.
As with the standard Eclipse-based Parasoft products, you can use the
This option enables/disables notifications to Parasoft CTP when virtual assets are deployed.
The following example enables notifications:
This is a read-only setting used by CTP.
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 Parasoft Development Testing Platform (DTP).
Configure the following options to connect to DTP:
Configure the following options to connect to License Server:
The following example enables licensing over a network:
This option specifies the type of license to retrieve from DTP or License Server. You can specify either
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.
This option specifies the host name of the DTP server. You must also set the
This option specifies the port number of the DTP server. You must also set the
This option specifies the user name for DTP authentication.You must also set the
This option specifies the password for DTP authentication.You must also set the
This option specifies the host name of the License Server. You must also set the
This option specifies the host port of the License Server. You must also set the
This option specifies the password for the local Virtualize license. You must also set the
This option specifies an expiration for the local Virtualize license. You must also set the
You can make external/custom jars (e.g., Parasoft SOAtest/Virtualize custom extensions, third-party jars, JDBC drivers, etc.) available to Parasoft Virtualize Server.
If you want to modify the value of the "Server" HTTP Header in Parasoft Virtualize Server's HTTP Response to ‘Parasoft Server’ (this is the default for traditional Eclipse-based Virtualize server deployments), you need to modify the servlet container configuration.
Some servlet containers reject Trace requests (i.e., HTTP requests using the TRACE HTTP method). If your servlet container rejects Trace requests but you want Parasoft Virtualize Server to support Trace requests (like traditional Eclipse-based Virtualize Server deployments do), you will need to update your servlet container configuration accordingly.