Runtime settings

Runtime settings let you fine-tune your scripts' and Vusers' behavior during test runs.

In this topic:

Open the runtime settings

Runtime settings control the behavior of Vusers executing scripts generated by VuGen and other script generation tools. They include pacing, logging options, and think time.

The Runtime settings dialog box lets you view and edit the runtime settings that apply to your script and Vusers.

To access the runtime settings, select a script in the Assets > Scripts tab and click the Runtime Settings button .

Back to top

Runtime settings nodes

The following table lists the nodes available in the Runtime settings dialog box.

Only runtime settings that are relevant to the selected script type are displayed and may be configured.

Setting	Description
Additional Attributes	Provide additional arguments for a Vuser script. Using this view, you can pass external parameters to existing scripts.
Browser	For TruClient scripts, you set the browser and proxy information in this section.
Browser Emulation	Configure the user agent and simulate browser cache for browser related runtime settings.
Digital Lab Settings	For TruClient Native Mobile scripts, you set the data collection, application, network virutualization, and transaction preferences.
Download Filters	Set the download filters for a script. You can filter addresses by a URL, host, or host suffix (TruClient). You can specify to include the listed entries, or to exclude the listed entries.
HTTP	Configure HTTP connection settings.
JMS Advanced	Set the JMS advanced runtime settings for Web Services scripts. For more information, see JMS Transport Overview below.
Log	Configure the amount and type of information to be recorded in the log. You can download the logs after the test run.
Miscellaneous	Configure miscellaneous settings for: Error Handling Continue on error (disabled by default) Fail open transaction on lr_error_messaqge Automatic Transactions Define each action as a transaction (enabled by default) Define each step as a transaction (disabled by default) VTS Access VTS port by query string. Enable this option to access your VTS server through a query string. For details, see Enable port forwarding in the VuGen Help Center.
Mobile Device	Change mobile device properties.
MQTT	Change MQTT runtime settings.
Other	For TruClient scripts, you set the snapshot preferences and non-interactive window size preferences (TruClient Web), and Action on error (TruClient Native Mobile). For details, see Dashboard actions and alerts.
Pacing	Control the time between iterations. The pace tells the Vuser how long to wait between iterations of your actions. You can control pacing either from the Load tests > Load profile tab or Runtime settings > Pacing view. To select which setting is applied during run time, in the Load tests > Load profile tab, select the Local pacing checkbox in the script's settings.
Preferences	For Web HTTP scripts, you configure settings in the following areas: Checks: Enable images and text checks (disabled by default). Web Performance Graph Generation: Allow the automatic generation of Web performance graphs (enabled by default). Advanced: Set advanced options such as the replay type, and whether or not to include the file name in automatic transactions. In addition this section allows you to customize HTTP, authentication, JavaScript, logging, and other internet-related runtime settings.
Proxy	Configure the proxy sever connection settings and list the exceptions. Note: Proxy settings are ignored by cloud-based load generators.
Replay	Configure replay settings, such as timeouts and user simulation. For TruClient scripts, you set the automatic transaction preferences in this section.
Run Logic	Set the run logic runtime settings for a script. You can: Add or remove actions (vuser_init, action, or vuser_end) and blocks in a block. Change the sequence order of actions and blocks in a block (move up or down). Configure the number of iterations a block is run. Configure the run logic for a block as: Sequential. The actions and blocks in each iteration of the block are run sequentially. Random. The actions and blocks in the block are run with a probability of a user-defined percentage. For example: You configure Block0 as random. Block0 contains Action1 and Block1. You configure Action1 as 20% and Block1 as 80%. During the total number of iterations, Action1 and Block1 run with a probability of 20% and 80% respectively (and not exactly 2 and 8 times). The total percentage of all the children in a block must equal 100%. Note: Run Logic settings are not copied when you copy runtime settings from one script to another.
Settings	For DevWeb scripts, use this section to specify the log level, proxy information, SSL, and when to create replay snapshots: Never or On error (Always is not supported).
SSL	Configure SSL connection settings.
Think time	Configure the think time settings, controlling the time that a script run waits between steps. These settings are designed to help you emulate a real user.

Back to top

Bulk runtime settings

In the Assets > Scripts tab, you can select multiple Web HTTP/HTML scripts or multiple TruClient scripts (TruClient – Web, TruClient – Mobile Web, or TruClient - Native Mobile), and update the runtime settings for all the selected scripts at the same time.

To update runtime settings for multiple scripts:

1. Select scripts of the same type that you want to update.

2. Click the Bulk runtime settings button . The Bulk runtime settings dialog box opens.

3. In the Bulk runtime settings dialog box, you can perform the following actions:

   1. Add a new setting. For the first setting, select a field from the dropdown list and then select a value for the field. For additional settings, click Add a field and then select the required field and value.

   2. Change the value for an existing setting. Select the new value for the required setting.

   3. Delete a setting. Click the Delete button for the setting you want to delete.

Back to top

Copy runtime settings

After you set the runtime settings for a specific script, you can copy them to other scripts of the same protocol.

To copy runtime settings and apply them to other scripts:

1. In the Assets > Scripts tab, select the script whose runtime settings you want to copy.

2. Click the Copy runtime settings button . The Select target scripts dialog opens with all scripts of the same protocol.

3. Select the scripts to which you want to apply the runtime settings, and click Apply.

Back to top

JMS Transport Overview

JMS is a J2EE standard for sending messages of either text or Java objects, between Java clients.

JMS implements Peer-to-Peer (also known as Point-to-Point) communication by defining a message queue as the target for a message. Multiple senders send messages to a message queue, and the receiver gets the message from the queue.

OpenText Core Performance Engineering supports point-to-point communication by allowing you to send and receive JMS messages to and from a queue.

Before you can send messages over JMS transport, you need to configure the following settings that describe the transport. You configure these settings in the Runtime Settings > JMS Advanced view for a script.

Setting	Description
Use external VM	Enables you to select a different VM. If this option is not selected, Vusers use the JVM provided with OpenText Core Performance Engineering.
Classpath	Specifies the Java classpath (vendor implementation of JMS classes).
Additional VM Parameters	Specifies extra parameters to send to the JVM, such as –Xms or –Xbootclasspath.
JNDI initial context factory	The fully qualified class name of the factory class that creates an initial context.
JNDI provider URL	The URL of the machine running the JNDI service.
JMS connection factory	The JNDI name of the JMS connection factory. You can only specify one connection factory per script.
JMS security principal	Identity of principal (e.g. the user) for the authentication scheme.
JMS security credentials	Principal’s credentials for the authentication scheme.
Number of JMS connections per process	The number of connections to create for each mdrv process. All Vusers sharing a connection receive the same messages. Fewer connections results in better performance. Default=1, maximum=50 Vusers. Allowed values range is 1 – 50.
Received message timeout options	Select an option: Infinite wait – wait as long as required for the message before continuing. No wait – do not wait for the message, and return control to the script immediately. If there is no message in the queue, the operation fails. Specify timeout – use defined value. If no message arrives by the timeout, the operation fails.
User defined timeout	Specify the number of seconds to wait for the message before timing out.
Automatically generate selector	Select the checkbox if you want OpenText Core Performance Engineering to automatically generate a selector for the response message with the correlation ID of the request.

Back to top

See also:

• VuGen runtime settings
• Scripts