The following is a list of advanced configuration options you can specify in a properties file. For details on working with properties files, as well as the most commonly-used options, see Server Configuration.
In this section:
Specifies the character encoding; valid values are any encodings available on the JVM being used. The default is UTF-8.
The default timeout in milliseconds. Allows you to customize the length of delay after which Virtualize should consider your HTTP, JMS, or MQ requests to be “timed out.” The default is 30000 milliseconds.
Specifies what file format to use for saving project files (e.g., .pva, .pvn, .changetemplate). Project files can be saved in three formats—XML, binary, and compressed XML. The default is XML.
Tells Virtualize to automatically back up and save the project files you are working on. The default is false.
Specifies the threshold at which the REST API will return an error about large .pva file size. You can then reduce the file size (and prevent performance problems) by dividing it into smaller files. The default is 20.
Lets you globally indicate that you want certain values (such as timestamps) ignored whenever:
Exclusions are specified in the format:
Specifies a comma-separated list of directories where fixed length data model files are located (for use in Fixed Length responders).
Enables/disables the application of Windows and IE proxy settings.
If Windows/IE are properly configured so that the proxy accesses the relevant websites, set this option to
The default is
If Windows and IE (which use the same settings) are configured to properly use the proxy to access the relevant websites, set this property to
The default is
Enables/disables ability to use an automatic configuration script. Set this to
The default is
If your proxy server requires authentication, set this property to true, then enter a valid user name and password with proxy.username and proxy.password. The default is false.
If you want to use the same proxy server for all protocols, set this property to true, then enter the address and port of the proxy server you want to use in the proxy.http, proxy.ftp, proxy.secure, and proxy.*.port properties. The default is true.
The value should be a URL to the script: either an HTTP(S) URL or a file URL. File URLs should be formatted as "file:///" followed by the file system path where the proxy autoconfiguration script lives. For example, on Windows this could be file:///c:/Users/user/scripts/proxy.pac. On Linux, it might be file:///home/machine/scripts/proxy.pac.
Address of the http proxy to use. If the same proxy server will be used for all protocols, this is the value that will be used.
Port of the http proxy to use. If the same proxy server will be used for all protocols, this is the value that will be used.
Address of the ftp proxy to use.
Port of the ftp proxy to use.
Address of the secure proxy to use.
Port of the secure proxy to use.
Username to use when proxy authentication is enabled.
Password to use when proxy authentication is enabled.
If you want to allow Web traffic from designated IP addresses to pass through directly (avoiding the proxy), enter those IP addresses in this property. If you enter multiple addresses, use a semicolon (;) to separate the entries.
Specifies the location of the trust store to be used for Server-Side SSL (authentication of the Queue Manager by the client).
Specifies the location of the key store to be used for Client-Side SSL (authentication of the client by the Queue Manager).
Specifies the MQ SSL Key Store password.
You can set the following system properties when executing the startup command to fine-tune server operation.
Asynchronous processing enables better concurrency when responders are configured with delays (e.g., in performance profiles). You can control how the server processes requests by setting the following system properties during startup.
This property sets the asynchronous processing mode. The following modes are supported:
ON- all requests are processed asynchronously
DELAY- only response that have a delay are processed asynchronously, default
OFF- no asynchronous processing
This property sets the number of worker threads available for performing asynchronous processing. Default is
HTTP, JMS, MQ and Http Listeners are supported.
You can monitor the SOAtest and Virtualize Server with an APM tool, such as Dynatrace or AppDynamics. Refer to your tool's documentation for information about deploying APM software to monitor the SOAtest and Virtualize Server.
Additional SOAtest and Virtualize Server configuration is required to deploy AppDynamics.
com.singularity class package used by App Dynamics to the
org.osgi.framework.bootdelegation property using a wild card, e.g.: