You can configure the proxy port, specify test creation options, and access the API so that the tool can be used in automated workflows. In this section:
Proxy System Properties
You can configure the web proxy by specifying system properties in the Manage Web Proxy console or from the command line when executing the .jar file. You can specify the following properties:
| -DapiPort | System property that specifies the API port number. Default is 40090. |
|---|---|
| -DwebsocketPort | System property that specifies the websocket port for streaming traffic events from the Chrome extension. Defaults to one port higher than API port. |
| -DproxyPortStart | System property that specifies the starting port number when scanning for an open port. Default is |
| -DproxyPortRange | System property that limits the number of ports scanned after the starting port number (value specified with the |
| -DproxyAutoConfigURL | System property that specifies the URL of a proxy auto-configuration (PAC) file, for example:
|
| -DuseSystemProxy | Enables/disables use of the network-level proxy. Default is |
| -Ddebug | Enables/disables system debugging information. Default is false. |
| -DenableHTTPCacheControl | Enables/disables HTTP cache headers to be passed through the proxy. Default is false. The default mode will actively remove HTTP cache headers. |
Manage Web Proxy Example
Add the system properties to the Java Options field in the Java tab. The following example sets the API port to 45000 and enables debugging:
Command Line Example
Specify the configuration options on startup from the command line. The following startup command sets the API port to 10080, scans for a range of port numbers, and enables debugging:
%JAVA_HOME%/bin/java -DapiPort=10080 -DproxyPortStart=20443 -DproxyPortRange=10 -Ddebug=true -jar com.parasoft.traffic.proxy.jar
Java Support
Parasoft Recorder ships with its own instance of Java, but you can use any Java 11 or later that is already installed on your system.
Test Creation Properties
You can configure test creation settings in the tst_creation.properties file. The file is shipped with SOAtest (see Configuring Smart API Test Generation) and is deployed to the SOAtest server workspace under the TestAssets folder. All web proxies that connect to the SOAtest server will use the settings configured in this file.
Parasoft Recorder also installs a tst_creation.properties.examples file on the local machine. You can override the settings configured in the tst_creation.properties file in the SOAtest server workspace by renaming the local file to tst_creation.properties and setting the useServerSettings property to false. The settings file should be stored in the same directory as the com.parasoft.traffic.proxy.jar file so that it can automatically be read during test creation.
Refer to Configuring Smart API Test Generation for details about the test creation properties.
Using the API
After starting the web proxy, you can go to the following URL to review the API defintions:
http://<host>:<port>/api/openapi.json
