...

• Use DTP settings: Enable this option to use the connections settings specified in DTP. See Connecting to DTP. 
• Server Name: Specifies a name for the server you are connecting to CTP. This is the name that will be used to identify this server within CTP.
• CTP URL: Specifies the location of the CTP to which you are connecting (e.g., http://emdemo:8080).

• Notify CTP of virtual asset deployment: Determines whether the  server notifies Parasoft CTP when virtual assets are first deployed.

• Username: Specifies the username for logging into CTP.

• Password: Specifies the password for logging into CTP.

  Note
  If OpenID Connect authentication is enabled, the Username and Password fields do not appear. Instead, you will see a notice that OIDC authentication is in use with a button to test that connection.

Global Data Source Settings

...

• Default timeout (milliseconds): Allows you to enter the length of delay (in milliseconds) after which SOAtest should consider your FTP, telnet, or HTTP requests to be “timed out.” The default is 30000 milliseconds.
• Report each duplicate error that occurs on the same line: Tells SOAtest to show only the first instance of duplicate errors that occur for the same line of code.
• Reset Cookies: Allows you to clear the current global cookies so that next HTTP invocations start a new session.
• Enable the Automatically backup project files option and specify a file size threshold for .tst and/or .pva files in the Warn on file size large than (MB) field to be notified when the size of the file exceeds the threshold. You can then reduce the size (and prevent performance problems) by dividing it into smaller files.

Proxy Settings

Anchor
OIDC OIDC

OpenID Connect

The OpenID Connect panels allows you to configure the application to authenticate users via your OpenID Connect server.

1. Go to Parasoft > Preferences and select OpenID Connect.
   Image Added
2. Check Enable.
3. Configure the following options:
   • Issuer URI: The URI of your OpenID Connect server.
   • Client ID: The ID registered on your OpenID Connect server.
   • Callback host: The local callback host required to communicate with the OpenID Connect server. The following options are available:
     • localhost: The localhost address will be used for communication.
     • 127.0.0.1: The loopback IP address 127.0.0.1 will be used for communication.
   • Callback port: The callback port number for communication with the OpenID Connect server. The following options are available:
     • Automatically select an open port: Automatically selects an open port (recommended).
     • Use port: Allows you to manually specify the port number.
   • Callback timeout: Specifies, in seconds, the maximum time the browser will wait for user credentials.
4. Click Test Authentication or Apply to open the OpenID Connect authentication page in your browser.
5. Provide your credentials in the browser window that opens.
6. Close the browser window when the authentication confirmation appears and continue in the application.
7. Click Apply to apply the changes.

The Status panel shows the current OpenID Connect authentication status.

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 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, seeProxy Configuration Details). 

...

The Scripting panel allows you to specify properties used for custom scripts.

• • Java: For Java, you can specify the Java home directory and the path to the javac compiler. You need to specify these parameters if you want to compile Java methods in the editor.   

    Note
    title Note
    The javac compiler is not included.

    • Java home: Specifies the Java installation directory.
    • Javac classpath: Specifies the Java classpath.
  • JavaScript: If you create scripts using
Jython or
• • JavaScript, you can specify a script template in the Script Template field.
    • Script Template: Whatever code is specified in this field will be used as the default code for inlined scripting in the language with which the field is associated. This is primarily useful for setting default inputs and common global variables. Script templates apply to scripts used in Extension tools; they do not apply to JavaScript that runs in a browser context.

  • Jython:

For Jython, you can specify the jython.home and jython.path variables. Both variables are used to locate Jython modules. Jython code that does not import any Jython modules can use the Jython scripting support without setting either variable. If you set the jython.home and jython.path variables, you need to restart SOAtest or Virtualize before the changes will take effect.

• • If you are using Jython scripts, you can specify the Jython Path variable. Jython scripting support can be used without setting this variable by specifying a script template in the Script Template field.

    • Jython Path: Specifies a list of directories to search for python modules that are not already included with Jython. Separate multiple directory paths using the OS default path separator (";" for Windows and ":" for Linux and macOS). If you set the Jython path then you need to restart SOAtest or Virtualize for the change to take effect.
    • Script Template: Code specified in this field sets a default template for Jython scripts used in the tool.
• Jython Home: Specifies the Jython installation directory. This must be a single directory. Use a forward slash (/) or backslash (\) to escape special characters.
• Jython Path: Used to add to your path modules that are not in your jython.home/Lib directory. Multiple paths can be listed. Use a forward slash (/) or backslash (\) to escape special characters.
Script Template: Jython code that does not import any Jython modules can use the Jython scripting support without setting either the jython.home or jython.path.
• • Timeout Settings: Specify how many minutes SOAtest or Virtualize should wait before attempting to stop an unresponsive script and log an error message.

Security Settings

You can configure default security settings for Responders used in your projects. In most cases, the security settings can be overridden by configurations set locally in your suites:

...

Configure global HTTP authentication properties that can be used when configuring HTTP protocols within an applicable tool.

1. Enables Enable the Perform Authentication option and enter the Username and Password to authenticate the request
2. Choose the authentication type from the drop-down menu. Supported types are Basic, NTLM, Kerberos, or Digest.
3. If you are using Kerberos authentication, enter the Service Principal to authenticate the request. If the correct username and password, or the correct service principal, are not used, the request will not be authenticated.
   1. Kerberos realm: Specify the Kerberos realm associated with your network. By convention, this is typically your domain name in all caps (e.g. PARASOFT.COM).
   2. KDC server: Specify the hostname of your Key Distribution Center (e.g. kdc.parasoft.com).
   3. Check Ticket: This will execute a simple test to locate a cached Kerberos TGT (Ticket Granting Ticket) to grant access to the service. SOAtest and/or Virtualize will not be able to communicate with the service if it cannot first locate a valid TGT. For more information about Kerberos, see Configuring Kerberos Authentication.

...

Anchor
#ConfiguringKerberosAuthentication #ConfiguringKerberosAuthentication

Configuring Kerberos Authentication for Tools

1. Select the tool for which you intend to use Kerberos authentication.
2. Select the Transport tab and select Security from the left pane of the Transport tab. 
3. Configure the following options from the security panel of the Transport tab:
   1. Perform Authentication: Select this option to activate authentication.
   2. Use Global Preferences: Select this option if you have authentication properties setup in Security Preferences.
   3. Type: Select Kerberos to perform Kerberos Authentication.
   4. Service Principal: Specify the name of the service/server as defined in the Kerberos database (e.g. HTTP/soatest.parasoft.com).

...

1. Click the Add button beneath the OASIS XML Catalog Locations section of the Schema Locations tab. The Location dialog box displays.
2. Type in the OASIS XML Catalog Location or Browse to it by clicking the Browse button.
3. Click OK after you have added all of the necessary locations.

Anchor
Localsettings Localsettings

Virtualize

...

Settings

There are two ways to define localsettings settings files:

• Enter them manually in a simple text file simple text file. There are no name or location requirements. Each local setting should be entered in a single line.
• Export your GUI preferences, then adjust or extend them as needed. To export, choose Parasoft> Preferences, select Parasoft (the root element in the left tree), click the Share link, specify which settings you want to export.

Localsettings Settings files can specify the following settings.

Licensing Settings

...

...

Miscellaneous Settings

Manually Adding the License to

...

Setttings

To add or change license settings via settings vialocalsettings:

1. If you will be using a custom edition license, define the appropriate license features in the localsettings settings as follows:
   [product].license.custom_edition_features= All enabled features
   Note that license feature settings apply only to custom edition licenses.

2. Define the main license settings in the localsettings settings as follows:

   Code Block
   virtualize.license.network.edition= [Type of license edition] virtualize.license.use_network= [Value (true or false)] license.network.host= Host name license.network.port= Port numberurl=[URL]

   If your server uses the HTTPS protocol, prepend https:// to the hostname.

Here are several examples of properly-configured license settings in localsettings settings file:

Virtualize network license - desktop edition

virtualize.license.network.edition=desktop_edition 
virtualize.license.use_network=true
license.network.hosturl=http://main1.parasoft.com.pl 
license.network.port=:2222

Virtualize network license -custom edition with various features

virtualize.license.custom_edition_features=Virtualize, Server, Message Packs, Unlimited Million Hits / Day
virtualize.license.network.edition=custom_edition
virtualize.license.use_network=true
license.network.hosturl=http://main1.parasoft.com.pl
license.network.port=:2222

Virtualize network license -custom edition with various features

...