...
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 Additional Preference Proxy Settings.
Console Settings
...
The OpenAI panel allows you to configure the application to use your OpenAI or Azure OpenAI account to assist you when creating test scenarios. The model of OpenAI that is used must support functional callsfunction calling. Functionality has been tested on GPT-3.5 turbo and GPT-4. Note this functionality is only supported with a license that has "LLM Integration" enabled.
Using OpenAI to create test scenarios requires access to your OpenAI or Azure OpenAI account. To enable it, set the following preferences:
Enable:
WhenWhen enabled, OpenAI is available when creating test scenarios from an OpenAPI/Swagger definition.
- Provider: Your OpenAI provider. Choose between OpenAI and Azure OpenAI.
- Configuration (OpenAI)
- API key: Your OpenAI token.
- Organization ID: The Organization ID you want to use when accessing the OpenAI client. Optional. If no Organization ID is supplied, the default organization ID for your account will be used.
- Test Connection: Click to test the connection to your OpenAI client.
- Model > Name: The name of the OpenAI model you are using, for example gpt-3.5-turbo-16k or gpt-4.
- Configuration (Azure OpenAI)
- Resource Name: The Azure resource group that contains your deployed Azure OpenAI resourcemodel.
- Deployment ID: The deployment name of your Azure OpenAI model.
- API key: Your Azure OpenAI token.
- Test Connection: Click to test the connection to your Azure OpenAI clientAzure OpenAI.
Note: OpenAI may produce inaccurate information, which may affect product features dependent on OpenAI.
| Note | ||
|---|---|---|
| ||
Eclipse users: If you are going through a proxy to connect to your OpenAI or Azure OpenAI account, your Eclipse proxy settings are used, not your Parasoft 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, seeAdditional Preference SettingsProxy Configuration Details).
- If Windows and IE (which use the same settings) are configured to properly use the proxy to access the relevant websites, select Use system proxy configuration.
Otherwise, select Enable proxy and manually enter the correct settings. These settings should be equivalent to what you would use in the browser outside of SOAtest/Virtualize.
- To use an automatic configuration script, select Use automatic configuration script and enter the proxy address in the Address field.
- If you want to use the same proxy server for all protocols, enable Same proxy server for all protocols, then enter the address and port of the proxy server you want to use in the Proxy Address and Proxy Port fields.
- If you want to use different proxy servers for different protocols, disable Same proxy server for all protocols, then enter the address and port of each proxy server you want to use in the Proxy Address and Proxy Port fields.
- If your proxy server requires authentication, enable Enable proxy authentication, then enter a valid username and password in the Username and Password fields.
- If you want to allow Web traffic from designated IP addresses to pass through directly (avoiding the proxy), enter those IP addresses in the Proxy Exceptions text field. If you enter multiple addresses, use a semicolon (;) to separate the entries.
- The Proxy Address 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 befile:///home/machine/scripts/proxy.pac.
...
| Info | ||
|---|---|---|
| ||
In order to perform operations that use the XML Signature Verifier, XML Signer, or XML Encryption tools, or if using Key Stores, you will need to download and install the Unlimited Strength Java Cryptography Extension. For details, see Additional Preference Settings JCE Prerequisite. |
Keystores are specified at the test or responder suite level. If this option is selected, the following options are available in the Certificate and Private Key tabs:
...
The XML Schema Locations panel lets you view, add, and remove schema locations.The XML Validator tool needs to know where to find the schema that it should use to validate the document of concern. In most cases this is a URI and is supplied within the document being validated. If, however, the URI for the schema is not supplied or if you want to use a different location, then disable Use namespace as location URI for Schemas for the XML Validator tool. For more information on the XML Validator tool, see .XML Validator vSOAVIRT_9.10. 2_CTP_3.0.2. When the tool is run with this option disabled, SOAtest will use the schema location(s) indicated in this panel. To add a new schema location:
...
| Setting | Purpose |
|---|---|
virtualize.license.use_network=true|false | Determines whether the current installation retrieves its license from License Server. |
virtualize.license.network.host=[host] | Specifies the machine name or IP address of the machine running License Server Configuration Manager. If your server uses the HTTPS protocol, prepend This setting is deprecated. |
virtualize.license.network.port=[port] | Specifies the License Server port number. This setting is deprecated. |
virtualize.license.network.user=[username] | Specifies the username for authentication on the secondary DTP server specified with the This option requires the Example: |
virtualize.license.network.password=[password] | Specifies the password for authentication on the secondary DTP server specified with the This option requires the We strongly recommend encoding your password to ensure successful authentication and a secure connection. You can encode your password by running Example:
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: |
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 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 This option requires the |
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 If set to |
virtualize.license.network.edition=[edition_name] | Specifies the type of license that you want this installation to retrieve from LicenseServer.
Example:
|
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 |
...
Note that with local licenses, the enabled features are specified via the generated password.
...