The lisa.properties property file stores initialization and configuration information.
Property files are stored in the DevTest install directory.
You can display the contents of this file in DevTest Workstation.
Note: Do not add your custom properties to this file, as CA Technologies reserves the right to replace this file at any time.
To open the lisa.properties file, select System, Edit Properties from the main menu.
This section contains the following topics:
Comma-Separated List of Paths for Javadoc and Source Code
Test Case Execution Parameters
TestEvent Handling Customizations
Test Manager/Editor Properties
Native Browser Information to Use for Internal Rendering
Test Manager/Monitor Properties
Built-In String-Generator Patterns
Properties for Use by StdSchedulerFactory to Create a Quartz Scheduler Instance
CA Continuous Application Insight Properties
Selenium Integration Properties
These paths are used to show you class and parameter documentation. The docpath can take directories and URLs that are base paths to the Javadoc. Here is an example that includes JDK docs from a website, but websites are not recommended because of delays. lisa.java.docPath=LISA_HOME\examples\javadoc,[http://java.sun.com/j2se/1.3/docs/api/
lisa.java.docPath=LISA_HOME\examples\javadoc
lisa.java.sourcePath=LISA_HOME\examples\src
This sourcepath can take directories as base paths and JAR or zip files of source.
lisa.axis.compiler.version=1.4
This is lisa.axis.compiler.version 1.4.
Encoding for files that DevTest reads or writes.
Default: UTF-8
To include the encodings to support in the HTTP/HTML Request step, change the comma-separated list. The underlying JVM must also support all encodings in this list. If a webpage uses an encoding that is not supported in the list, then the encoding is replaced with the DevTest default encoding (file.encoding key in lisa.properties). Also, if an encoding is not selected when creating a HTTP/HTML Request step, then the DevTest default encoding is assumed.
Default: ISO-8859-1, UTF-8, Shift_JIS, EUC-JP
Default: 1.7
Default: Error
Default: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
Default: org.apache.xerces.jaxp.SAXParserFactoryImpl
Default: org.apache.xalan.processor.TransformerFactoryImpl
The IP address that we listen on. By default, we listen on all our IP addresses. You can restrict this value to a specific IP address. To prevent other computers connecting but allow local connections, set the value to 127.0.0.1 or localhost.
Default: false
Default: false
Default: true
Default: true
Default: true
Default: true
Default: LISA
Default: true
lisa.update.every=1
Controls how often DevTest checks to see whether a newer version is available to download. To disable checking, set the value to blank. The other valid values are:
lisa.update.URL=http://www.itko.com/download/ga/
lisa.testcase=test.xml
Default when running a test from the com.itko.lisa.test.TestCase class directly.
lisa.registry=registry.xml
Default when running a test from the com.itko.lisa.test.TestCase class directly.
lisa.runName=Ad-hoc Run
Default when running a test from the com.itko.lisa.test.TestCase class directly.
lisa.registryName=registry
Default name of the registry to attach to, and the default name of the registry when you start it without a name.
lisa.coordName=coordinator
The coordinator server default name when started without an explicit name AND when the Test Runner needs one and you do not specify a coordinator server on the command line.
lisa.simulatorName=simulator
The default name of a simulator daemon if you do not provide one on the command line.
lisa.vseName=VSE
The virtual environment server default name when started without an explicit name.
lisa.defaultRegistry.pulseInterval=30
Status log interval for the registry. The default value is 30 seconds.
lisa.coordinator.pulseInterval=30
The status log interval for the coordinator. The default value is 30 seconds.
lisa.simulator.pulseInterval=30
The status log interval for the simulator. The default value is 30 seconds.
lisa.vse.pulseInterval=30
The status log interval for VSE. The default value is 30 seconds.
lisa.server.projectmap.refresh.pulseInterval=600
The time interval after which the DevTest servers (coordinator and simulator) refresh the map of project names to file paths.
lisa.defaultRegistryConnectionTimeoutSeconds=90
Timeout value in seconds that coordinators and simulators use when connecting to a DevTest registry. A value of 0 indicates an infinite timeout; that is, we wait forever trying to connect.
lisa.regex.helper.tutorial.url=http://download.oracle.com/javase/tutorial/essential/regex/
For the Regex helper window, the URL to show for the regular expression tutorial.
lisa.hooks=com.itko.lisa.files.SampleHook
To register hooks with DevTest; these values are comma-separated.
lisa.project.ignore=CVS|SCCS|RCS|rcs|\.DS_Store|\.svn|vssver\.scc|vssver2\.scc|\.sbas|\.IJI\..*|.*\.pyc|.*\.pyo|\.git|.*\.hprof|_svn|\.hg|.*\.lib|.*~|__pycache__|\.bundle|.*\.rbc
This property is a Java regular expression that lets you hide the types of files that you do not want to see in the Project tree. By default, a variety of well-known control files for third-party products are hidden. To show files that are hidden by default, modify the regular expression.
The default values for header keys in the HTTP support are in the following list. To get the benefit of the change, remove or change them for all tests. To change them for a test, or even the execution of one HTTP transaction, use TestNode-specific header directives.
Values: compatible, MSIE 6.0, Windows NT 5.0
Default: Mozilla/4.0
Default: Pragma
Default: no-cache
Default: Cache-Control
Default: no-cache
Default: Accept
Default: image/gif, image/x-xbitmap, image/jpeg
Default: Accept-Language
Default: en
Default: Accept-Charset
Default: iso-8859-1,*,utf-8
Default: User-Agent
Default: Mozilla/4.0, MSIE 6.0; Windows NT 5.0
The following list shows defaults for fields that appear in the HTTP Field editor. Do not include "Authentication" because the editor adds it automatically.
Values: Accept,Accept-Language,User-Agent,Connection
Values: html,text,magnus-internal,application/pdf
Values: css,script
Values: .gif,.jpg,.jpeg,.css,.js,.ico
Enables NTLM authentication in the Test Runner.
Default: true
lisa.hotDeploy=C\Projects\Lisa\custom_classes
This setting tells the ClassLoader built into DevTest where to look for custom classes. The default is $LISA_HOME\hotDeploy.
lisa.overloadThreshold=1000
The TestNode attempts to determine if the simulator is thrashing by checking the actual amount of time slept in think time as opposed to the amount of think time it was supposed to take. This setting is the amount of additional "slip" in think time that is acceptable before sending a warning TestEvent that the simulator is overloaded. The default of 1000 means that if the simulator sleeps 1 second more than it was supposed to, (presumably because the computer is CPU starved), then raise the TestEvent.
lisa.webservices.encode.empty.xmlns=true
Some web service server stacks require empty xmlns strings in the SOAP request (for example, jbossWs). Others, such as Amazon, do not work with empty xmlns strings. Change this property to suit the stack you are calling.
lisa.webservices.encode.version=1.1
Set the encoding version to force for client stub generation. The default is 1.1.
lisa.tm.sys.min.millis=0
lisa.tm.sys.max.millis=0
The default think time for new system steps, in milliseconds. The system steps include subprocesses, continue, continue (quiet), fail and end.
lisa.numFilters.warning=100
lisa.numAsserts.warning=100
Sometimes, filters and assertions are dynamically added to test steps. In a load test, this could mean many thousands of asserts/filters. The preceding two numbers are the threshold before the log generates a WARN level message.
lisa.exception.on.num.exceeded=true
If the threshold is exceeded, should we raise a TestDefException (kills the test)?
lisa.urltrans.encode.queryparams=false
Setting this property to false ensures the query parameters in an HTTP/HTML URL are not decoded/encoded when executing the step.
lisa.generic.url.decoder=true
Set this property to true when opening a test case in DevTest 7.1.1 or later that has an HTTP/HTML Request step that was created in 7.0.0 or earlier.
lisa.perfmon.snmp.port=1161
The StatKeeper can load a Perfmon integration class that wraps or implements a platform-specific monitor, like Windows Perfmon, JMX, SNMP, and others. DevTest comes with a Perfmon DLL class and an SNMP class to support producing our stats output to either the Windows Performance monitor OR (not both) as an SNMP agent. For more information, see the documentation on SNMP. The usual port for SNMP is 161, but you have to be root to use that.
lisa.perfmon.class=com.itko.lisa.stats.snmp.SnmpPerfmon
When we do have something that can pump native OS data into a performance monitor, implement a class that can push DevTest data into that tool and put that class name here.
lisa.perfmon.dll=/c:/Projects/Lisa/PerfmonJNI/LISAPerfmonJNI/Debug/LISAPerfmonJNI.dll
Windows Perfmon integration to the StatKeeper has a "DLL" setting for the Windows (native) implementation. Put the full path/file here. You only need this if you are using PerfmonStatKeeperWindows.
Simulators use a separate thread and queue to send TestEvents to the coordinator to cut down on the chattiness of RMI. These are the thresholds that cause the daemon thread to push events. We take the minimum of the size or the max-wait (if either we take too long or have too many, we post them).
lisa.eventPoolPoll=250
How often we check the queue size or we see if we have overrun our max wait (in milliseconds).
lisa.eventPoolSize=64
The maximum size that we let it get before sending.
lisa.eventPoolMaxWait=1000
How long we are willing to go with an event being unforwarded.
Default: false
Default: 6
Default: LISA_HOME\screens
Default: lisa-screencap-
Default: -contents
This property sets the "scale" (primarily, font size) for things in the model and step inspectors of the main model editor. 1.0 is 12 points, so determine a value for this property by dividing the size that you want in points by 12. For example, 11 points is 11/12 = 0.92, 10 points is 10/12 = 0.83 (the default), 14 points is 14/12 = 1.17.
Default: 0.83
Some built-in metrics (steps for each second) use a Java DecimalFormat to display floating-point values. To not use the decimal point, make this value "######" or select from a range of displays; see http://download.oracle.com/javase/6/docs/api/java/text/DecimalFormat.html.
Default: ###,###.#
This is the comma-separated list of all custom Java test nodes to include in your test case.
This drives the formatting of messages to the System Messages window.
Default: %-5p - %m%n
The HTTP recorder binds to this port.
Default: 8010
Default: on
|
lisa.prefill.jndiNames= |
JBOSS=org.jnp.interfaces.NamingContextFactory |
|
lisa.prefill.jndiUrlPrefix= |
JBOSS=jnp:// |
|
lisa.prefill.jndiDefPort= |
JBOSS=1099 |
|
lisa.prefill.jndiNeedsClass= |
JBOSS=false |
|
lisa.prefill.jndiFactories= |
org.jnp.interfaces.NamingContextFactory |
|
lisa.prefill.jndiServerURLs= |
jnp://SERVER:1099&t3://SERVER:7001 |
|
lisa.editor.URLTransEditor.protos= |
http,https |
|
lisa.editor.URLTransEditor.hosts= |
|
|
lisa.editor.URLTransEditor.ports= |
80,443 |
|
lisa.editor.URLTransEditor.files= |
|
|
lisa.prefill.jdbc.names= |
Oracle |
|
lisa.prefill.jdbc.jdbcDrivers= |
oracle.jdbc.driver.OracleDriver |
|
lisa.prefill.jdbc.jdbcConnectionURLs= |
jdbc:oracle:thin:@SERVER:1521:SIDNAME |
lisa.internal.browser.on=yes
lisa.internal.browser.win=com.itko.lisa.web.ie.IEUtils
lisa.internal.browser.osx=com.itko.lisa.web.jxbrowser.JxBrowserUtils
lisa.internal.browser.linux=com.itko.lisa.web.jxbrowser.JxBrowserUtils
lisa.internal.browser.sol-sparc=null
lisa.internal.browser.imgs=false
lisa.internal.browser=msie
WR type: mozilla, safari, msie
lisa.internal.browser.swing.heavy=false
lisa.internal.browser.usejsinviews=yes
lisa.example.wsdls=http://localhost:8080/itko-examples/services/UserControlService?wsdl
The maximum number of event rows that are kept in the Test Manager as a test is run. The number of objects that are kept is twice this number.
Default: 500
The system messages window maximum size. The memory that is consumed is twice this value.
Default: 10240
lisa.patterns.stringgenerator.types=&Phone=(DDD)DDD-DDDD, &SSN=DDD-DD-DDDD, &Date=Lll-DD-DDDD, &Zip=D*(5)
|
lisa.jmx.types |
com.itko.lisa.stats.jmx.JSE5Connection |
|
lisa.jmx.typeprops |
com.itko.lisa.stats.jmx.JSE5Connection=LISA_JMX_JSE5 |
You do not generally need anything for these parameters.
Default: LISA_HOME/lib/mx4j.lib
Default: LISA_HOME/lib/mx4j.lib
If you are running JSE 5, you do not need to change this property. We ship a jbossall-client that includes what you need, assuming the version is right.
Default: LISA_HOME/lib/mx4j.lib{{path.separator}}LISA_HOME/hotDeploy/jbossall-client.jar
This parameter is for Tomcat.
Default: LISA_HOME/lib/mx4j.lib{{path.separator}}LISA_HOME/hotDeploy/mx4j-tools.jar
Default: LISA_HOME/hotDeploy/weblogic.jar{{path.separator}}LISA_HOME/hotDeploy/wljmxclient.jar
This parameter needs to change to the location of your weblogic.jar. No wlclient.jar will not work.
Default: LISA_HOME/hotDeploy/weblogic.jar
Oracle AS
Default: LISA_HOME/lib/oc4jclient.jar{{path.separator}}LISA_HOME/lib/adminclient.jar
IBM WebSphere
It is easier to use your IBM/WAS CLASSPATH before you start DevTest and leave this blank.
Default: LISA_HOME/lib/mx4j.lib
If you use performance monitoring alerts, this parameter is the "from" email address for those alerts.
Format: lisa@itko.com
This parameter is the email server that we try to route emails with (SMTP server).
Default: localhost
Values:
Runs the test case once with one simulated user
Runs the test case once with one simulated user and no think time
Runs the test case with one simulated user for one minute, restarting the test as needed
Stage the test for 5 minutes, restarting as needed
Execute this test until manually stopped
Execute this test with 5 virtual users for 1 minute
Default: com.itko.lisa.files.DefaultAudit.aud
Default: 5
test.cmde.win.shell=cmd /c
test.cmde.unix.shell=sh -c
test.cmde.Windows.NT.(unknown).shell=cmd /c
lisa.props.blankOnMissing=true
Property to use if you want DevTest to replace key with an empty string if key is not in state.
lisa.test.custevents=&101="Custom Event 101"; &102="Custom Event 102"
Custom events: the first allowed event number is 101, so we have registered two as examples here.
lisa.SimpleWebFilter.responseCodeRegEx=[45] d d
lisa.fsss.dateformat=MM/dd/yyyy hh:mm:ss a
Configure Main Scheduler Properties
Default: org.quartz.simpl.RAMJobStore
Default: org.quartz.simpl.SimpleThreadPool
Default: 5
Default: 5
Platform-Specific Parameters in the TM
Default: xterm -e {0}
Default: cmd /c start {0}
Default: open -a /Applications/Utilities/Terminal.app {0}
Properties Used by Swing Testing Support
Uncomment to use a custom Log4J logging properties file in SwingTestProgramStarter.
Default: C:/Lisa/swingtestclient-logging.properties
License Settings
Default: laf/license.do
Default: https://license.itko.com
Default: true
Reporting Properties
Values: A4 | letter
Reporting JPA Properties
Default: create-tables
Default: database
Default: false
Default: true
To check for expired reports, set autoExpire = true. Set the expiration period: an integer followed by (m=month,w=week,d=day,h=hour). The default expiration period is 30d (30 days).
Default: 30d
Validate the report database schema. By default, only the registry validates the schema.
Default: false
Default: true
Default: true
The default behavior is to not automatically shut down the local registry if it was started automatically. The exceptions are DevTest Workstation, VSE, and VSE Workstation.
Default: true
Default: false
JUnit and TestRunner should never auto shut down the registry.
Default: false
Property Used for the Eclipse Connector
Default: 8546
Property Used for Example Test Suites
Default: LISA_HOME/examples
Defines the minimum length of the argument value in a VSE transaction request that is required to consider that argument for constructing a magic string.
Default: 3
Defines how searches in VSE for magic string content relate to word boundaries.
Values:
Default: both
Specifies whether to exclude specific strings from eligibility for magic stringing.
Values: Yes, YES, yes, No, NO, no, true, True, TRUE, false, False, FALSE, __NULL
Default: Yes, YES, yes, No, NO, no, true, True, TRUE, false, False, FALSE, __NULL
Specifies whether to change text in XML tags to magic strings.
Default: false
Specifies whether multiple VSE instances run on different computers from the same installation directory. If they do, uncomment this property and set it to true.
Default: false
Specifies whether to format the XML in the service image if VSE records an XML response. The default, false, indicates DevTest does not prettyprint, format, or add line breaks to XML. If the XML arrives as one long string, DevTest displays it that way.
Default: false
Specifies whether VSE remembers the execution modes you set with the VSE Dashboard for virtual services. Comment out this property if you do not want VSE to remember the execution modes across shutdowns.
Default: true
Sets the number of events for each VS model to define how many matching related events VSE buffers. The property sets the number of events for each VS model. For example, if two VS models are deployed with the default event buffer size of 100, then 200 events are buffered. These events are the source for the Match tab of the VS model inspection page in the VSE dashboard.
Default: 100
Defines the number of inbound VSE requests for which a full set of DevTest events is buffered. The property sets the number of events for each VS model. For example, if two VS models are deployed with the default request buffer size (5), 10 sets of events (grouped by inbound request) are buffered. These sets of events are the source for the Events tab of the VS model inspection page in the VSE dashboard.
For performance reasons, VSE holds 50 events for processing. This limit can result in the removal of events from the processing queue and the absence of in the Inspection View. To prevent the truncation of events, you can increase the size of the event processing queue. However, this action can increase memory usage and can reduce performance.
Default: 5
Defines the order in which registered VSE text response editors are queried when using autodetect. Only enough of the "right end" of the class name to make it unique is required.
Values: XMLTextEditor, JSONTextEditor
Default: The default text editor
Defines (in milliseconds) the default minimum think time for new "regular" steps.
Default: 500
Defines (in milliseconds) the default maximum think time for new "regular" steps.
Default: 1000
Specifies the maximum number of optional query parameters to use per method in a WADL or RAML file. If there are more than lisa.vse.rest.max.optionalqueryparams optional query parameters specified in a WADL or RAML file, only the first lisa.vse.rest.max.optionalqueryparams are used to create transactions.
Default: 5
Date-Checker Properties
The VSE date utilities use the following properties to determine which date patterns are considered valid for date sensitivity conversions. Each of the following entries represents a regular expression that VSE considers as a part of a date.
((\[12\]\\d)\|(3\[01\])\|(0?\[1-9\]))
((1\[012\])\|(0 \\d)\|0\[1-9\]\|\[1-9\])
(\\bJAN\\b\|\\bFEB\\b\|\\bMAR\\b\|\\bAPR\\b\|\\bMAY\\b\|\\bJUN\\b\|\\bJUL\\b\|\\bAUG\\b\|\\bSEP\\b\|\\bOCT\\b\|\\bNOV\\b\|\\bDEC \\b)
\\d\\d\\d\\d
\\d\\d
(\\s?((\[012\]? \\d)\|(2\[0123\]))\:((\[012345\] \\d)\|(60))\:((\[012345\] \\d)\|(60)))
((\[012\]? \\d)\|(2\[0123\]))\:((\[012345\] \\d)\|(60))\:((\[012345\] \\ d)\|(60))
((\[012\]?\\d)\|(2\[0123\]))\:((\[012345\]\\d)\|(60))\:((\[012345\]\\d)\|(60))\\.(( \\d \\d \\d)\|0)
((\[012\]?\\d)\|(2\[0123\]))\:((\[012345\] \\d)\|(60))\:((\[012345\] \\ d)\|(60)) \\.((\\d \\d \\d)\|0) \\s(\[A-Za-z\]\[A-Za-z\]\[A-Za-z\])
\\d\\d\\d\\d-((1\[012\])\|(0\\d)\|0\[1-9\]\|\[1-9\])-((\[12\]-\\-d)\|(3\[01\])\|(0?\[1-9\]))T((\[012\]?-\\-d)\|(2\[0123\]))\:((\[012345\]-\\-d)\|(60))\:((\[012345\]-\\-d)\|(60))-\\-.-\\-d-\\-d-\\-d\[-+\]\\d\\d\\d \\d
((\[12\]\\d)\|(3\[01\])\|(0?\[1-9\]))(JAN\|FEB\|MAR\|APR\|MAY\|JUN\|JUL\|AUG\|SEP\|OCT\|NOV\|DEC)\\d \\d \\d \\d
(JAN\|FEB\|MAR\|APR\|MAY\|JUN\|JUL\|AUG\|SEP\|OCT\|NOV\|DEC)((\[12\]\\d)\|(3\[01\])\|(0?\[1-9\]))\\d \\d \\d \\d
\\d\\d \\d \\d((\[12\] \\d)\|(3\[01\])\|(0?\[1-9\]))(JAN\|FEB\|MAR\|APR\|MAY\|JUN\|JUL\|AUG\|SEP\|OCT\|NOV\|DEC)
\\d\\d\\d\\d(JAN\|FEB\|MAR\|APR\|MAY\|JUN\|JUL\|AUG\|SEP\|OCT\|NOV\|DEC)((\[12\] \\d)\|(3\[01\])\|(0?\[1-9\]))
((\[12\]\\d)\|(3\[01\])\|(0?\[1-9\]))(JAN\|FEB\|MAR\|APR\|MAY\|JUN\|JUL\|AUG\|SEP\|OCT\|NOV\|DEC)
(JAN\|FEB\|MAR\|APR\|MAY\|JUN\|JUL\|AUG\|SEP\|OCT\|NOV\|DEC)((\[12\]\\d)\|(3\[01])|(0?\[1-9\]))
((\[12\]\\d)\|(3\[01\])\|(0?\[1-9\]))(JAN\|FEB\|MAR\|APR\|MAY\|JUN\|JUL\|AUG\|SEP\|OCT\|NOV\|DEC)\\d\\d
In VSE, each of the following entries represents a valid pattern for part of date:
Format: dd
Format: MM
Format: MMM
Format: yyyy
Format: yy
Format: HH:mm:ss
Format: HH:mm:ss
Format: HH:mm:ss.SSS
Format: HH:mm:ss.SSS z
Format: yyyy-MM-dd'T'HH:mm:ss.SSSZ
The following date patterns cannot be constructed by using a combination for the previous patterns that involve at least day, month, and year:
Format: MMM*dd*yyyy
Format: MM*dd*yyyy
Format: dd*MMM*yyyy
Format: dd*MM*yyyy
Format: yyyy*MMM*dd
Format: yyyy*MM*dd
Format: ddMMMyyyy
MMMddyyyy
Format: yyyyddMMM
Format: yyyyMMMdd
Format: ddMMMyy
Format: ddMMM
Format: MMMdd
Defines the valid separator characters to use in the date formats.
Values: -/.
Example: lisa.vse.datechecker.separators=/ sets ‘/’ as a separator as in 10/15/2011.
Defines the order in which to match the date pattern. The separator characters that lisa.vse.datechecker.separators defines replace the asterisks.
Example: MM*dd*yy generates four date patterns: "MM-dd-yyyy", "MM dd yyyy", "MM/dd/yyyy", "MM.dd.yyyy".
lisa.vse.datechecker.mmmddyyyy.separatorformat&\
lisa.vse.datechecker.mmddyyyy.separatorformat&\
lisa.vse.datechecker.ddmmmyyyy.separatorformat&\
lisa.vse.datechecker.ddmmyyyy.separatorformat&\
lisa.vse.datechecker.yyyymmmdd.separatorformat&\
lisa.vse.datechecker.yyyymmdd.separatorformat&\
lisa.vse.datechecker.mmmddyyyyformat&\
lisa.vse.datechecker.ddmmmyyyyformat&\
lisa.vse.datechecker.yyyyddmmmformat&\
lisa.vse.datechecker.yyyymmmddformat&\
lisa.vse.datechecker.ddmmmyyformat
lisa.vse.datechecker.time.millis.zoneformat&\
lisa.vse.datechecker.time.millisformat&\
lisa.vse.datechecker.time.tenthsformat&\
lisa.vse.datechecker.time.hhmmssformat
lisa.vse.datechecker.bottom.priorityorder
lisa.vse.datechecker.mmmddformat&\
lisa.vse.datechecker.ddmmmformat
Values: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Format: (?ism).*((\\d[./-](19|20)[0-9]{2})|((JAN|FEB|MAR|APR|MAY|JUN|JUL|AUG|SEP|OCT|NOV|DEC)[. /-](19|20)[0-9]{2})|((19|20)[0-9]{2}[. /-][0-9]{2})).*
Defines a coarse level test to determine whether the payload contains anything that resembles a year. To avoid matching too much, it looks nearby for other identifying information such as month information and common date separators (for example, - or / or .).
When the year is difficult to distinguish from any other four-digit number, this pattern may not match. In that case, your magic dates are not found. Try one of the following solutions:
Format: (?ism).*((\\d[./-]?(19|20)[0-9]{2})|((JAN|FEB|MAR|APR|MAY|JUN|JUL|AUG|SEP|OCT|NOV|DEC)[. /-]?(19|20)[0-9]{2})|((19|20)[0-9]{2}[. /-]?[0-9]{2})).*
Defines a more permissive coarse level test than the previous test to determine whether the payload contains anything that resembles a year. If the dates are not recognized, this Regex may allow them to be found. To avoid matching too much, it looks nearby for other identifying information such as month information and common date separators (for example, - or / or .).
However, this Regex can have some performance impact. If this Regex matches too many dates, the patterns above run in situations where they are not applicable. Running large numbers of Regex patterns against large payloads can be time consuming.
VSE JMS Messaging - Custom JMS Properties to Ignore
Some JMS platforms include extra custom properties in the JMS messages they deliver. These properties can interfere with VSE creation. vse.jms.ignore.proplist contains a list of properties to ignore when recording a JMS service with the VSE messaging recorder. The format is a comma-delimited list of regular expressions. By default, it excludes standard JMS extension properties (JMSX) and JBoss custom bookkeeping properties (JMS_.).
Default: JMSX.*, JMS_.*
VSE Recorder Conversation Batch Size
Defines how many conversations we process before committing them to the database. If you have a few large conversations, make this number small. If you have many smaller conversations, make this number large. A batch size of <= 0 is the same as a batch size of 1.
Default: 10
VSE Service Image Database Settings
Default: create-tables
Defines the database to use as the repository for service images. VSE uses the open source EclipseLink JPA provider. By default we use our reports database as the repository for service images.
Default: LISA reports database
Validate the VSE Schema
If EclipseLink is configured to do query timings (the default), this value defines the maximum interval (in milliseconds) allowed for a database query before the com.itko.lisa.vse.stateful.model.SqlTimer logger raises a WARN-level message. If you set the threshold on that logger to DEBUG, timings return for all SELECT statements EclipseLink issues. This logging is the first step in debugging VSE performance issues. If the database is local and all the indexes are created, then you should not see anything over about 20 ms. However, a database on the network that is not under your control and possibly missing indexes could easily take 100ms or more to return a result. In that case, VSE can seem to be slow when in fact it is fast if correctly deployed. Most service images are small enough or have a working set sufficiently small enough to fit into the VSE entity cache. Therefore, the number of SELECTs that VSE issues should dwindle to zero, provided the VSE has a large enough heap. The cache maintains soft references by default.
Default: 100
VSE Delimited Content Detection Properties
Defines the maximum number of characters to inspect to determine the content type.
Default: 1000
Defines the maximum percentage of characters to inspect to determine the content type. This property is used if it is higher than lisa.vse.delimited.delimiter.check.maxchars.
Default: 2
Defines the characters that the Delimited Content Detector looks for as delimiters.
Default: :,\\,,;,|,\u00A6,\t,\n
Defines the minimum number of delimiters that are counted for the Delimited Content Detector. The payload must have at least this many delimiters.
Default: 3
Defines the Name-Value separators that are used to detect the delimited name-value payload. These values must not be in the lisa.vse.delimited.delimiter.list.
REST Data Protocol Properties
Defines the maximum number of items of matching traffic that are populated in the lower pane of the URI rules wizard. If the wizard takes a long time to populate the lower pane with matching traffic, try using a lower value in this field.
Default: 100
Defines the maximum number of items of unmatched traffic that display in the unmatched traffic dialog. If the wizard takes a long time to populate this wizard, try using a lower value in this field.
Default: 100
Defines for the REST data protocol a regular expression that detects the parts of an HTTP request that it can consider to be an identifier. The data protocol converts such identifiers to dynamic parameters. When you have dynamic parameters that you know follow a specific format, you can use this property to detect them.
Default: [a-zA-Z]+[0-9]{5,}[a-zA-Z]*
Example: The value id12345 can denote a stock item and the subsequent rule contains {URLPARAM0}.
Defines the maximum number of changes that VSE allows for a token before the variability is considered significant enough to generate a rule.
Default: 1
Defines the prefix that the REST data protocol uses for the parameters in rules.
Default: URLPARAM
Defines the position in the URL at which the REST data protocol starts looking for variable tokens.
Default: 3
Example: In the URI GET /a/b/c/d, GET is at position 0, a is at position 1, and b is at position 2.
Limits the size of responses that DevTest writes to the vse.log. This property is only applied when trace-level logging is enabled: specifically, when com.itko.lisa.vse.http.Transaction=TRACE or when com.itko.lisa.vse.stateful.protocol.http.Coordinator=TRACE.
Values:
Default: 2048
The network port properties take the form of lisa.net.APPID.port.
If you must change these defaults, override them in the site.properties file. Clients make assumptions about what port to connect to their server based on these values.
DevTest Workstation
Default: 2008
Coordinator
Default: 2011
Registry
Default: 2010
JUnit exec
Default: 2012
Test Runner (command line)
Default: 2005
Others
Default: 2007
VSE
Default: 2013
VSEManager
Default: 2004
ServiceManager
Default: 2006
Simulator (we start here so it is easier to have many on the same computer).
Default: 2014
Default: true
Default: 0.0.0.0
Default: 2009
Our embedded web server.
Default: 1505
Default: false
Default: 1507
Default: true
Default: true
The host of our embedded web server. 0.0.0.0 binds to all local addresses.
Default: 0.0.0.0
Default: /acl/
These properties set the values for all of the portal app launchers from DevTest Workstation. Currently, the TR host name is used for the Host value so we get that value dynamically. The URL is launched externally in your system's browser.
Default: http://* (http://\*)
Default: /index.html
Default: /index.html?lisaPortal=cvsdashboard
Default: /index.html?lisaPortal=pathfinder
Default: /index.html?lisaPortal=serverconsole
Default: /index.html?lisaPortal=serverconsole
Default: reporting
Default: /index.html?lisaPortal=reporting
Default: /pathfinder/lisa_pathfinder_agent/defectcapture
Default: /pathfinder/lisa_pathfinder_agent/saveDefectData
Default: /lisa-invoke
Default: /reports
Default: lisa.tmpdirlisa.portal.invoke.report.url
Default: /devtest/#/main
Default: {{devtest.portal.base.url.path}}/dashboard
Default: {{devtest.portal.base.url.path}}/createartifacts
Default: {{devtest.portal.base.url.path}}/pathManageAgents
Default: LISA_HOME
Reporting Graph View Properties
Default: 100
Results more than maximum threshold. Modify a filter to fetch the details.
Default: 10000
Results more than maximum threshold. To fetch the details, modify a filter.
Async Reporting Support
If you run load tests and you find that the bottleneck in the test cases is writing the events to the reporting database, consider removing everything except metrics from the report generator. If you still see the reporting engine as the bottleneck, consider enabling this property. The property uses JMS to send the reporting event and background threads in the simulators and coordinator write the events to the database asynchronously. This means that your load test finishes before all the events are written to the database, so the report does not appear for some time (how long depends on your test cases and how many events they generate). The simulator queue typically takes the longest to flush; you get a message at the INFO level in the simulator log showing the percentage complete.
This feature is considered as "advanced usage" for now and is disabled by default. Feedback at http://ca.com/support is welcome and encouraged.
Default: false
Default: 100
These properties control the collection of statistics for a test step during the execution of a test case. The values specify the maximum number of occurrences that are recorded for the properties that are used and properties that are set. You should not need to change the default values.
Default: 100
Default: true
Default: 30
Enable periodic thread dumps. It is a good idea to leave this enabled. It efficiently checks to see if the threadDumpLogger is at INFO or below and not do anything if it is set to WARN or higher. Properties are only read once at startup; the logging.properties file is checked every 10 seconds for changes. All you must do is leave this alone and set the log level of the threadDumpLogger to INFO and wait for at most 30 seconds to get periodic thread dumps of a running DevTest Server. These logs are invaluable when debugging performance issues. See the comments in logging.properties for more information.
Default: threadDumpLogger
These properties are used to control the metrics collection in VSE servers. The metrics that are collected can be viewed in the web-based VSE dashboard.
Main property to turn on the overall metrics collection (true) or off (false).
Default: true
This property controls the level at which transaction counts are recorded. When the named transaction counts are summed, you get transactions for any time period.
Values: none (or false), service, request
Default: service
This property controls how often transaction rate and response times are sampled.
Default: 5m
Default: 1h
These properties control how often old metric data is scanned for and deleted, and what is considered old.
Default: 30d
Indicates whether to start the internal Derby database instance in the registry.
Default: true
The network interface that the internal Derby database uses. The default value 0.0.0.0 indicates that all interfaces are used.
Default: 0.0.0.0
The port number that the internal Derby database listens on.
Default: 1528
Default: 1d
These properties control how often old ACL audit log data is scanned for and deleted, and what is considered old.
Default: 30d
The following components interact with a database: reporting, Agent broker, VSE, and ACL. Typically you would point them all to the same connection pool, but you can define a separate pool for each or mix and match. To define a new pool, set up properties like lisa.db.pool.myPool.url. The underlying pool implementation is the open source c3p0 pool, and the various properties are passed down. For available settings, see http://www.mchange.com/projects/c3p0/index.html#configuration_properties.
Default: common
Default: common
Default: common
Default: common
Default: org.apache.derby.jdbc.ClientDriver
Default: jdbc:derby://localhost:1528/database/lisa.db;create=true
Default: rpt
Set the password by removing the trailing _enc from the property name and adding =MyPlaintextPassword. The password is automatically encoded at startup.
Default: 76f271db3661fd50082e68d4b953fbee
The following pool properties keep the number of connections to a minimum when DevTest is idle.
Default: 0
Default: 0
Default: 10
Default: 1
Default: 45
Default: 5
Other common database settings: copy and paste the relevant user, password, and pool size parameters from the common template.
Default: oracle.jdbc.OracleDriver
Default: jdbc:oracle:thin:@HOST:1521:SID
Default: com.ibm.db2.jcc.DB2Driver
Default: jdbc:db2://HOST:50000/DBNAME
Default: com.microsoft.sqlserver.jdbc.SQLServerDriver
Default: jdbc:sqlserver://durry;databaseName=LISA
Default: com.mysql.jdbc.Driver
Default: jdbc:mysql://HOST:3306/DBNAME
When defining a JDBC Connection asset, the connection pool size can be configured by this property.
Default: 5
Indicates whether to enable the CICS mainframe bridge.
Default: false
Indicates whether the mainframe bridge runs in client mode or server mode.
Default: server
When the mainframe bridge is running in server mode, this port is the well-known port that the mainframe bridge listens on.
Default: 61617
Default: 127.0.0.1
When the mainframe bridge is running in client mode, these values are the IP address and the well-known port of the LPAR agent.
Default: 3997
Two-character unique ID for each client.
Default: AA
For more information, see Mainframe Bridge in Agents.
WebSphere MQ Properties
lisa.mq.ccsid.default=819
You can use this property to override the default Coded Character Set Identifier (CCSID) for all IBM WebSphere MQ messages sent from DevTest. This value can also be overridden for each case in the Publisher Info's Message Properties of the IBM WebSphere MQ step. For more information, see Using CA Application Test. For the complete list of CCSIDs, see http://www-01.ibm.com/software/globalization/ccsid/ccsid_registered.html. The default value for United States locales is 819 (ASCII).
Localization Options
lisa.locale.languages=en
You can use this property to indicate the languages to support in the UI. The valid values are en and ja, indicating English or Japanese.
If you specify both en and ja here, you can switch the UI between English and Japanese by using the System, Language option off the Main menu.
Valid values are ISO-8859-1,UTF-8,Shift_JIS,EUC-JP,Windows-31J.
Specifies whether to add an implicit waitForElementPresent step for each step in the test case that must locate a web element.
Defines the type of browser for running a Selenium Integration test case. Use this property in a project configuration file.
Values:
Note: If this property is not specified, the test runs in Firefox by default.
Defines the full path to the Selenium driver on a local computer that is used to run a Selenium Integration test in a Microsoft Internet Explorer browser. Use this property in a project configuration file.
C:\lisa-se\IEDriverServer.exe
Defines the full path to the Selenium driver on a local computer that is used to run a Selenium Integration test in a Chrome browser. Use this property in a project configuration file.
C:\lisa-se\ChromeDriverServer.exe
Defines the URL of a remote Selenium Server hub to run Selenium Integration test cases on a remote browser. Use this property in a project configuration file.
http://your_remote_hostname:4444/wd/hub
Note: You can define selenium.chrome.driver.path and selenium.ie.driver.path in the same project configuration file. A configuration file that contains selenium.chrome.driver.path or selenium.ie.driver.path cannot also contain selenium.remote.url.
Specifies the location of the parameter file used to set advanced options in the Selenium web driver.
Default: {{LISA_PROJ_ROOT}}/Data/selenium-capabilities.conf
The port properties control the dynamic assignment of ports when using auto configuration with the HTTP protocol in VSEasy.
If the minimum port is less than 1024, the value is set to 1024. If the maximum port is greater than 65535, the value is set to 65535. If the maximum port is less than or equal to the minimum port, both values are reverted to the defaults.
Default: 8000
Default: 65535
Specifies the name of the default group in the VSEasy console.
Default: VSEasy
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|