...
| Table of Contents | ||
|---|---|---|
|
Authors
The Authors configuration screen enables you to specify how code authors are mapped to user names and email addresses when quality tasks are generated. See Specifying Author-to-Author and Author-to-Email Mappings for details.
Browser Settings
The Browser panel lets you set options related to Web scenario recording. Available settings include:
Firefox Executable Path: Specifies the path to the Firefox executable. On Windows machines, SOAtest and/or Virtualize will attempt to detect a Firefox installation automatically. Linux users will have to browse to the Firefox executable.
- Chrome Executable Path: Specifies the path to the Chrome executable. Paths set here will be used in web recording wizards and other applicable areas. On Linux, choose
google-chrome(e.g. /opt/google/chrome/google-chrome)—notchrome.
Proxy port: Specifies the proxy port. See Proxy Configuration Details below for more information and tips.Anchor proxy-port-field proxy-port-field - Browser communication port: Specifies the browser communication port.
Browser Timeout Settings: Specifies the length of delay (in milliseconds) after which SOAtest and/or Virtualize should stop waiting for browser startup or a user action and consider it to be "timed out."
Wait Condition Default Timeout Settings: Specifies the length of delay (in seconds) after which SOAtest and/or Virtualize should stop waiting for the activity specified in the wait condition to occur and consider it to be "timed out."
Debug Options> Print debugging information: During recording of a web scenario, it is possible that an action taken is not recorded by SOAtest and/or Virtualize. Enabling this option will allow messages to be printed to the message console during recording, with information about what events SOAtest and/or Virtualize handled, any locators that may have been generated, and if applicable, any exceptions that took place during recording.
Error Reporting> Report website's scripting errors: Configures SOAtest and/or Virtualize to report scripting errors that occur during scenario execution. In Internet Explorer, the Selenium Web-Driver framework will not report JavaScript errors on the page to SOAtest and/or Virtualize; this reporting is supported only for the legacy engine.
- Allowable Binary Files in Traffic Viewer and Outputs: Allows binary files with the specified extensions or MIME types to be used in the Traffic Viewer and output. By default, only text files will be allowed.
Browser Contents Viewer Rendering Engine: Enables you to specify what browser is used for the Browsear Contents Viewer tool(described in Browser Contents Viewer tool ) , which can be attached to the Browser Playback tool.
- The default option (Same browser used for playback) is generally the recommended option because some web applications generate their pages differently based on the browser used. Using the same browser that was used during the playback can help ensure that pages display properly in the Browser Contents Viewer. Note that if the playback browser was Chrome, the Firefox rendering engine is used.
When Internet Explorer is selected, the version of IE that is used depends on what version of IE is installed on the machine running SOAtest and/or Virtualize. The Internet Explorer option is available only on Windows.
When Firefox is selected, the version of Firefox that is used depends on what Eclipse is being used to run SOAtest and/or Virtualize. It can range from Firefox 3.0.1 to Firefox 10, depending on what OS is being used.
- If the particular web application being tested does not render properly in the Browser Contents Viewer, you could try configuring this option to use either Internet Explorer or Firefox specifically (rather than use the default Same browser used for playback option) to see if using a specific rendering engine will improve how the page is shown in the Browser Contents Viewer.
HTML Content Fetch Mode: Enables you to determine whether the contents of hidden frames are displayed in the pre- and post-action HTML viewer. This can impact record and playback speed, as well as file size. It is possible to use one mode on some of your team’s SOAtest and/or Virtualize machines (e.g., desktop installation), and a different mode on others (e.g, the Server machine running in command-line mode).
Fetch all HTML content Choose this option if you want to see the contents of hidden frames in the pre- and post-action HTML viewer
Fetch content for all content except hidden frames: Choose this option if you do not need to see the contents of hidden frames in the pre- and post-action HTML viewer.
Proxy Configuration Details
When you record or run web scenarios in a browser, the proxy settings in the browser are set to an internal proxy maintained by SOAtest and/or Virtualize. All communication to and from the browser during recording and playback goes through the internal proxy, which is an intermediary used to capture traffic and otherwise facilitate execution. During recording and playback, SOAtest and/or Virtualize temporarily creates this proxy on localhost using the port specified by the Browser Playback setting’s Proxy port option.
The default host and port for the internal proxy is localhost:55555. Change the port number if this port is already in use using the controls Proxy port field. Do not change this from within the browser.
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 Proxy Settings.
Internet Explorer Notes
SOAtest and Virtualize modify the global registry settings prior to starting its instance of the browser. If an instance of Internet Explorer was running on the machine prior to launching SOAtest or Virtualize (not recommended), the global registry settings will not be set in the existing browser instance.
In these cases, check the Internet Options panel in the existing browser instance while a web scenario is running to verify that the settings point to SOAtest’s or Virtualize's proxy and click OK in the Internet Options panel. If you click OK, the proxy settings are updated in the existing browser instance. If you click Cancel, or do not go to the Internet Options panel, then the existing browser instance never picks up the proxy settings and should continue to navigate fine.
Proxy settings may not be reset properly if the browser exited abnormally, if there is a hanging browser process, etc. Such issues can affect new browser instances (or other programs that connect to the internet). If this happens, you can resolve it by resetting your machine’s proxy settings to the appropriate settings or killing any hanging browser processes.
Console Settings
The Console panel allows you to determine the amount of information that is reported to the Console view and whether it is automatically activated when it contains messages.
...
If you have Continuous Testing Platform (CTP) and a valid license, you can configure your connection to CTP:
- 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.
Global Data Source Settings
Global data sources can be reused and shared across Virtualize deployments. The Global Data Source panel lets you determine how information about global data sources is saved. For information on how to configure global data sources, see Adding a Data Source at the Responder Suite, Project, or Global Level.
Technical Support Settings
Use the Technical Support interface to create a zip archive containing the related files if you are experiencing issues. Send the zip file to Parasoft's support team so that they can assist you.Virtualize can automatically create an archive when problems occur. Archives are approximately half a megabyte and are created in about 60 seconds.
By default, an archive is not created when problems occur. You can either manually prepare and send a support archive when needed, or you can modify Parasoft archive creation options so that the product automatically prepares and sends an archive when problems occur.
To configure the product to automatically prepare and send archives when problems occur:
- Open the Technical Support panel by choosing Parasoft> Preferences, then selecting the Parasoft> Technical Support category.
- Check Enable auto-creation of support archives.
- Customize additional options as needed. Note that Enable auto-creation of support archives and Send archives by email are not applicable to Virtualize.
- Click Apply, then OK.
To manually create a support archive:
- Choose Parasoft> Preferences and click the Technical Support category
- Choose your archive options and click Create Archive.
To open the Technical Support Archive Manager, which allows you to review, e-mail, or delete recent support archives:
- Choose Parasoft> Preferences and click the Technical Support category
- Click Browse Recent Archives.
Enabling Debug Logging
You can add the following system properties when starting Virtualize from the command line to enable debug logging and to ensure that the all relevant information is included when creating a support archive.
| Scroll Table Layout | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Specifies the preconfigured JAR file shipped withVirtualize that contains logging settings. This is the recommended property to use for enabling logging.
Example:
| No Format |
|---|
-J-Dparasoft.logging.config.jar.file=/com/parasoft/xtest/logging/log4j/config/verbose.console.xml |
(in the Browser Playback tool, Browser Contents Viewer, Browser Data Bank, and Browser Validation tool). This is desirable if you want to create validations/extractions in hidden iframes. This mode will significantly slow down recording and playback. Moreover, it will significantly increase .tst file size if your application uses hidden iframes.
Fetch content for all content except hidden frames: Choose this option if you do not need to see the contents of hidden frames in the pre- and post-action HTML viewer.(in the Browser Playback tool, Browser Contents Viewer, Browser Data Bank, and Browser Validation tool). In this mode, the browser will still retrieve all frames from the server and it can still perform validations and extractions on the hidden iframes. However, it will not display the contents of hidden frames in the pre- and post-action HTML viewer.
Proxy Configuration Details
When you record or run web scenarios in a browser, the proxy settings in the browser are set to an internal proxy maintained by SOAtest and/or Virtualize. All communication to and from the browser during recording and playback goes through the internal proxy, which is an intermediary used to capture traffic and otherwise facilitate execution. During recording and playback, SOAtest and/or Virtualize temporarily creates this proxy on localhost using the port specified by the Browser Playback setting’s Proxy port option.
The default host and port for the internal proxy is localhost:55555. Change the port number if this port is already in use using the controls Proxy port field. Do not change this from within the browser.
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 Proxy Settings.
Internet Explorer Notes
SOAtest and Virtualize modify the global registry settings prior to starting its instance of the browser. If an instance of Internet Explorer was running on the machine prior to launching SOAtest or Virtualize (not recommended), the global registry settings will not be set in the existing browser instance.
In these cases, check the Internet Options panel in the existing browser instance while a web scenario is running to verify that the settings point to SOAtest’s or Virtualize's proxy and click OK in the Internet Options panel. If you click OK, the proxy settings are updated in the existing browser instance. If you click Cancel, or do not go to the Internet Options panel, then the existing browser instance never picks up the proxy settings and should continue to navigate fine.
Proxy settings may not be reset properly if the browser exited abnormally, if there is a hanging browser process, etc. Such issues can affect new browser instances (or other programs that connect to the internet). If this happens, you can resolve it by resetting your machine’s proxy settings to the appropriate settings or killing any hanging browser processes.
Console Settings
The Console panel allows you to determine the amount of information that is reported to the Console view and whether it is automatically activated when it contains messages.
Continuous Testing Platform Settings
| Anchor | ||||
|---|---|---|---|---|
|
If you have Continuous Testing Platform (CTP) and a valid license, you can configure your connection to CTP:
- 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.
Global Data Source Settings
Global data sources can be reused and shared outside of a single SOAtest project and across Virtualize deployments. The Global Data Source panel lets you determine how information about global data sources is saved. For information on how to configure global data sources, see Adding a Data Source at the Responder Suite, Project, or Global Level and Adding a Data Source at the Test Suite, Project, or Global Level.
Technical Support Settings
Use the Technical Support interface to create a zip archive containing the related files if you are experiencing issues. Send the zip file to Parasoft's support team so that they can assist you.SOAtest/Virtualize can automatically create an archive when problems occur. Archives are approximately half a megabyte and are created in about 60 seconds.
By default, an archive is not created when problems occur. You can either manually prepare and send a support archive when needed, or you can modify Parasoft archive creation options so that the product automatically prepares and sends an archive when problems occur.
To configure the product to automatically prepare and send archives when problems occur:
- Open the Technical Support panel by choosing Parasoft> Preferences, then selecting the Parasoft> Technical Support category.
- Check Enable auto-creation of support archives.
- Customize additional options as needed. Note that Enable auto-creation of support archives and Send archives by email are not applicable to Virtualize.
- Click Apply, then OK.
To manually create a support archive:
- Choose Parasoft> Preferences and click the Technical Support category
- Choose your archive options and click Create Archive.
To open the Technical Support Archive Manager, which allows you to review, e-mail, or delete recent support archives:
- Choose Parasoft> Preferences and click the Technical Support category
- Click Browse Recent Archives.
Enabling Debug Logging
You can add the following system properties when starting SOAtest and Virtualize from the command line to enable debug logging and to ensure that the all relevant information is included when creating a support archive.
| Scroll Table Layout | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Property | Description | ||
|---|---|---|---|
parasoft.logging.config.jar.file | Specifies the preconfigured JAR file shipped withSOAtest and Virtualize that contains logging settings. This is the recommended property to use for enabling logging. Example:
| ||
parasoft.logging.config.file | Specifies a log4j configuration file on disk. Use this system property if you have your own log4j configuration file and are unable to use the Example:
|
| Anchor | ||||
|---|---|---|---|---|
|
The Dictionary panel allows you to customize the dictionary that the Spell tool uses to identify misspelled words.
Adding Words
To add words to the dictionary:
- To add a new word, click Add, then enter it in the dialog that opens.
- To import a set of words from a text file, click Import, then specify the file that contains the set of words you want to import.
- To remove a word, select it in the list of words, then click Delete. You can select more than one word, then delete all selected words with one click.
- To export a list of words into a text file (for example, to export your User Added Words list so that your team members can import them) click Export, then indicate what file you want to contain the exported words.
| Tip | ||
|---|---|---|
| ||
You can also add reported misspelled words to the dictionary from the Quality Tasks view. Just right-click the reported misspelled word, then choose Add to Dictionary.
|
Adding Dictionaries
You can expand SOAtest’s built-in dictionary by extending it with additional sets of ispell-format dictionaries (such as dictionaries for language other than English, dictionaries of industry-specific terms, etc.). Each dictionary set has a name and one or more dictionaries.
To add an additional dictionary set:
- Save the dictionaries in the SOAtest installation directory.
- Click the Add button, then use the file chooser to select the set of dictionaries you want to add.
Adding Non-Text Characters or Words Containing Non-Text to the Dictionary
By default, SOAtest treats non-text characters as white space and does not allow you to add dictionary words that contain non-text characters. If you want SOAtest to consider a designated non-text character as a valid character within a word (rather than as one unit of white space), you need to add that character to the list of allowable non-text characters. This allows you to identify spelling errors in words that contain allowed non-text characters and to add dictionary words that contain allowed non-text characters.
To add non-text characters to the list of allowable non-text characters:
- Enter them in the Allowable non-text characters field. If you want to allow multiple non-text characters, list them one after the other—do not separate them with a space character, comma, or other delimiter.
...
Specifies a log4j configuration file on disk. Use this system property if you have your own log4j configuration file and are unable to use the parasoft.logging.config.jar.file property, such as configuring server deployments.
Example:
...
MIME Type Settings
The MIME Types panel lets you add and remove MIME types. In addition, it lets you specify the location of your preferred text and XML editors and lets you specify what editor you want to use to edit all files that have a particular MIME type.
...
- Show tool descriptions: Enables/disables showing tool descriptions in applicable wizards. wizards.
Auto Beautify: Tells SOAtest to automatically beautify XML messages in the selected tool or tools (Traffic Viewer, Diff, Editor) if the message is under the specified size (10 KB is the default setting).
- Character Encoding: You can enable System default to configure SOAtest and/or Virtualize to use the default character set for the particular system being used. Enable Custom to encode characters from the list of encodings available on the JVM being used.
Save settings: Specifies what file format to use for saving project files (e.g., .pva, .pvn, .tst, .changetemplate). See Understanding the Available Project File Formats.
- 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
...
- of the file exceeds the threshold. You can then reduce the size (and prevent performance problems) by dividing it into smaller files.
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, seeProxy 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, then enter the proxy address in the Address field.
- If you want to use the same proxy server for all protocols, check the Same proxy server for all protocols check box, 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, clear the Same proxy server for all protocols check box, 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, check the Enable proxy authentication check box, then enter a valid user name 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.
HTTP proxies that do not require authentication can be used while managing remote SOAtest and Virtualize servers. HTTP proxies that require authentication will not be applied when adding a remote SOAtest or Virtualize server to the server tree.
Scanning Settings
This Scanning panel specifies settings related to how SOAtest scans Web applications. Available options include:
- Agent name: Determines the user agent that SOAtest uses to identify itself.
- FTP Log: Determines whether (and how) to create a log of FTP connections made to scan Web resources from SOAtest.
- Script options:
- Script extensions: Determines what files SOAtest considers "scripts".
- Limit the number of script items per page to: Determines the maximum number of script items per page that SOAtest will consider. If a page has more script items than the number that you allow, SOAtest will place a "red flag" icon next to the related Project tree node.
- Load JavaScript: Determines whether or not SOAtest loads JavaScript.
- Simulate JavaScript events: Determines how SOAtest simulates JavaScript events (such as opening and closing additional windows, running timers, and so on). If you choose single time, SOAtest triggers each handler once, with default arguments. If you choose multiple times, SOAtest tries to create multiple kinds of events while loading a site (in order to find new links)
- 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, then enter the proxy address in the Address field.
- If you want to use the same proxy server for all protocols, check the Same proxy server for all protocols check box, 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, clear the Same proxy server for all protocols check box, 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, check the Enable proxy authentication check box, then enter a valid user name 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.
...
- .
Scripting Settings
The Scripting panel allows you to specify properties used for custom scripts.
...
You can configure default security settings for Responders used for clients and Responders used in your projects. In most cases, the security settings can be overridden by configurations set locally in your suites:
...
Now when you invoke your tool, the required Negotiate token will automatically be generated and send as an HTTP header. Kerberos provides a mechanism to prevent so-called "replay" attacks where a user tries to provide captured duplicate credentials for a service in order to gain access to them. When performing a load test, where multiple virtual users provide the same user credentials, the KDC will respond as if a replay attack is occurring and errors will be thrown. This is expected behavior and it is uncertain at this point whether there is a work-around.
Server Certificate Settings
...
The Server panel allows you to configure the following settings for the SOAtest and/or Virtualize server. SOAtest and/or Virtualize server. The SOAtest server allows you to work with the Call Back tool and Asynchronous testing—as well as Message Stub tools integrated into end-to-end test scenarios.
Start server: Enable this option to automatically start the server when SOAtest and/or Virtualize starts up.
- Server port: Specifies the ports that the server use for HTTP/HTTPS.
...
| Tip | ||
|---|---|---|
| ||
If you want to quickly add a large number of jar files—or add jars to a headless instance of your Parasoft solution— copy them into one of the following directories within your workspace:
On a headless instance, if you want to reload the jars without having to restart SOAtest or Virtualize, call post /v<version>/preferences/systemProperties/reload from the REST API. |
...
Virtualize is automatically configured to ignore timestamps—based on the regular expression [0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}([.][0-9]{1,3})?(([+-][0-9]{2}:[0-9]{2})|Z)??
You can add or modify exclusions using the table controls. Element names are specified as exact matches or using a wildcard (*) to match everything. Values are specified as regular expressions.
UDDI Settings
The UDDI panel lets you set the UDDI inquiry endpoint, which is the endpoint that you want SOAtest to reference when performing dynamic router resolution. If you specify a UDDI registry here, the SOAP Client tool can search for a service by querying that registry using the UDDI serviceKey specified in the SOAP Client parameters. If you do not specify a UDDI registry here, you have to configure your SOAP Client tool so that the server endpoint is hard-coded as a router valueYou can add or modify exclusions using the table controls. Element names are specified as exact matches or using a wildcard (*) to match everything. Values are specified as regular expressions.
WSDL History
The WSDL panel lets you review or modify the WSDLs that have been used in tools and projects. These WSDLs will be available for selection in relevant drop-down boxes. This way, if you need to specify the same WSDL multiple times, you don’t need to constantly type it in over and over again.
...
The XML Conversion settings panel lets you register data models for fixed length messages.
For details on using this setting in Virtualize, see Fixed Length Message ResponderResponder. For details on using this setting in SOAtest, see Fixed Length Client and Fixed Length Call Back.
XML Schema History Settings
...
| Anchor | ||||
|---|---|---|---|---|
|
The XML Schema Locations panel lets you view, add, and remove schema locations.To 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 the Use namespace as location URI for Schemas option for the XML Validator tool. For more information on the XML Validator tool, see XML Validator. 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 LicenseServer. |
virtualize.license.network.host=[host] | Specifies the machine name or IP address of the machine running LicenseServer Configuration Manager. If your server uses the HTTPS protocol, prepend Example:
|
virtualize.license.network.port=[port] | Specifies the LicenseServer port number. Example:
|
virtualize.license.network.user=[username] | Specifies the username for authentication on the secondary DTP server specified with the This options 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.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. |
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 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 |
...
- If you will be using a custom edition license, define the appropriate license features in the localsettings as follows:
[product].license.custom_edition_features= All enabled features
Note that license feature settings apply only to custom edition licenses. Define the main license settings in the localsettings 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 number
If your server uses the HTTPS protocol, prepend
https://to the hostname.
Here are several examples of properly-configured license settings in localsettings file:
...