To display the tabs while you are editing a script, click Script . If necessary, click to the left of the script and step names below the script timeline.
You can define default values for some of the settings described below.
Select the Profile tab to select the device, customize a profile, or change concurrency limits.
Select whether the script is for a Desktop Browser or a Mobile Device. If you select Mobile Device, mobile-specific options become available.
Click the mobile-only option Change device to open the Device Manager, where you can select the device you want the script to emulate. For details, see Using the Mobile Device Manager.
Changing from a desktop browser to a mobile device, or vice versa, removes any headers that are defined for this script and inserts the default headers for the device, if appropriate.
Use this section to change the concurrency limits:
Concurrent connections per host (max) – The maximum number of simultaneous HTTP connections allowed to connect to a single host. For Mobile Device scripts, a default value is entered automatically.
Simultaneous HTTP requests (max) – The maximum number of total requests allowed to execute at the same time. For Mobile Device scripts, a default value is entered automatically.
Click Customize to open the Customize Profile window, where you can change the device name, user agent, and other details. For details, see Using custom profiles.
Click Load to apply a saved profile (
.gprof file) to the script. When you open the file, the Customize Profile window opens so you can modify the profile if needed.
Save the current profile settings to a
.gprof file that you can import into other scripts: click Save, enter a file name, and click Save.
This option is available only when you select Mobile Device. To specify a location (to emulate a mobile device's ability to provide GPS information), click Select Location to open the Mobile Location dialog box.
From the drop-down list, select one of the following settings:
No Location – The default. The script will not use location information.
Custom Location – Enter latitude and longitude in the fields. For southern latitude and western longitude, use negative numbers.
Use the mobile node location – With this option, when the script is uploaded to the Dynatrace Portal and provisioned, it uses the location of the mobile node that runs the script.
Because node coordinates are not available when you run the script locally, selecting this option displays fields for you to enter latitude and longitude GPS coordinates for local playback. If you leave these fields blank, the script will use the default location of the Dynatrace office in Detroit, Michigan. When the script is uploaded to the Dynatrace Portal, the node location overrides these local playback coordinates.
In special cases where you are emulating something other than a browser, enter the appropriate headers on this tab. For example, to emulate a web service, you can enter the SOAP headers for an XML request. By default, the script uses the headers the selected browser sends, so in most cases you do not need to enter anything here. For a mobile device, the headers that a device sends with each request are displayed and you can edit them here.
The user agent is a header sent on each request that identifies the client browser. Changing this field does not change the browser that the script is played back in (that depends on the playback agent), but does change what the server or web application sees as the client. By default, the User Agent header is the header for the playback agent. If you selected a mobile device in the Profile tab, its user agent header is entered. You can enter any header string. To use one of the headers the Recorder provides for recent versions of commonly used browsers, click Change To and select the browser.
Select this tab to define special script-level variables. For details, see Setting parameters.
The Playback tab contains options for collecting additional data during script playback.
Enable Flash playback
This option is only available for Desktop Browser scripts.
Flash playback is enabled by default. If this option is not selected, the playback may only call for the basic Flash objects to be downloaded. When the option is selected, additional objects are called by Flash to provide you with a more comprehensive view of the load. In a Flex environment, it is almost always true that more objects will be called.
If a site auto-executes Flash as part of the
onLoad event, it usually causes a large increase in the payload. When Flash playback is enabled, the Recorder shows the performance impact of the auto-execute and provides you with accurate statistics for the true payload, not only the initial objects.
Interactions with Flash features (for example, muting the sound or pausing and restarting play) are not recorded.
For more information, see Recording and playing back Flash.
Enable Silverlight playback
This option is only available for Desktop Browser scripts.
If your script has steps that include Silverlight content, you can Enable Silverlight Playback.
If you do not select this option, the playback may only call for the basic Silverlight objects to be downloaded. If you do select the option, additional objects are called by Silverlight to provide you with a more comprehensive view of the load.
Interactions with Silverlight features (for example, muting the sound or pausing and restarting play) are not recorded.
Select this option to use the SPDY transfer protocol during script playback. For example, you can create separate scripts that record the same actions with SPDY enabled and disabled, to compare performance in each situation.
When you play back the script with SPDY support enabled, the results views include SPDY data.
This option is not available for the IE agent.
Include client (non-network) time in results
When you select this option, the waterfall chart displays non-network time as gaps in the chart.
When you select this option and play the script using the Firefox, Chrome, or Mobile playback agent, the waterfall chart displays W3C navigation time metrics.
Run script as a repeat visitor
This option is only available for the IE agent.
When you enable this option, the script emulates a user returning to the website after previously visiting it: as if downloaded objects are cached and do not need to be downloaded again.
IE Compatibility Mode
The IE Agent supports Compatibility Mode in the Internet Explorer browser.
Use the IE Compatibility Mode setting to specify the browser version when playing the script using the IE Agent. This setting lets you measure how your web application performs in a specific version of Internet Explorer.
Click Change To, then select the version from the list.
For Desktop Browser scripts, you can select to play back the script using IPv4 only (the default), IPv6 only, or IPv6 Preferred (play back on IPv6 if available, otherwise on IPv4). If IPv6 is available, select an IPv6 option; otherwise use IPv4.
For Mobile Device scripts, the IP Mode options are not displayed. Only IPv4 is supported.
You can provide client-side certificates for playback. For details, see Using certificates.
Use this tab to map the domains that will be used by the script to specific destination IP addresses or hostnames. Entering values here causes the test to ignore the system/Internet DNS servers. You may find this useful if you are testing your network or testing a website that is not yet public.
Use host mapping
- Select the Hosts tab and click at the far right.
A new set of definition fields is added to Host/IP Mapping.
In the Hostname field on the left, enter the hostname to map, for example,
From the Map To drop-down list, select whether to map to an IP Address or a Hostname.
In the Destination column, enter a maximum of three IP addresses or hostnames.
For more information, see Host mapping.
Delete a mapping
Click to the right of the host mapping to delete it.