Browser Settings

The Browser panel lets you set options related to Web scenario recording=
. Available settings include:

Firefox ExecutablePath: Specifies=
the path to the Firefox executable. On Windows machines, SOAtest and/or Vi=
rtualize 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 Chro=
me executable. Paths set here will be used in web recording wizards and oth=
er applicable areas. On Linux, choose google-chrome (e.g. /opt/google/chrome/google-chrome)=E2=80=94not chrome.=

Browser Timeout Settings: Specifies the length of d=
elay (in milliseconds) after which SOAtest and/or Virtualize should st=
op waiting for browser startup or a user action and consider it to be "time=
d 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 oc=
cur and consider it to be "timed out."

Debug Options> Print debugging information: Duri=
ng 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 infor=
mation about what events SOAtest and/or Virtualize handled, any locato=
rs that may have been generated, and if applicable, any exceptions that too=
k place during recording.

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 allow=
ed.

Browser Contents Viewer Rendering Engine: Enables y=
ou to specify what browser is used for the Browsear Contents Viewer tool(de=
scribed in Browser=
Contents Viewer) , which can be attached to the Browser Play=
back tool.

The default option (Same browser used for playback) is=
generally the recommended option because some web applications generate th=
eir pages differently based on the browser used. Using the same browser tha=
t was used during the playback can help ensure that pages display properly =
in the Browser Contents Viewer. Note that if the playback browser was Chrom=
e, 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 r=
unning SOAtest and/or Virtualize. The Internet Explorer option is avai=
lable only on Windows.

When Firefox is selected, the version of Firefox th=
at 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 wh=
at 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 u=
se either Internet Explorer or Firefox specifically (rather than use the de=
fault Same browser used for playback option) to see if usi=
ng a specific rendering engine will improve how the page is shown in the Br=
owser Contents Viewer.

HTML Content Fetch Mode: Enables you to determine w=
hether the contents of hidden frames are displayed in the pre- and post-act=
ion 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=E2=80=99s S=
OAtest and/or Virtualize machines (e.g., desktop installation), and a diffe=
rent mode on others (e.g, the Server machine running in command-line mode).=

Fetch all HTML content Choose this option if you wa=
nt to see the contents of hidden frames in the pre- and post-action HTML vi=
ewer (in the Browser Playback tool, Browser Contents Viewer, Browser D=
ata Bank, and Browser Validation tool). This is desirable if you want to cr=
eate validations/extractions in hidden iframes. This mode will signific=
antly slow down recording and playback. Moreover, it will significantly inc=
rease .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, Bro=
wser Contents Viewer, Browser Data Bank, and Browser Validation tool). In t=
his mode, the browser will still retrieve all frames from the server and it=
can still perform validations and extractions on the hidden iframes. Howev=
er, it will not display the contents of hidden frames in the pre- and post-=
action HTML viewer.

Proxy Configuration Detail=
s

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 p=
layback, SOAtest and/or Virtualize temporarily creates this proxy on l=
ocalhost using the port specified by the Browser Playback setting=E2=80=99s=
Proxy port option.

The default host and port for the internal proxy is localhost:55555. Cha=
nge 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 configur=
e SOAtest and/or Virtualize to point to that proxy. This enables SOAte=
st and/or Virtualize to configure its internal proxy to forward all traffic=
to the specified proxy configured in Proxy Settings.

Internet Expl=
orer Notes

SOAtest and Virtualize modify the global registry settings prior to star=
ting its instance of the browser. If an instance of Internet Explorer was r=
unning on the machine prior to launching SOAtest or Virtualize (not recomme=
nded), 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=E2=80=99s or Virtualize's proxy and click OK i=
n the Internet Options panel. If you click OK, the proxy s=
ettings are updated in the existing browser instance. If you click =
Cancel, or do not go to the Internet Options panel, then the exist=
ing 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 abnormall=
y, 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=E2=80=99s proxy =
settings to the appropriate settings or killing any hanging browser process=
es.

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

If you have Continuous Testing Platform (CTP) and a valid license, you c=
an configure your connection to CTP:

Global Dat=
a 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 le=
ts you determine how information about global data sources is saved.

Technical =
Support Settings

If you are experiencing problems with Virtualize, the best way to remedy=
the problem is to create a zip archive containing the related files, then =
send that zip file to Parasoft's support team. To facilitate this process, =
you can have the product automatically create an archive when problems occu=
r. On average, these archives are about half a megabyte, and are created in=
about one minute.

By default, an archive is not created when problems occur. You can eithe=
r manually prepare and send a support archive when needed, or you can modif=
y 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 archive=
s when problems occur:

Open the Technical Support panel by choosing Parasoft> Prefe=
rences, then selecting the Parasoft> Technical Support<=
/strong> category.

Check Enable auto-creation of support archives.

Customize additional options as needed. Note that Enable auto-c=
reation of support archives and Send archivesby email are not applicable to Virtualize.

When creating a support archive it is best to ensure that it contains al=
l the info which is relevant to the problem and does not contain any =
unrelated info. To ensure that detailed logs are sent to the standard outpu=
t console, add the following argument to virtualizecli:

Dictionary Settings

The Dictionary panel allows you to customize the dictionary that the Spe=
ll 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 dia=
log that opens.

To import a set of words from a text file, click Impor=
t, 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 De=
lete. 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 expor=
ted words.

Adding Words from the Quality Tasks view

You can also add reported misspelled words to the dictionary from the Qu=
ality Tasks view. Just right-click the reported misspelled word, then choos=
e Add to Dictionary.

Adding Dictionar=
ies

You can expand SOAtest=E2=80=99s built-in dictionary by extending it wit=
h additional sets of ispell-format dictionaries (such as dictionaries for l=
anguage other than English, dictionaries of industry-specific terms, e=
tc.). 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.

By default, SOAtest treats non-text characters as white space and does n=
ot allow you to add dictionary words that contain non-text characters. If y=
ou want SOAtest to consider a designated non-text character as a valid char=
acter within a word (rather than as one unit of white space), you need to a=
dd that character to the list of allowable non-text characters. This allows=
you to identify spelling errors in words that contain allowed non-text cha=
racters and to add dictionary words that contain allowed non-text character=
s.

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=E2=80=94do not separate them with a space character, comma, or other=
delimiter.

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 l=
ets you specify what editor you want to use to edit all files that have a p=
articular MIME type.

To add, edit, or remove a MIME type:

To add a MIME type, click Add MIME Type, enter the new=
MIME type in the dialog box that opens, then enter the file extensions tha=
t you want to assign to this MIME type, and (optionally) indicate the impli=
ed MIME type by checking the appropriate check boxes. If you enter multiple=
extensions for a MIME type, separate the extensions with one space charact=
er.

To edit a MIME type=E2=80=99s settings, select the MIME type whose sett=
ings you want to edit, then modify the settings as needed.

To remove a MIME type, select the MIME type that you want to remove, th=
en click Delete MIME Type.

Miscellaneous=
Settings

The Misc panel allows you to set the following miscellaneous settings:=
p>

Auto Beautify: Tells SOAtest to automatically beautify XML messages in t=
he 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&=
nbsp;to encode characters from the list of encodings available on =
the JVM being used.

Default timeout (milliseconds): Allows you to enter th=
e length of delay (in milliseconds) after which SOAtest should consider you=
r FTP, telnet, or HTTP requests to be =E2=80=9Ctimed out.=E2=80=9D The defa=
ult 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 opt=
ion and specify a file size threshold for .tst and/or .pva files in th=
e Warn on file size large than (MB) field to be notif=
ied when the size of the file exceeds the threshold. You can then redu=
ce 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 s=
cenarios (for details on this other proxy, seeProxy Configuratio=
n Details).

If Windows and IE (which use the same settings) are configured to prope=
rly use the proxy to access the relevant websites, select Use syste=
m proxy configuration.

Otherwise, select Enable pr=
oxy and manually enter the correct settings. These settings should=
be equivalent to what you would use in the browser outside of SOAtest/Virt=
ualize.

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 <=
strong>Same proxy server for all protocols check box, then enter t=
he address and port of the proxy server you want to use in the Prox=
y Address and Proxy Port fields.

If you want to use different proxy servers for different protocols, cle=
ar 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 p=
assword in the Username and Password fiel=
ds.

If you want to allow Web traffic from designated IP addresses to pass t=
hrough directly (avoiding the proxy), enter those IP addresses in the Proxy Exceptions text field. If you enter multiple addresses, u=
se 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 "fil=
e:///" followed by the file system path where the proxy autoconfiguration s=
cript lives. For example, on Windows this could be file:///c:/Users/u=
ser/scripts/proxy.pac. On Linux, it might be file:///home/machine/scripts/proxy.pac.

HTTP proxies that do not require authentication can be used while managi=
ng remote SOAtest and Virtualize servers. HTTP proxies that require authent=
ication will not be applied when adding a remote SOAtest or Virtualize serv=
er to the server tree.

Limit the number of script items per page to: Determin=
es 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 wil=
l place a "red flag" icon next to the related Project tree node.

Simulate JavaScript events: Determines how SOAtest sim=
ulates JavaScript events (such as opening and closing additional windows, r=
unning timers, and so on). If you choose single time, SOAt=
est triggers each handler once, with default arguments. If you choose multiple times, SOAtest tries to create multiple kinds of event=
s while loading a site (in order to find new links).

Scripting Setting=
s

The Scripting panel allows you to specify properties used for custom scr=
ipts.

Java: For Java, you can specify the Java home direc=
tory and the path to the javac compiler. You need to specify t=
hese parameters if you want to compile Java methods in the editor. &n=
bsp;

Note

The javac compiler is not included.

Java home: Specifies the Java installation directory.<=
/li>

Javac classpath: Specifies the Java classpath.

JavaScript: If you create scripts using Jython or Java=
Script, you can specify a script template in the Script Template field.

Script Template: Whatever code is specified in this fi=
eld will be used as the default code for inlined scripting in the language =
with which the field is associated. This is prmarily useful for setting def=
ault inputs and common global variables. Script templates apply to scripts =
used in Extension tools; they do not apply to JavaScript that runs in a bro=
wser context.

Jython: For Jython, you can specify the jython.home=
and jython.path variables. Both variables are used to locate Jython module=
s. Jython code that does not import any Jython modules can use the Jython s=
cripting support without setting either variable. If you set the jython.hom=
e and jython.path variables, you need to restart SOAtest or Virtualize befo=
re the changes will take effect.

Jython Home: Specifies the Jython installation directo=
ry. 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:Jy thon 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 sc=
ript and log an error message.

Se=
curity Settings

The Security panel allows you to set the following security settings:

Global HTTP Authentication Properties: Allows you to s=
pecify global HTTP authentication properties that can be used when configur=
ing HTTP protocols within an applicable tool. Select the Perform Au=
thentication check box and enter the Username and=
Password to authenticate the request, and select either Basic, NTLM, or Digest, f=
rom the Authentication Type drop-down list. For Kerberos, =
enter the Service Principal to authenticate the request. I=
f the correct username and password, or the correct service principal, are =
not used, the request will not be authenticated.

Trust all certificates: Enable this option to accep=
t any certificate. This is useful if you want to load pages whose certifica=
tes are not "trusted."

Use default Java cacerts: Enable this option to acc=
ept only certificates from the standard list of Java-trusted certificate ve=
ndors.

Use client keystore: Enables you to specify settings f=
or both the server side and client side certificates for SSL through the Cl=
ient Keystore options.

Important

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 d=
ownload and install the Unlimited Strength Java Cryptography Extension. For=
details, see JCE=
Prerequisite.

Keystores are specified at the test or responder suite level. If this op=
tion is selected, the following options are available in the Certif=
icate and Private Key tabs:

Certificate tab optio=
ns:

Use same key store for private key: Select if the Key =
Store contains private keys for the certificate.

Key store file: Specify the key store file by clicking=
the Browse button and using the file chooser that opens. =
If you want the path saved as a relative path (for example, to facilitate p=
roject sharing), check the Persist as Relative Path option=
.

Key store type: (Only available if the Use sam=
e key store for private key option is unselected in the Certificat=
e tab) Specify the type of Key Store being used (e.g. JKS, PKCS12, BKS, PEM=
, UBER)

Load: Click to populate the aliases with the available=
certificates/keys if the path, type, and key store password are valid.

Private key alias: Specify the private key alias.

Private key password: Specify the private key password=
.

About K=
erberos Authentication

Kerberos authentication is known as a trusted third-party authentication=
mechanism. A client requests access to a service not directly, but from an=
other service: the Key Distribution Center, which manages network-wide auth=
orization. This mechanism facilitates Single Sign-On (SSO) so that a client=
need only provide authorization credentials once in a given time period (u=
sually 8-10 hours). The authorization is granted in the form of a ticket wh=
ich can then be cached and reused throughout the granted time period withou=
t re-authenticating.

Entities in a Kerberos-protected network, such as clients and servers, a=
re known as principals. The network-space that Kerberos protects is known a=
s a realm. Microsoft's IIS (Internet Information Services) Server provides =
HTTP-based services with Kerberos through the Negotiation protocol. Other s=
erver vendors provide their own implementations of Microsoft's Negotiate pr=
otocol.

The ticket that is received upon initial authentication is known as a Ti=
cket Granting Ticket, or TGT. For example, in a Windows environment, the TG=
T is generated when first logging on to the workstation in the morning. SOA=
test and/or Virtualize authorizes itself to use a Kerberos-protected servic=
e by retrieving a user's TGT from the system cache.

Avoiding Common Kerberos Errors

For tips on common Kerberos errors and how to solve them, see http://docs.oracle.com/javase/8/docs/technotes/guides/security=
/jgss/tutorials/Troubleshooting.html.

C=
onfiguring Kerberos Authentication

Configure the following options in the Security preferences panel:

Kerberos realm: Specify the Kerberos realm associat=
ed with your network. By convention, this is typically your domain name in =
all caps (e.g. PARASOFT.COM).

Check Ticket: Click to execute a simple test to loc=
ate a cached Kerberos TGT (Ticket Granting Ticket) to grant access to the s=
ervice. SOAtest and/or Virtualize will not be able to communicate with the =
service if it cannot first locate a valid TGT.

Select the tool for which you intend to use Kerberos authentication.

Select the Transport tab and select Security=
strong> from the left pane of the Transport tab.

Configure the following options from the security panel of the T=
ransport tab:

Use Global Preferences: Select this option if you have=
authentication properties setup in Security Preferences.

Type: Select Kerberos to perform Kerb=
eros Authentication.

Service Principal: Specify the name of the service/=
server as defined in the Kerberos database (e.g. HTTP/soatest.parasof=
t.com).

Now when you invoke your tool, the required Negotiate token will automa=
tically be generated and send as an HTTP header.

Note

Kerberos provides a mechanism to prevent so-called "replay" attacks wher=
e a user tries to provide captured duplicate credentials for a service in o=
rder to gain access to them.When performing a load test, where multiple vir=
tual 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 beha=
vior and it is uncertain at this point whether there is a work-around.

JCE =
Prerequisite

In order to perform security operations that use XML Signature Verifier,=
XML Signer, or XML Encryption tools=E2=80=94or to use Key Stores=E2=80=94 =
you will need to download and install the Unlimited Strength Java Cryptogra=
phy Extension. You can do this as follows:

Install the downloaded files in into the following directory on your ma=
chine:[Parasoft Test install dir]\[Parasoft Test version number]\=
plugins\com.parasoft.xtest.jdk.eclipse.core.[platform]_[jre version]\jdk\jr=
e\lib\securityFor example:C:\Program Files\Parasoft\Te=
st\9.10\plugins\com.parasoft.xtest.jdk.eclipse.core.win32.x86_64_1.8.0.102\=
jdk\jre\lib\securityBe sure to replace the existing local_=
policy.jar and US_export_policy.jar files with the new =
ones that you downloaded.

Restart SOAtest and/or Virtualize.

Where to Install JCE Policy Files

To see exactly where Unlimited JCE policy files should be added on your =
system, look at the message shown if you view keystore settings in the pref=
erences for two-way SSL.

This "Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction =
Policy Files may need to be installed" message is displayed only if Unlimit=
ed JCE policy files are not yet installed to the JRE that is running =
on. After the files are installed properly and product is restarted, the me=
ssage will no longer be shown.

Server Settings

The Server panel allows you to configure the following settings for the =
SOAtest and/or Virtualize server. The SOAtest server allows you to wor=
k with the Call Back tool and Asynchronous testing=E2=80=94as well as Messa=
ge Stub tools integrated into end-to-end test scenarios.

Server port: Specifies the ports that the server use f=
or HTTP/HTTPS.

SOA Registry Se=
ttings

SOAtest can create tests that enforce policies applied to Web service as=
sets that are declared in a BEA AquaLogic Enterprise Repository or So=
ftware AG Centrasite repository as described in Using Oracle or BEA with SOAtest=
and Using Software AG CentraSite Active SOA with SOAtest. T=
he SOA Registry panel allows you to specify settings that SOAtest will use =
by default in forms that reference such repositories. For instance, if you =
specify settings for BEA ALER here, SOAtest will use these values by defaul=
t in the wizard for creating tests from BEA ALER.

SOAP Setti=
ngs

The SOAP panel allows you to specify the following settings:

Default Transport: Allows you to set the default trans=
port protocol.

Attachment Encapsulation Format: Allows you to choo=
se MIME, DIME, or MTOM, =
for the default attachment encapsulation. See Working with Attachments for details.=

SOAP Version: Allows you to select SOAP 1.1 or SOAP 1.2.

Outgoing Message Encoding: Allows you to choose the en=
coding for outgoing messages. You can choose any Character Encoding=
you wish to read and write files, but the Outgoing Messag=
e Encoding provides additional flexibility so you can set a differ=
ent charset encoding for the SOAP request.

Customizing SOAP Serialization Settings

You can also customize how SOAtest and/or Virtualize serialize the SOAP =
objects they transmit and deserialize the SOAP messages they receive, but y=
ou cannot do so within the Preferences panel.

SOAP messages are deserialized from XML into some native format and obje=
cts are serialized into XML format so that they can be sent as responses.=
p>

To add a serializer/deserializer pair, you add a line to th=
e register.py file in the <INSTALL_HOME>/plugins/com.parasoft.xtest.libs.=
web_<version>/root/startup directory. You must pr=
ogrammatically use Jython register Apache Axis-compliant serializers.

For Axis, you can retrieve the TypeMappingRegistry used by calling soate=
st.api.SOAPUtil.getDefaultAxisRegistry(). After you retrieve that registry,=
you can use the Axis API to register the serializer as needed.

System Properties Settings

The System Properties panel lets you add JAR files, class folders, and J=
ava projects to the classpath if needed. Use the available controls to add =
or remove JAR files, class folders, and Java projects. The specified JAR fi=
les, classpaths, and Java projects will be added to the system's clas=
spath and the corresponding classes will be loaded into the JVM after SOAte=
st or Virtualize is restarted.

Click Reload to force classes from the class path entri=
es to reload.

If you want to quickly add a large number of jar files=E2=80=94or add ja=
rs to a headless instance of your Parasoft solution=E2=80=94 copy them into=
one of the following directories within your workspace:

TestAssets/system_jars

stubs/system_jars

VirtualAssets/system_jars

Jar files in those directories will automatically be loaded upon start=
up or after
Reload is clicked in the Preferences page.

On a headless instance, if you want to reload the jars without having to=
restart SOAtest or Virtualize, call post /v<version>/preferences/sys=
temProperties/reload from the REST API.

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 endp=
oint that you want SOAtest to reference when performing dynamic router reso=
lution. If you specify a UDDI registry here, the SOAP Client tool can searc=
h for a service by querying that registry using the UDDI serviceKey specifi=
ed in the SOAP Client parameters. If you do not specify a UDDI registry her=
e, you have to configure your SOAP Client tool so that the server endpoint =
is hard-coded as a router value.

WSDL History

The WSDL panel lets you review or modify the WSDLs that have been used i=
n tools and projects. These WSDLs will be available for selection in releva=
nt drop-down boxes. This way, if you need to specify the same WSDL multiple=
times, you don=E2=80=99t need to constantly type it in over and over again=
.

Enable the Save WSDLs used in message responders, <=
/strong>SOAP clients, and projectsif you want SOAtest/Virtualize to save tests' or assets' WSDL URI=
s. If you are using SOAtest only, the option will read Save=
WSDLs used in SOAP clients and projects. If you are using Virtualize only, the option will read<=
strong> Save WSDLs used in message responders=
and projects.&nbsp=
;

The WSDL URI field lists the WSDL URIs that will b=
e available in tools=E2=80=99 WSDL URI drop down menu. By =
default, all WSDL URIs used in related tools are added to this list. Click =
on a URI in the field and click Refresh WSDL to =
refresh the WSDL from the given location URL and re-parse it.

Enable theWSDL/Schema Parsing section=
to check all schema locations in order to locate components=
belonging to a give target namespace.Disable this o=
ption to use only the first schema location encountered in order to resolve=
components for a given target namespace.

XML Schema History Settings

The XML Schema History panel lets you review or modify the XML Schemas t=
hat have been used in Messaging Clients (SOAtest), message respon=
ders (Virtualize), and projects. These Schemas will be available for select=
ion in relevant drop-down boxes. This way, if you need to specify the same =
Schema multiple times, you don=E2=80=99t need to constantly type it in over=
and over again.

XML Schema Locations Se=
ttings

The XML Schema Locations panel lets you view, add, and remove schema loc=
ations.The XML Validator tool needs to know where to find the schema that i=
t should use to validate the document of concern. In most cases this is a U=
RI and is supplied within the document being validated. If, however, the UR=
I 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 Valid=
ator 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 locati=
on:

Type in the OASIS XML Catalog Location or Browse to it=
by clicking the Browse button.

Click OK after you have added all of the necessary loc=
ations.

Virtualize Localsettings

There are two ways to define localsettings files:

Enter them manually in a simple text file simple text file. There are n=
o 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 e=
xport, choose Parasoft> Preferences, select Par=
asoft (the root element in the left tree), click the Share=
link, specify which settings you want to export.

Localsettings files can specify the following settings.

Licensing Setting=
s

Setting

Purpose

virtualize.license. use_network=3Dtrue|fal=
se

Determines whether the current installation retr=
ieves its license from LicenseServer.

virtualize.license. network.host=3D[host]<=
/code>

Specifies the machine name or IP address of t=
he machine running LicenseServer Configuration Manager.

Example:

<=
p>virtualize.license.network.host=3D10.9.1.63

virtualize.license. network.port=3D[port]<=
/code>

Specifies the LicenseServer port number.

<=
p>Example:

virtualize.license.network.port=3D2222

virtualize.license.network.ed=
ition=3D[edition_name]

Specifies the type of license that you want t=
his installation to retrieve from LicenseServer.

[edition_name]=
can be server_edition. To use a custom edition, d=
o not set anything after the "=3D"; simply leaving the value empty.

E=
xample:

virtualize.license.network.edition=3Ddesktop_edition

virtualize.license.network.edition=3Dserver_edition=

virtualize.license.autoconf.timeout=3D[sec=
onds]

Specifies the maximum number of seconds this ins=
tallation will wait for the license to be automatically configured from Lic=
enseServer. Default is 10.

virtualize.license.local.=
expiration=3D[expiration]

Specifies the local license that you want this i=
nstallation to use.

virtualize.license. local.password=3D[pass=
word]

Specifies the local password that you want this =
installation to use.

virtualize.license.wait.for.tokens.time=3D=
[time in minutes]

Specifies the time that this installation wil=
l wait for a license if a license is not currently available.

F=
or example to make it wait 3 minutes for license tokens, use vi=
rtualize.wait.for.tokens.time=3D3.

Disabled: Configures the product to use only one of th=
e available CPUs.

parallel.max_threads=3D<number>

Specifies the maximum number of paralle=
l threads that can be executed simultaneously. The actual number of pa=
rallel threads is determined based on the number of CPUs, available memory,=
and license settings.

parallel.free_memory_limit=3D<percentag=
e>

Specifies the amount of memory that should be ke=
pt free in low memory conditions (expressed as a percentage of the total me=
mory available for the application). This is used to ensure that free memor=
y is available for other processes.

parallel.no_memory_limit=3Dtrue|false

Indicates that you do not want to place any rest=
rictions (beyond existing system limitations) on the memory available to th=
e product.

tasks.clear=3Dtrue|false

Clears existing tasks upon startup in cli mode. =
This prevents excessive time being spent "loading existing results." The de=
fault is true.

security.trust.all.certificatestrue|false<=
/code>

Tells Virtualize that you want it to accept any =
certificate. This is useful if you want to load pages whose certificates ar=
e not "trusted."

security.use.default.java.cacertstrue|fals=
e

Tells Virtualize that you want it to accept only=
certificates from the standard list of Java trusted certificate vendors.=
td>

Manually Adding the License to localsetttings

To add or change license settings vialocalsettings:

If you will be using a custom edition license, define the appropriate l=
icense features in the localsettings as follows:[product].license=
.custom_edition_features=3D All enabled featuresNote that licens=
e feature settings apply only to custom edition licenses.