Through TMS, the following configuration items are available.
Auth Master Server
- Identifies the server that manages authentication. In environments where the Replay Server is on
the same server as the Portal application, this value is
- Time (in minutes) that static resources are kept in the cache. If not accessed again before the timeout expires, items are deleted from the cache.
- Enables caching for each browser type. The default setting is 0, which means caching per browser
type is not enabled.
To enable caching for each browser type, set the value to 1.Note: Set
1only if your site returns different content for the same URLs based on the User-Agent header.
- Specifies the number of renderer instances using the Chrome/WebKit browser to spawn on the
Replay Server. This definition is available in the raw configuration only.Note: This renderer is only needed if your web application supports the Chrome browser or mobile web browser sessions.
Days to Keep Logs
- Number of days to retain Replay Server log data. The default value is 30 days.
- When set to 1,
DisableRendererImageLoadingstops an image from loading during replay rendering to improve performance. If this setting is enabled, the
FakeImagesOnRendersetting is disabled.
- Set to 1 to enable DOM Capture (default), or set to 0 disable DOM Capture. Enabling DOM Capture
allows the Replay Server to parse DOM capture data and then use it to show Replay.
When you enable DOM capture, any UI Events that do not contain DOM capture data are hidden, though these UI events are still available to make Step Events in Request data.
- Set to 1 to enable Native Replay (default), or set to 0 disable Native Replay. Enabling Native Replay allows the Replay Server replay sessions from mobile device users.
Exec UI Events Now
- When enabled, UI events in the session are rendered while the hit is rendered. This
configuration may assist if pages rendered in BBR appear to display UI events on the page after
which the event occurred.
By default, this setting is
False, which means that events are rendered after the hit has been rendered.
Fake Images On Render
- When set to 1, the Replay Server generates stub 1x1 pixel images to be used for all image
requests, instead of retrieving real images from the origin site. By default, this option is
disabled, but it can be enabled if image load time is significant.
- This definition is available in the raw configuration only.
- Specifies the Internet Explorer emulation mode used by
BBRIERenderer.exe. By default,
BBRIERenderer.exeuses the Emulation Mode of the minimum version of Internet Explorer supported by Experience Analytics.
If you want
BBRIERenderer.exeto render using a different version of Internet Explorer, set the
IEEmulationproperty to the Emulation Mode associated with the version of Internet Explorer that you want to use.
BBRIERenderer.exerenders the IE sessions using the mode specified.
For information about emulation modes for the different versions of Internet Explorer, consult the Microsoft™ Developer Network article about Browser Emulation.Note: If you change the IE emulation mode, all renderers need to be restarted by restarting the Replay Server.
Insert Missing or Cached Pages
- When enabled, this option attempts to insert pages that are missing in the session or that were
cached by a content delivery network (CDN) by retrieving them from the origin server. By default,
this setting is disabled. Note: This option should be enabled in isolation to rectify simple issues with replay of missing data. Enabling this setting may result in false positives, in which query parameters in the URLs for UI events cannot be matched with pages stored in the session. In these cases, this option causes the Replay Server to reach for the page from the origin server; for UI event pages, the page does not exist, which may cause replay problems.
- Browsers cache previously visited pages and do not issue a request back to original server when user goes back to those pages. This option allows to synthetically insert viewable pages into navigation list when UISDK is instrumented on the website. UI events will be attached to the synthetic pages for smooth replay.
- This option attempts to inserts missing back buttons pages from UI events.
Performance InitUI event and its
WindowHrefvalue. It goes through the session looking for miss pages based on the
- When set to
Yes, logging is enabled.
- This option is the maximum number of renderers that are dedicated to render a session selected out of available pool of renderers. Other renderers will not be touched to render the given session.
- Specifies the number of renderer instances using the Mozilla Gecko browser to spawn on the
replay server. The default setting is 4. You should not have to change this value.
This definition is available in the raw configuration only.
- When enabled, only the current page and the page following are rendered until another page is requested. This improves session load time.
- The default value is 38000. This property defines the server port through which Replay Server interactions are performed. For advanced configuration of your replay server, contact your account representative or Professional Services .
Proxy Auth Password
- When a proxy server is between BBR users and the public Internet, this setting specifies the password to use for authentication with the proxy.
Proxy Auth Username
- When a proxy server is between BBR users and the public Internet, this setting specifies the username to use for authentication with the proxy.
- Render delay is the amount of time (in seconds) that the renderer will wait after the page is loaded (and UI events are run) before taking the snapshot. After the initial page snapshot the UI events are run one at a time (snapshot after each one after renderer delay.
Session Idle Timeout
- Number of minutes of permitted inactivity for a BBR session after which the session is automatically timed out.
- Navigation list includes UI Capture JSON message Client State (Type 1) message when enabled.
- Type 7
- Type 2
- Navigation list includes UI Capture JSON message's Control (Type 4) message when enabled.
- Path to directory to temp storage space for replay.
- When enabled, this option removes redundant UI events such as click a text field from the session that is delivered during replay. Events such as these do not offer additional value.
- To delete duplicate adjacent UI events for replay purposes, set this value to 1.
- This list displays the potential UI Event SubTypes that you can specify to skip (value=1) or to replay (value=0). Depending on how your site is rendered, some of these sub-types may generate a significant volume of events or may not replay correctly, so these options can be used to fine-tune the BBR replay experience specific to your web application.
- When this value is set to 1, the Replay Server stores request data from the rendered session in a local file. When set to 0, the request data is stored in memory.
White List Enable
- When enabled, you may specify whitelists of URLs that are permitted to contact the origin server
for the defined domain.
These whitelists are specified as regex patterns in the Portal Management page.
UseReplayProxyparameter can be set to 1 or 0.
UseReplayProxyto 1 (default) to retrieve static content from the Replay Server.Set
UseReplayProxyto 0 to retrieve static content directly, instead of through the Replay Server, with the URL displaying as it did on the session originally.Note: The browser might refuse to retrieve static content if there is a mix domain / same origin issue. For example, if the Experience Analytics server is
HTTPSand the public website is
HTTP. See https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy for information about Same-origin policy.
UI event sub-types
The following UI event subtypes can be enabled or disabled for replay in BBR. When disabled, these events are hidden during replay; the data remains in the session for eventing and other purposes.
These settings apply only to the rendering of sessions in BBR. If your implementation of UI Capture has been configured to not capture a sub-type, the data is not present in the session, and changing the corresponding setting here has no impact.
||Focus has been removed from the element.||0|
||Element has received focus.||1|
||Focus has been moved off of element.||1|
||A click of the mouse button has been recorded on the element.||1|
||A clicked mouse button has been released on the element.||1|
||The mouse wheel has been scrolled over the element.||0|
||The element has been scrolled||1|
||The element has received focus, lost it, and remains unchanged.||0|
||The element has received attention.||0|
||The element has been resized.||0|
||The element has been loaded on the page.||0|
||The element has been unloaded from the page.||0|
||The mouse has moved out of the element.||0|