To load site-wide properties automatically from a DevTest registry, uncomment this property and make it the right URL to your DevTest registry. The hostname/lisa.TestRegistry property usually works. Your properties in this file override any properties that are defined at the site level.
To load site-wide properties from a DevTest registry automatically, uncomment this property and make it the right URL to your DevTest registry. The hostname/lisa.TestRegistry usually works. Your properties in this file override any properties that are defined at the site level for non-GUI components.
DevTest Workstation does not use this property. You can select the registry that you want to connect to with the Select Registry dialog or by the Change Registry button in the workstation. If you disable the "prompt on startup" check box in the Select Registry dialog, then DevTest Workstation connects to the last registry that it was using.
Format: tcp://somehost/Registry
Format: https://license.itko.com
Format: iTKO/LISA/YOURCO
Format: YOURUSERNAME
Format: YOURPASSWORD
Lets you override the directory where run-time files are managed. Set this property to an absolute directory path. If you do not start the path with a drive specification, it becomes relative to LISA_HOME. If you are specifying a multilevel directory, specify in this format: C:\\Temp\\myVSE.
Note: In properties files, you MUST double backslashes for them to be recognized.
The valid values are the list of VSE SI text editor class names that are found in typemap.properties assigned to the vseTextBodyEditors name. If you write a custom text editor and make it available through standard SDK methods, that class name can also be a value for this property.
The following properties let VSE use old-style socket I/O rather than new I/O ("NIO"). Be aware of the following restrictions when using old style socket support:
Setting this property to false causes both plain and SSL sockets to use old-style I/O.
Default: true
This property controls only plain sockets.
Default: sa.vse.tcp.uses.nio
This property controls only SSL sockets.
Default: isa.vse.tcp.uses.nio
Default: EFFICIENT
Defines the size in bytes of cache values that are allowed to persist in specific caches.
Default: 1024 * 1024 * 2 (2 MB)
When set to false, DevTest stops the collection of periodic samples that calculate Response Time, Forced Delay, and Transactions per Second. The rest of the metrics data that is tracked in the VSE_METRICS_TXN_COUNTS table is still captured to produce the charts for the following items:
When set to false, these items in the charts list on the VSE Console do not show any data:
Default: true
Lets you configure the number of errors that cause a VSE service to stop.
Errors are still reported in the VSE console with a red circle and an error count, regardless of the value of this property.
To designate the number of errors that cause the service to stop, enter a valid number, 0 or greater. A value of 0 means that no errors are allowed; the service shuts down after the first error.
To designate an unlimited number of errors, enter any negative number.
If you enter an invalid value or no value, the default number of 3 errors is used.
Default: 3
Note: Depending on the type of error and model, the final error count can be greater than the value set in lisa.vse.max.hard.errors. Shutting down the virtual service can take some time. While the shutdown is in process, some types of errors can continue to increase.
Specifies if sockets are closed immediately at the end (or termination) of a TCP recording.
Both local (listen port) and remote sockets are affected.
If a socket read or write is in progress (if there is a long delay by server or client) and recording is terminated, then this property specifies whether to close or to let the communication complete.
For long running conversations (for example, large file downloads) this property specifies whether to terminate the conversation or let it run until the end.
Values: blank, true, and false. If the value is blank, the value defaults to true.
Default: true
Specifies the amount of memory that is set aside to cache the uncompressed body for VSE request and response objects. Units are in MB.
Default: 10
Specifies the length of time cached uncompressed bodies of VSE requests and responses remain in the cache. Units are in seconds.
Default: 60
This property tells VSE to allow leading or trailing whitespace, or both, on incoming request arguments when matching to a service image. The default value is false, which causes VSE to strip off leading and trailing whitespace on incoming request arguments before matching the request to a service image.
Default: false
These properties define the IMS Connect message parameters for the protocol to use for recording and playback purposes.
Default: EBCDIC
Default: 80
If an existing session cannot be found, VSE attempts to match the request against the starter transactions of each conversation in the image. If a match is found, a new session is created and the relevant response is returned. The session is maintained until 2 minutes after it has last been "seen" by VSE. You can change this behavior by setting lisa.vse.session.timeout.ms. If no conversation starters match, no session is created and the list of stateless transactions is consulted in the order they are defined. If there is a match, the appropriate response is returned. If there is still no match, the "unknown request" response is sent.
Default: 120000
Controls the period that we wait for a TCP read to be satisfied before timing out and running retry logic. Its default setting of 500 milliseconds is sufficient for "normal" or well-tuned networks where network latency is not an issue. For networks experiencing delays longer than 1/2 a second, you can set this property to allow the code to wait for a longer time before retrying. The retry logic should be sufficient for communications on the TCP socket to be maintained at the loss of some throughput (a lower number of transactions per second).
NIO must be turned off for the lisa.vse.tcp.oldio.read.timeout property to work. Set lisa.vse.ssl.tcp.uses.nio=false.
Default: 500
VSE supports unrecorded back navigation during playback in a conversational transaction. Set this property to true to enable back navigation for all services. The conversational session then tracks received requests and allows any next request to be one of the previous ones.
Default: false
Defines how long to keep session tracking information, in hours.
Default: 8
Indicates the existence of the 4-byte IMS Connect LLLL length field in the request payload. A value of true includes the LLLL field. A value of false excludes it.
Default: false
Indicates the existence of the 4-byte IMS Connect LLZZ length field in the request payload. A value of true includes the LLZZ field. A value of false excludes it.
Default: false
Instructs the protocol to generate the 4-byte IMS Connect LLZZ length field in the response messages. A value of true creates the LLZZ field. A value of false does not create it.
Default: true
The Enterprise Dashboard database is used for the DevTest Solutions Usage Audit Report data, registry status and component information, historical event logs, and historical component metrics.
The Enterprise Dashboard database is not able to reside in the same database schema as a registry database. We recommend that the database have at least 50 GB of storage.
Derby is not supported in a distributed environment.
The Enterprise Dashboard does not support IBM DB2.
Because the site.properties is handled solely by a registry process, a custom Enterprise Dashboard database must be configured in the local.properties file.
These are the properties that DevTest uses to connect to the Enterprise Dashboard database. The default connection is to the internal Derby database. For information about connecting to external databases, see "External Database Configuration".
Oracle Properties
Default: oracle.jdbc.driver.OracleDriver
Default: jdbc:oracle:thin:@[HOST]:1521:[SID]
Default: [USER]
Default: [PASSWORD]
MS SQL Server Properties
Default: com.microsoft.sqlserver.jdbc.SQLServerDriver
Default: jdbc:sqlserver://[SERVER]:[PORT];databaseName=[DATABASENAME]
Default: [USER]
Default: [PASSWORD]
MySQL Properties
Default: com.mysql.jdbc.Driver
Default: jdbc:mysql://[DBHOST]:[DBPORT]/[DBNAME]
Default: [USER]
Default: [PASSWORD]
Derby Properties
Default: common
Default: org.apache.derby.jdbc.ClientDriver
Default: jdbc:derby://localhost:1530/database/dradis.db;create=true
Default: app
Enterprise Dashboard Pool Properties
Default: dradis
Default pool properties to keep the number of connections to a minimum if we are idle.
Default: 0
Default: 0
Default: 10
Default: 1
Default: 45
Default: 5
Should the internal Derby database instance in the Enterprise Dashboard be started?
Controls whether the Enterprise Dashboard starts an internal Derby database. If you configured to use an external database, you can save resources by setting this property to false.
Default: true
Default: {{LISA_HOME}}webreckeys.ks
Default: passphrase
DevTest to DevTest communication encryption. Normally the network traffic is not encrypted. To use encryption, we support SSL out of the box. Instead of naming your server endpoints with "tcp," name them with "ssl" - for example: ssl://hostname:2010/Registry. You do not have to set any of the following properties; simply naming the endpoints (and the server name) with SSL is enough. For example, you can start a new simulator:
Simulator -name ssl://thishost:2014/Simulator -labName ssl://regHost:2010/Registry
We provide a default internal self-signed certificate (in LISA_HOME\webreckeys.ks). For a stronger certificate, specify the lisa.net.keyStore property and the plaintext password in lisa.net.keyStore.password.
The next time DevTest starts, an encrypted string (lisa.net.keyStore.password_enc) replaces the plaintext password.
Default: {{LISA_HOME}}lisa.ks
This is where we keep our identification certificate. If we are a server installation, this is the certificate that clients need to add to their list of trusted servers. If we are a client installation and we are doing mutual (client) authentication, this is the certificate that needs to be added to the truststore on the server side. If we are a client installation that is not using mutual authentication, then you do not need to specify this.
Default: {{LISA_HOME}}lisa.ts
Default: 079f6a3d304a978146e547802ed3f3a4
This is where we keep trusted certificates. If we are primarily a client installation, this holds a list of trusted servers. If we are a server installation and we are doing mutual (client) authentication, this is where we put trusted client certificates.
Indicates whether to use mutual authentication.
Default: false
Values: SSL or TCP
Default: SSL
Default: ssl
Default: true
Defines the proxy server, in the format my_proxyserver.com.
If your proxy server requires credentials, leave blank to use the native NTLM authentication.
Default: 3128
Defines the proxy domain, if needed for NTLM.
Optional
Optional
If there is a license error, send an email. Refer to the following example. Replace mailhost with the hostname of your mail host. Replace recipient@mycompany.com with the target email address. Replace from@mycompany.com with the email address from which the email is sent.
Example: mailhost,recipient@mycompany.com,from@mycompany.com
The DevTest SDK examples require:
Format: com.mycompany.lisa.AssertFileStartsWith
Format: com.itko.lisa.editor.DefaultAssertController,com.itko.lisa.editor.DefaultAssertEditor
Format: com.mycompany.lisa.FilterFileFirstLine
Format: com.itko.lisa.editor.FilterController,com.itko.lisa.editor.DefaultFilterEditor
Format: com.mycompany.lisa.node.FTPTestNode
Format: com.mycompany.lisa.node.FTPTestNodeController,com.mycompany.lisa.node.FTPTestNodeEditor
Change the default behavior for validating the SSL certificates.
A value of "true" says to validate the validity dates for the certificate.
Default: false
A value of "true" says to validate the cert revocation list that is specified in the certificate.
Default: false
Enable a client cert and password for SSL (used by HTTP step and Raw SOAP step; also used by Web Service step if not overridden).
A full path to the keystore.
The password for the keystore. This password is automatically encrypted when DevTest runs.
An optional password for the key entry if using a JKS keystore and key has a different password from keystore. This password is automatically encrypted when DevTest runs.
Override the client certificate and password for SSL (ssl.client.cert.path and ssl.client.cert.pass) for Web Service step.
A full path to the keystore.
The password for the keystore. This password is automatically encrypted when DevTest runs.
An optional password for the key entry if using a JKS keystore and key has a different password from keystore. This password is automatically encrypted when DevTest runs.
These credentials are automatically encrypted when DevTest runs. To reset the values, use the unencrypted property names. To use the native NTLM authorization (Windows only), leave these settings commented out.
The domain name; use this option for NTLM.
Username
Password
Preemptively send the authorization information rather than waiting for a challenge.
Values: basic, ntlm, negotiate
Default: ntlm
NTLMv2 is used by default but by setting this property to true it can be forced to use NTLMv1 when not using native integrated Windows authentication.
Default: true
The location of the login configuration file.
The location of the Kerberos configuration file that would be used to override any preset locations.
The name of the principal to be used for the login when using DevTest support for principal and password authentication. This parameter is encrypted when DevTest Workstation is started.
The password to be used for the login when using DevTest support for principal and password authentication. This parameter is encrypted when DevTest Workstation is started.
The machine name or IP address.
The machine name or IP address to exclude from proxy authentication. To enter multiple values, delimit values with pipes ( | ). Use * as a wildcard.
Default: 127.0.0.1
The machine name or IP address.
The machine name or IP address to exclude from SSL proxy authentication. To enter multiple values, delimit values with pipes ( | ). Use * as a wildcard.
Default: 127.0.0.1
Leave blank to use integrated NTLM authentication.
Used for NTLM authentication.
Exclude simple host names from proxy use.
Default: true
Preemptively send authorization information rather than waiting for a challenge.
Values: basic, ntlm
Default: ntlm
HTTP Timeout (in milliseconds) - To extend the timeout to wait indefinitely, set the values to zero.
Default: 15000
HTTP Timeout (in milliseconds). To extend the timeout to wait indefinitely, set the value to zero.
Default: 180000
lisa.toxml.serialize.mode=NOREFERENCES
NOREFERENCES means a simple tree is rendered. Circular references are not allowed. XPATHREFERENCES means the XPATH notation is used for references. Circular references can be used. If there is a circular reference, we fall back to XPATHREFERENCES. However, any serialization before version 3.6 that is re-read fails and could require you to set a default of XPATHREFERENCES.
lisa.ui.admin.tr.control=no
lisa.ws.jms.SoapAction.quoted=false
SOAP over JMS with TIBCO BusinessWorks/Active Matrix: BW/AM requires that the SOAPAction header is quoted.
When DevTest serializes a date, time, or dateTime, it uses the following formats by default. To change the default formats/time zone, use these properties. You can also dynamically set them during the test case. You can set the format to one that does not comply with the XML schema specification. However, doing so is not recommended (except for a negative test case).
lisa.ws.ser.dateFormat=yyyy-MM-dd
lisa.ws.ser.timeFormat=HH:mm:ss.SSS'Z'
lisa.ws.ser.timeFormat.timeZone=GMT
lisa.ws.ser.dateTimeFormat=yyyy-MM-dd'T'HH:mm:ss.SSS'Z'
lisa.ws.ser.dateTimeFormat.timeZone=GMT
ws.raw.format=true
To format the SOAP response for RAW Soap Steps, set this property to true. This formatting can also be done dynamically at run time.
lisa.ws.endpoint.fullautoprop=false
The entire WS Endpoint URL is automatically converted into a single DevTest property. To convert the URL to use the WSSERVER and the WSPORT properties, set this property to false.
stats.unix.xml.folder={ {LISA_HOME } }/umetrics
lisa.ipspoofing.interfaces=2-34-56-78-90-AB, eth0, Realtek PCIe GBE Family Controller
Interfaces: a comma-separated list of interfaces that is used for the IP spoofing. These interfaces can be named using the MAC address (JDK 1.6+), interface name, or interface display name.
lisa.ui.useNativeFileDialog=true
Force the use of a native file dialog.
Specify the maximum number of recent items to show in the Prefill combo boxes (no less than 10).
Default: 10
Specify the maximum number of recent items to show in the Open Recent Quick Start tab (no less than 5).
Default: 5
Default: /lisa-invoke
Default: /reports
Default: lisa.tmpdirlisa.portal.invoke.report.url
Default: d:/lisatests/
This value must be the external IP address or DNS name for the registry to be accessible remotely. This parameter is referenced in the relevant connection properties. If the value is left at "localhost," it is automatically overridden in the external IP address of the registry server when sent to connecting applications.
Default: localhost
Normally the network traffic is not encrypted. SSL encryption is supported out of the box. Instead of naming your server endpoints with "tcp," name them with "ssl": for example, ssl://hostname:2010/Registry. You do not have to set any of the following properties: naming the endpoints (and the server name) with ssl is enough. For example, to start a new simulator: Simulator -name ssl://thishost:2014/Simulator -labName ssl://regHost:2010/Registry.
LISA_HOME\webreckeys.ks is a default internal self-signed certificate. For a stronger certificate, specify the lisa.net.keyStore property and the plaintext password in lisa.net.keyStore.password. The next time DevTest starts, an encrypted string lisa.net.keyStore.password_enc replaces the plain text password.
lisa.default.keystore={{LISA_HOME}}webreckeys.ks
lisa.default.keystore.pass=passphrase
Where the identification certificate is kept. For a server installation, this value is the certificate to add to the list of trusted servers. For a client installation doing mutual (client) authentication, this value is the certificate to add to the truststore on the server side. For a client installation that is not using mutual authentication, you do not need to specify this parameter.
lisa.net.keyStore={{LISA_HOME}}lisa.ks
lisa.net.keyStore.password=PlainTextPasswordWilBeConvertedToEncrypted
Where trusted certificates are kept. For a primarily client installation, this field holds a list of trusted servers. For a server installation doing mutual (client) authentication, this field is where to put trusted client certificates.
lisa.net.trustStore={{LISA_HOME}}lisa.ts
lisa.net.trustStore.password_enc=079f6a3d304a978146e547802ed3f3a4
Whether or not to use mutual authentication.
lisa.net.clientAuth=false
Defines the default protocol for ActiveMQ connections. The default is tcp.
lisa.net.default.protocol=tcp
If you are experiencing agent errors and you are not licensed for the DevTest agent, consider turning it off here.
Default: false
The string-value is supplied by a data set such as the Unique Code Generator.
A run-time value that sets the correlation ID for an outgoing MQ message.
Default: string-value
A run-time value that sets the correlation ID as a byte[] for nonprintable values.
Default: byte[]
A run-time value that sets the message ID for an outgoing MQ message.
Default: string-value
A run-time value that sets the message ID as a byte[] for nonprintable values.
Default: byte[]
The string-value is often supplied by a data set such as the Unique Code Generator.
A run-time value that sets the JMSCorrelationID for an outgoing JMS message.
Value: string-value
A run-time value that sets the time-to-live for an outgoing JMS message.
Value: num-value
A value of true auses the JMS step to always close the JNDI context at the end of its execution.
Values: true, false
If too many errors are reported in a test, the coordinator uses up all its available heap space. When the heap space is used up, DevTest Server must be restarted. This situation is bad if multiple tests are running, and one test gets staged and throws nothing but errors. This property limits the size of the coordinator failure list.
Default: 15
To view the full text of long responses, set this property to the length of your longest response. Run your test, capture what you need, verify that the correct response is indeed being sent back, and then comment out the added line in the local.properties file to revert to the default length.
Default: 1024
Forces the communication through a specific NIC on the computer.
Value: IP address of selected NIC
This property configures whether the XPath local-name() function is always used during XPath generation. The default value is false, meaning that the local-name() is only used when necessary. To generate an XPath that works regardless of the namespace of an XML node, set the value of this property to true.
Default: false
To capture the information that is necessary to populate the Cumulative HTTP Traffic Summary report, enter this property into one of the custom property files.
Default: true
The property to designate the size at which the view of an XML response in an editor or in the ITR is plain and no DOM view is provided.
Default: 5 MB
Default: 10
These properties were added to make the report cleanup thread run more often. The first is the initial delay, in minutes, before the cleaner starts. The second is the time between runs, in minutes.
Default: 60
Set to limit the number of errors that are reported to prevent the report generator from backing up.
Default: 50
Initialization of the Metric Collector occurs during the staging of the test/suite and the test/suite does not start until the collectors are initialized. The default value of 90000 means that initialization times out after 90 seconds (for each collector).
Default: 90000
When the graphical XML diff displays an error, this property controls how many lines before and after the differing lines are displayed. The default is two lines before and two lines after.
Values: 0, 1, and 2.
Default: 2
There is a small sleep() just before the dashboard refreshes at end-of-test. The sleep() allows a timeslice for the metric collectors to wrap up their work. Adjust the timeslice with this property.
Format: milliseconds
Designates the default scripting language to use.
Values:
Default: beanshell
All the user session lifetimes in different DevTest modules are configurable with properties.
The ACL session-related properties and their default values are:
The registry.max.user.lifetime.seconds property is the main session lifetime property that determines how long a user session is valid after the last activity done by a user in a session.
Specifies how many seconds the SSO security token is kept in memory for DevTest Workstation to bypass authentication for DevTest console web applications (for example: reporting, CVS, CAI, Server Console), the DevTest Portal, and DevTest Workstation.
When you click a button to access a console web application, DevTest bypasses ACL authentication by using an SSO security token. That SSO security token is stored in memory for reuse. However, if DevTest Workstation is idle for 20 minutes (or the number of seconds specified for this property) that SSO security token becomes expired. It then requires reauthentication. If you start DevTest Workstation, you can click these buttons and go directly to the web application without entering a userid and password. But after DevTest Workstation is idle (no activity) for 20 minutes, if you click these buttons, DevTest Workstation will prompt for a userid and password to proceed so that a new security token is kept in memory again.
Default: 1200
The following modules have a user session lifetime, but they always communicate with the registry to decide if the session is still alive.
vse.max.user.lifetime.seconds=1200
console.max.user.lifetime.seconds=1200
coordinator.max.user.lifetime.seconds=1200
simulator.max.user.lifetime.seconds=30
The console refresh interval can be configured with the following property.
lisa.portal.server.console.polling.interval.seconds=5
The interval at which the DevTest Console checks whether the current session is valid and is not expired.
user.session.check.interval.seconds=60
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|