Property value descriptions
This section describes the property values that are displayed in
the Property tab, and a table indicating the default values for each
profile type.
- Abort RFT script on timeout
- When the timeout value is reached the Rational® Functional Tester script is aborted.
The following values are valid for this property:
- True
- Aborts the script when the timeout is reached.
- False
- Disables the abort function.
- Agent Default
- Use the setting specified in the agent configuration. This is the default value.
- Collect instances
- Indicates when data is collected.
- TRUE
- Collects all instance data. This includes performance data for every transaction that matches the specified IP address, URL, or data pattern. For a high-traffic website, a large amount of performance data can quickly accumulate.
- FALSE
- Collects no instance data. It disables the collection of instance data and only collects a single statistical summary record for the aggregate interval. This choice provides a single record and the lowest overheard in terms of the amount of data that the software collects, retains in the database, and displays.
- On Slow
- Collects transaction instance data for a transaction that is deemed to be slow. This property value also accounts for failed transactions.
- On Failure
- Collects transaction instance data after a violation occurs.
- Concurrent CLI Playback
- Indicates if more than one instance of the same command can be run concurrently. Valid values for this property are True or False. If concurrent playback causes performance or other problems, set this option to False. If you select False, the software queues all non-concurrent CLI commands and runs them sequentially. All concurrent CLI commands are run simultaneously and are not affected by any non-concurrent commands.
- Enable screen content capture
- Indicates whether screen content is captured. Valid values are True (enable screen capture), False (disable screen capture), or Agent Default (use the setting from the agent configuration).
- Importance
- Indicates the business value of the monitored transaction. The
following values are valid for this property:
- Discretionary
- Very_Low
- Low
- Medium
- High
- Very_High
- Highest
Note that this Importance value can affect the sorting of applications displayed in Rank order in certain workspaces and views. For example, applications that are displayed in the Application Availability Historical Summary view of the Applications workspace are sorted in rank order, but the rank value is calculated using percent failed and slow, as well as Importance values. So the importance attached to monitored transactions can affect the sorting that is ultimately displayed.
- Max response time threshold (seconds)
- The maximum acceptable slow response time, in seconds, for a single transaction instance during the data interval. If a transaction exceeds this response time value, it is considered to be a failed transaction. By default this property is left blank or is set to zero, meaning that failed transactions are not identified.
- Min. response time threshold (seconds)
- The maximum acceptable response time, in seconds, for a single transaction instance during the data interval. If a transaction exceeds this response time value, it is considered to be a slow transaction. By default, for Transaction Tracking this property is set to 10 seconds. If this property is left blank or set to zero, slow transactions are not identified.
- Number of retries
- The number of times to retry the transaction after the first attempt
fails before sending a time out event to the management server.
For example, if the number of retries is 4, the transaction is attempted up to five times (once, plus the four specified retries) before sending a time out event to the management server.
- Retry lag time (seconds)
- The number of seconds to wait between each retry. For example,
if you set the number of retries to 3 with a lag time of 1, the software
times out and generates an event when both of the following events
take place:
- The software tries the transaction four times (once as part of the playback, plus the three specified retries).
- The software waits one second between retries.
Tip: For example, if you set Number of Retries to 3, Retry Lag Time to 1, and Timeout Period to 30, the software times out and generates an event when all of the following events occur:- The software tries the script four times (once as part of the playback, plus three retries). Each time, the script does not respond in 30 seconds.
- The software waits one second between retries.
If the Timeout Period is too short, the software kills the process after retrying for the number of times specified in Retry Lag Time, You also should add some buffer. For example, if you have a script that takes 5 minutes to run and you want to add a 1 minute buffer, enter 360 to set up a 6 minute Timeout Period.
- RFT application configuration
- Use the application configuration (provided by Rational Functional Tester) that is specified
in the script, or use the configuration specified on the agent. The
following values are valid for this property:
- Exported
- Use the application configuration provided in the script.
- Local
- Use the application configuration located on the agent. This is the default value.
- Sampling Percent
- The percentage of transactions to be sampled during the data interval.
For example, 50 returns 50% of the transactions. Note: This cannot be changed on robotic profiles.
- Script interval (minutes)
- The frequency at which the script is played back, in minutes.
- Success Return Code
- The expected return code value returned by the CLI command. The default expected return code for most executable commands and scripts is 0. Script writers can cause their scripts to exit with unexpected return code values to indicate to the software that an error occurred. If the command returns a value that does not match the expected return code value, then the monitor fails the transaction and optionally sends an Expected Return Code failure event if one is defined for the monitor. You can only view the filter and reporting properties panel. You must edit the transaction itself to change the values
- Terminate RFT and reboot when not responding
- When the Rational Functional
Tester process is not responding, the process is terminated and the
system is rebooted. This property is available only for Rational Functional Tester Robotic Response
Time scripts. The following values are valid for this property:
- True
- Always terminate and reboot.
- False
- Never terminate and reboot.
- Agent Default
- Use the setting specified in the agent configuration. This is the default value.
- Timeout period (seconds)
- The amount of time, in seconds, to wait for the script to respond before timing out and retrying.
The following table specifies default values for each property based on the profile type.
| Property | Robotic Response Time Robotic script | Robotic Response Time CLI playback command | Transaction Tracking ARM type | Transaction Tracking non-ARM type | Web Response Time |
|---|---|---|---|---|---|
| Abort RFT script on timeout | Agent (Only available for RFT scripts.) | Agent (Only available for RFT scripts.) | Not applicable | Not applicable | Not applicable |
| Collect instances | False | False | False | Not applicable | On Failure |
| Concurrent CLI Playback | Not applicable | True | Not applicable | Not applicable | Not applicable |
| Enable screen content capture | False (Only available for RFT scripts, and for RPT scripts that use HTTP protocols.) | False (Only available for RFT scripts, and for RPT scripts that use HTTP protocols.) | Not applicable | Not applicable | Not applicable |
| Importance | Medium | Medium | Medium | Not applicable | Medium |
| Max response time threshold (seconds) | None | None | None | None | None |
| Min. response time threshold (seconds) | 10 | 10 | 10 | 10 | 10 |
| Number of retries | 1 | 1 | Not applicable | Not applicable | Not applicable |
| Retry lag time (seconds) | 3 | 3 | Not applicable | Not applicable | Not applicable |
| RFT application configuration | Agent (Only available for RFT scripts) | Agent (Only available for RFT scripts) | Not applicable | Not applicable | Not applicable |
| Sampling percent | 100% | Not applicable | 100% | Not applicable | 100% |
| Script interval (minutes) | 15 | 15 | Not applicable | Not applicable | Not applicable |
| Success Return Code | Not applicable | 0 | Not applicable | Not applicable | Not applicable |
| Timeout period (seconds) | 120 | 120 | Not Applicable | Not Applicable | Not Applicable |