Skip to content
DevTest Solutions - 10.3
Documentation powered by DocOps

Local Properties File

Last update March 28, 2019

The properties in the local.properties file take precedence over the lisa.properties and site.properties files.

Autoconnection Properties

  • lisaAutoConnect
    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

License Properties

  • laf.server.url
    Format: https://license.itko.com
  • laf.domain
    Format: iTKO/LISA/YOURCO
  • laf.username
    Format: YOURUSERNAME
  • laf.password
    Format: YOURPASSWORD

VSE Properties

  • lisa.vse.deploy.dir
    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.
  • lisa.vse.si.editor.prefer.xml
    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:

  • The ability of VSE to handle being a proxy in front of SSL automatically cannot be supported. The solution is to create a VSM that is in Live System mode and points to the actual virtual service, with SSL turned on.
  • The ability of VSE to handle plain text traffic, even when the listen step has been configured to use SSL, cannot be supported. The solution is to provide two virtual services, one with SSL configured and one without SSL configured.
  • Using old style socket support does not scale as efficiently as the default socket support VSE uses.

  • lisa.vse.tcp.uses.nio
    Setting this property to false causes both plain and SSL sockets to use old-style I/O.
    Default: true
  • lisa.vse.plain.tcp.uses.nio
    This property controls only plain sockets.
    Default: sa.vse.tcp.uses.nio
  • lisa.vse.ssl.tcp.uses.nio
    This property controls only SSL sockets.
    Default: isa.vse.tcp.uses.nio
  • lisa.vse.execution.mode
    • EFFICIENT uses the most efficient path through a VS model.
    • TRACK records VSE activity at the VS level.
    • LIVE routes requests received by a VS model to a live system (somewhat like a pass through mode).
    • VALIDATION uses both VSE and the live system to determine a response. Both are recorded as tracking information and feed the model healing process. The live response becomes the response of the virtual service.
    • DYNAMIC invokes a script or subprocess for every request that must resolve to one of the other four modes. This approach is useful for tracking requests that only the virtual service model sees.
    • LEARNING automatically "heals" or corrects the virtual service to have the new or updated response from the live system.
    • STAND_IN first routes a request to the virtual service (the same as Most Efficient mode). However, if the virtual service does not have a response, the request is then automatically routed to the live system.
    • FAILOVER first routes a request to the live system (the same as Live System mode). However, if the live system does not have a response, the request is then automatically routed to the virtual service.
    Default: EFFICIENT
  • lisa.vse.body.cache.weight
    Defines the size in bytes of cache values that are allowed to persist in specific caches.
    Default: 1024 * 1024 * 2 (2 MB)
  • lisa.vse.metric.collect
    When set to false, DevTest stops the collection of periodic samples that calculate Response Time, Forced Delay, and Transactions per Second. The remainder 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:
    • Server Charts
    • Total Lifetime Transactions
    • Daily Transaction Counts
    • Server Availability
    • Service Charts
    • Total Transactions per Day.
    When set to false, these items do not show any data:
    • Service Charts
    • Transaction Throughput
    • Transaction Hits and Misses
    • Response Time
    • Forced Delay
    • Transactions per second.
    Default: true
  • lisa.vse.max.hard.errors
    Lets you configure the number of errors that cause a VSE service to stop.
    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.
  • lisa.tcp.tcprecorder.close.immediately
    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
  • lisa.vse.body.cache.size
    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
  • lisa.vse.body.cache.timeout
    Specifies the length of time cached uncompressed bodies of VSE requests and responses remain in the cache. Units are in seconds.
    Default: 60
  • lisa.vse.argument.match.allow.whitespace
    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.

  • lisa.vse.protocol.ims.encoding
    Default: EBCDIC
  • lisa.vse.protocol.ims.header.length
    Default: 80
  • lisa.vse.session.timeout.ms
    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
  • lisa.vse.tcp.oldio.read.timeout
    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
  • lisa.vse.conversational.back.navigation.allowed
    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
  • lisa.vse.tracking.delete.data.age
    Defines how long to keep session tracking information, in hours.
    Default: 8
  • lisa.vse.protocol.ims.response.includes.llll
    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
  • lisa.vse.ims.connect.llzz.request
    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
  • lisa.vse.ims.connect.llzz.response
    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
  • lisa.vse.http.server.lookup.client.names
    Controls whether we do reverse DNS lookup on our clients.
    Values: true, false
    Default: false
  • lisa.vse.performance.enabled
    Specifies whether to enable CA Service Virtualization performance mode.
    Values: true, false
    Default: false
  • lisa.vse.http.response.allowNonStandardResponseCode
    Allows for non-standard response codes when using the HTTP virtual service.
    Values: true, false
    Default: false
  • lisa.baseline.cache.timeout.seconds

    After baselines are created, they are maintained in cache for a short period to allow time for our web-based applications to retrieve them. The length of time they remain in cache is managed with this property,

    Default: 60 seconds

  • lisa.baseline.cache.maximum.entries

    Determines which baselines to evict when the cache size becomes larger than desired. This property does not ensure a maximum size, it only provides a suggested size limit to the cache manager.  When this size limit is reached, the cache manager considers the least-recently accessed baseline for eviction.

    Default: 100

  • lisa.baseline.conversationThread.maximumTransactions

    Baselines of virtual services support the concept of "conversation threads." Every stateful conversation in a service image starts with a single transaction that defines a "start node". This start node has branches to other transactions, those transactions lead to others, and so on, yielding a hierarchy of transactions.

    Each path from a start node to a leaf node constitutes a "conversation thread". Each conversation thread yields one baseline test case. Usually, these conversation threads are not long and contain only a handful of transactions. Inevitably, pathological cases arise, and these pathological cases have the potential of introducing runtime errors such as Out Of Memory exceptions and Stack Overflow exceptions. To mitigate these problems, this property can be set to limit the number of transactions that are allowed in a single conversation thread.

    With the default, the first 100 transactions in a conversation thread are included in the baseline test, and the remaining transactions along that thread are ignored.
    Default: 100

  • com.itko.lisa.vse.sio.loggerName
    Enables NIO session logic to log higher levels of state information during playback. This logging is at the TRACE log level instead of the INFO level of the current logging. In order to turn on NIO traces, make this property value NIOSession. To see the higher-level traces, add log4j.logger=NIOSession to the logging.properties file.
  • lisa.vse.close_socket_after_response.enabled
    TCP-specific property to control whether or not the lisa.vse.close_socket_after_response metadata property is set when recording responses or handling live responses. The lisa.vse.close_socket_after_response metadata property instructs the VSE whether or not to close the socket after sending back a particular response during playback.
    When recording live TCP traffic, we set the lisa.vse.close_socket_after_response metadata property on a response if (and only if) it the system we are recording traffic from closed its socket after sending it. It also applies to the TCP Live Invocation Step, where we will the lisa.vse.close_socket_after_response metadata property on a response if (and only if) it the live system closed its socket after sending it. If the lisa.vse.close_socket_after_response.enabled property is set to false, then we will never explicitly add the lisa.vse.close_socket_after_response metadata property to a response, even if the live system closed its socket.
    Default: true

Enterprise Dashboard Properties

The Enterprise Dashboard database is used for the 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.

A custom Enterprise Dashboard database must be configured in the dradis.properties file.

  • lisa.activation.retry.count
    Defines the number of times (count) that DevTest retries the initial communication with Enterprise Dashboard.
    Default: 3

The default connection is to the internal Derby database. For information about connecting to external databases, see External Database Configuration.

Interconnectivity Properties

  • lisa.default.keystore
    Default: {{LISA_HOME}}webreckeys.ks
  • lisa.default.keystore.pass
    Default: passphrase

DevTest to DevTest communication encryption. Typically 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.

  • lisa.net.keyStore
    Default: {{LISA_HOME}}lisa.ks
  • lisa.net.keyStore.password

This is where we keep our identification certificate. If we are a server installation, this is the certificate that clients must 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 must 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.

  • lisa.net.trustStore
    Default: {{LISA_HOME}}lisa.ts
  • lisa.net.trustStore.password_enc
    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.

  • lisa.net.clientAuth
    Indicates whether to use mutual authentication.
    Default: false
  • lisa.net.default.protocol
    Values: SSL or TCP
    Default: SSL
    Default: ssl

License Properties if Using an HTTP Proxy Server

  • laf.usehttpproxy.server
    Default: true
  • laf.httpproxy.server
    Defines the proxy server, in the format my_proxyserver.com.
  • laf.httpproxy.port
    If your proxy server requires credentials, leave blank to use the native NTLM authentication.
    Default: 3128
  • laf.httpproxy.domain
    Defines the proxy domain, if needed for NTLM.
  • laf.httpproxy.username
    Optional
  • laf.httpproxy.password
    Optional
  • laf.email.alert
    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

SDK Properties

The DevTest SDK examples require:

  • asserts
    Format: com.mycompany.lisa.AssertFileStartsWith
  • com.mycompany.lisa.AssertFileStartsWith
    Format: com.itko.lisa.editor.DefaultAssertController,com.itko.lisa.editor.DefaultAssertEditor
  • filters
    Format: com.mycompany.lisa.FilterFileFirstLine
  • com.mycompany.lisa.FilterFileFirstLine
    Format: com.itko.lisa.editor.FilterController,com.itko.lisa.editor.DefaultFilterEditor
  • nodes
    Format: com.mycompany.lisa.node.FTPTestNode
  • com.mycompany.lisa.node.FTPTestNode
    Format: com.mycompany.lisa.node.FTPTestNodeController,com.mycompany.lisa.node.FTPTestNodeEditor

SSL Properties

Change the default behavior for validating the SSL certificates.

  • ssl.checkexpiry
    A value of "true" says to validate the validity dates for the certificate.
    Default: false
  • ssl.checkcrl
    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; also used by Web Service step if not overridden).

  • ssl.client.cert.path
    A full path to the keystore.
  • ssl.client.cert.pass
    The password for the keystore. This password is automatically encrypted when DevTest runs.
  • ssl.client.key.pass
    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.

  • ws.ssl.client.cert.path
     A full path to the keystore.
  • ws.ssl.client.cert.pass
    The password for the keystore. This password is automatically encrypted when DevTest runs.
  • ws.ssl.client.key.pass
    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.

Use a custom keystore when acting as the SSL server during VSE recording and playback (Listen Step).  

  • ssl.server.cert.path
    A full path to the SSL server keystore file.
  • ssl.server.cert.pass
    The password for the SSL server keystore. When DevTest runs, this password is automatically encrypted as a new property named ssl.server.cert.pass.encrypted.
  • lisa.ssl.reuse.session

    If you are reusing the same socket (for example, within the same test it reuses sockets) DevTest creates a new session.
    Default: false

Web Server Properties

  • lisa.webserver.https.enabled
    The default value is true. Do not change the value.
  • lisa.webserver.ssl.keystore.location
    The default value is {{LISA_HOME}}webserver.ks. Change the value if you want to use a keystore file with a different name or in a different directory.
  • lisa.webserver.ssl.keystore.password
    Set the value to the password that you defined when generating the keystore file.

    Use changeit as a default keystore password.
  • lisa.webserver.ssl.keymanager.password
    Set the value to the key manager password that you defined when generating the keystore file. Unless you specified a different password, this password is the same as the keystore password.

    Use changeit as a default keymanager password.

HTTP Authorization Properties

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.

  • lisa.http.domain
    The domain name; use this option for NTLM.
  • lisa.http.user
    Username
  • lisa.http.pass
    Password
  • lisa.http.preemptiveAuthenticationType
    Preemptively send the authorization information rather than waiting for a challenge.
    Values: basic, ntlm, negotiate
    Default: ntlm
  • lisa.http.forceNTLMv1
    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

Kerberos Authentication Properties

  • lisa.java.security.auth.login.config
    The location of the login configuration file.
  • lisa.java.security.krb5.conf
    The location of the Kerberos configuration file that would be used to override any preset locations.
  • lisa.http.kerberos.principal
    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.
  • lisa.http.kerberos.pass
    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.

HTTP Proxy Server Properties

  • lisa.http.webProxy.host
    The machine name or IP address.
  • lisa.http.webProxy.nonProxyHosts
    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
  • lisa.http.webProxy.port
  • lisa.http.webProxy.ssl.host
    The machine name or IP address.
  • lisa.http.webProxy.ssl.nonProxyHosts
    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
  • lisa.http.webProxy.ssl.port
    Leave blank to use integrated NTLM authentication.
  • lisa.http.webProxy.host.domain
    Used for NTLM authentication.
  • lisa.http.webProxy.host.account
  • lisa.http.webProxy.host.credential
  • lisa.http.webProxy.nonProxyHosts.excludeSimple
    Exclude simple host names from proxy use.
    Default: true
  • lisa.http.webProxy.preemptiveAuthenticationType
    Preemptively send authorization information rather than waiting for a challenge.
    Values: basic, ntlm
    Default: ntlm
  • lisa.http.timeout.connection
    HTTP timeout (in milliseconds) - To extend the timeout to wait indefinitely, set the values to zero.
    Default: 15000
  • lisa.http.timeout.socket
    HTTP timeout (in milliseconds). To extend the timeout to wait indefinitely, set the value to zero.
    Default: 180000

XML Serialization Settings

  • 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 reread fails and could require you to set a default of XPATHREFERENCES.

Workstation Management Properties

  • 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

IP Spoofing

  • 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.

Quick Start Recent Items Properties

  • lisa.prefill.recent
    Specify the maximum number of recent items to show in the Prefill combo boxes (no less than 10).
    Default: 10
  • lisa.quickstart.recent
    Specify the maximum number of recent items to show in the Open Recent Quick Start tab (no less than 5).
    Default: 5

lisa-invoke Properties

  • lisa.portal.invoke.base.url
    Default: /lisa-invoke
  • lisa.portal.invoke.report.url
    Default: /reports
  • lisa.portal.invoke.server.report.directory
    Default: lisa.tmpdirlisa.portal.invoke.report.url
  • lisa.portal.invoke.test.root
    Default: d:/lisatests/

Server Host Name Properties

  • lisa.net.externalIP
    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

DevTest to DevTest Communication Encryption Properties

Typically 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

IBM WebSphere MQ Properties

The string-value is supplied by a data set such as the Unique Code Generator.

  • lisa.mq.correlation.id
    A run-time value that sets the correlation ID for an outgoing MQ message.
    Default: string-value
  • lisa.mq.correlation.id.bytes
    A run-time value that sets the correlation ID as a byte[] for nonprintable values.
    Default: byte[]
  • lisa.mq.message.id
    A run-time value that sets the message ID for an outgoing MQ message.
    Default: string-value
  • lisa.mq.message.id.bytes
    A run-time value that sets the message ID as a byte[] for nonprintable values.
    Default: byte[]

JMS Properties

The string-value is often supplied by a data set such as the Unique Code Generator.

  • lisa.jms.correlation.id
    A run-time value that sets the JMSCorrelationID for an outgoing JMS message.
    Value: string-value
  • lisa.jms.ttl.milliseconds
    A run-time value that sets the time-to-live for an outgoing JMS message.
    Value: num-value
  • jms.always.close.jndi
    A value of true always uses the JMS step to close the JNDI context at the end of its execution.
    Values: true, false

Miscellaneous Properties

  • lisa.coord.failure.list.size
    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: 256
  • testexec.lite.longMsgLen
    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
  • java.rmi.server.hostname
    Forces the communication through a specific NIC on the computer.
    Value: IP address of selected NIC
  • lisa.xml.xpath.computeXPath.alwaysUseLocalName
    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
  • lisa.commtrans.ctstats
    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
  • gui.viewxml.maxResponseSize
    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
  • rpt.cleaner.initDelayMin
    Default: 10
  • rpt.cleaner.pulseMin
    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
  • lisa.LoadHistoryWriteSupport.max.errors
    Set to limit the number of errors that are reported to prevent the report generator from backing up. The counter for errors increases based on four events; Abend, Abort, Warning, and Error. If the number of warnings and errors or errors (if warnings are excluded) is greater than maxErrors, then DevTest attempts to stop the test through the coordinator.
    Default: 100
  • lisa.LoadHistoryWriteSupport.includeWarnings
    You can exclude warnings from incrementing the counter by setting lisa.LoadHistoryWriteSupport.includeWarnings=false.
    Default: true
  • lisa.metric.initialization.timeout
    Initialization of the Metric Collector occurs during the staging of the test or suite and the test or 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
  • lisa.graphical.xml.diff.report.numberofextralines
    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
  • lisa.gui.dashboard.sleep.ms
    There is a small sleep() right 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
  • lisa.scripting.default.language
    Designates the default scripting language to use.
    Values:
  • applescript (for OS X)
    • beanshell
    • freemarker
    • groovy
    • javascript
    • velocity
    Default: beanshell
  • lisa.serverSocket.bind.backlog
    Specifies the backlog argument while binding Server Socket. Backlog is the requested maximum number of pending connections on the server socket. Its exact semantics are implementation-specific. In particular, an implementation may impose a maximum length or may choose to ignore the parameter altogether.
    Values: numeric, greater than 0.
    Default: 100
  • qc.pulseInterval
    Specifies the interval, in seconds, that HP ALM Quality Center tries to ping the registry,
    Default: 300

  • lisa.server.https.cipher.suites
    Lets you restrict the enabled cipher suites for DevTest.

    Note: Some of the cipher suites that Java ships with enabled have known vulnerabilities, and may appear on a security scan against running virtual services that are using SSL. You can use this property to restrict DevTest to only the ciphers that you want to allow.

    The rules for this property are:

    • Configure one or more ciphers by setting this property to a comma-separated list of cipher names.
    • If this property is not included in the properties file or if the property is included but with an empty value, then the default JVM-supported ciphers are enabled.
    • If none of the cipher names that are specified in this property are supported by the JVM, then the default JVM-supported ciphers are enabled.
    • If at least one cipher name specified in this property is supported by the JVM, then those ciphers alone are enabled.
  • FileNode.cache.max.size.mb
    For the Read a File (Disk, URL or Classpath) step, specifies when the cache file should be flushed, by size.
    Default: 20 MB
  • FileNode.cache.duration.mins
    For the Read a File (Disk, URL or Classpath) step, specifies when the cache file should be flushed, by time.
    Default: 30 minutes
  • lisa.portal.url.prefix
    Prefix for the URL of DevTest Portal.
    Default: http://
  • devtest.hostname
    The hostname for DevTest Portal.
    Default: the registry server
  • devtest.itr.size.pref
    The default width of the ITR, in pixels.
    Default: 800
  • lisa.cvs.monitor.startup.delay
    Used to delay the CVS start, which gives additional time for a coordinator to start and prevents CVS jobs failing when a coordinator is still unavailable. Specified in seconds.
    Default: 0
  • lisa.builderSession.cleanup.task.interval
    Used to specify the intermittent time interval in which the process will run to clean up the builder sessions on the disk, in hours.
    Default: 1
  • list.builderSession.cleanup.interval
    Used to specify the time interval after which every builder session needs to be removed or cleaned up from the file system, in hours.
    Default: 24
  • lisa.ant.junit.password
    Used to specify the password to use when running JUnit tests.
  • lisa.ant.junit.user
    Used to specify the userid to use when running JUnit tests.

User Session Lifetime Properties

All the user session lifetimes in different DevTest modules are configurable with properties.

The ACL session-related properties and their default values are:

  • registry.max.user.lifetime.seconds

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 Portal to bypass authentication for the DevTest Portal.

When you click a button to access a UI, DevTest bypasses ACL authentication by using an SSO security token. That SSO security token is stored in memory for reuse. However, if Portal 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 Portal, you can click these buttons and can go directly to the UI without entering a userid and password. But after Portal is idle (no activity) for 20 minutes, if you click these buttons, Portal 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.

Mobile Properties

  • lisa.mobile.custom.arguments
    If set, then the string value of the property is added to the command line of the Appium process. It can be anything meaningful to Appium. A full list of Appium arguments can be found here.
    For example: lisa.mobile.custom.arguments=--no-reset 
    This can be used with applications that require setup configuration or can exhibit distinct behavior on the first run. The no-reset assures that the application would not require setup on every test run.
  • lisa.mobile.remote.user
    When running remote tests through a headless app like TestRunner, this property is required if you want to prompt for a User name for the remote host during a playback of a recording.
  • lisa.mobile.remote.password
    When running remote tests through a headless app like TestRunner, this property is required if you want to prompt for a Password for the remote host during a playback of a recording.
    Ensure you encrypt this password by clicking the check box for the lock icon in DevTest Workstation.
  • lisa.mobile.saucelabs.appium.version
    This property lets you specify the specific version of Appium to use for a device you have defined on SauceLabs.
    For example: lisa.mobile.saucelabs.appium.version=4.3 always uses Appium 4.3 for these tests.

  • lisa.mobile.remote.device
    The iOS device name that is used for remote recording and playback. The default value is "iPhone 6".

  • lisa.mobile.remote.device.version
    The iOS device version that is used for remote recording and playback. The default is "9.3".

Was this helpful?

Please log in to post comments.