Through the Replay Rules text file, you can use control host and port remapping, custom page modification, and the fields in the session's requests that are used for the URL, host name, and more.
The RequestMapping
node contains a standard set of entries that are found in the session requests and rarely must be modified.
The replay configuration is an XML file in the following location on the Replay Server:
<install_directory>\System\ReplayServerProfile.xml
Host and port remapping and other custom page modifications are applied to sessions based on their host names. For example, to customize sessions from www.sample.com
, the following node must be displayed in ReplayServerProfile.xml
:
<HostProfile name="www.sample.com">
Within the HostProfile
node, the follow entries control remapping:
<!-- RemapMode values: off, on, null -->
<RemapMode value='on' />
<RemapHost value="www.sample2.com" />
<!-- There can be multiple RemapPort nodes -->
<RemapPort valueIn="49191" valueOut="80" />
RemapMode
toggles remapping, or it remaps a host to a null host, which can always return a 404 status code on any request.
- With
RemapMode
enabled, theRemapHost
node specifies the host name to which to remap.
RemapPort
is used to remap port numbers to other numbers. This value is needed when images or other page elements are available on a port other than the port number that appears in the captured data.
IgnoreURL
specifies the URLs that must not be displayed in the NavList. It supports the asterisk wildcard (*
). In the following example, any URL matching /path.axd
with query parameters is ignored:
<IgnoreURL value="/path.axd?*" />
ResponseMod
is used to apply regular expressions to response pages to alter them as might be required for replay. For example, you might use it to disable a JavaScript™ that forces a page to break from a FRAMESET if it finds itself in one. The ResponseMod
node has the following attributes:
<ResponseModify url=".*" pattern="top.location != location"
replacementString="0" occurrences="first" id="7"/>
PopupURL
Similar to IgnoreURL rules, PopupURL rules can be used to identify popup pages. BBR includes these pages in the NavList and displays them in the main replay window.
<PopupURL value="/path/popup.asp?*" id="3"/>
ExternalFileModify
These rules are used to modified external files that are referenced in the response. In the following example, an external JavaScript file is modified in order to change the value of this.fadeDuration
from .8
to .001
, which causes the fade for the page to be much shorter.
<ExternalFileModify id="409"
url="/path/Details.js\?cache=.*"
pattern="this.fadeDuration = .8;"
replacementString="this.fadeDuration = .001;"
occurrences="all"/>
Masking on-demand privacy rule configuration
As needed, you can configure privacy rules to be applied to sensitive data only during replay, which enables the original session to retain the data for search and reporting purposes.
These privacy rules can be configured to block or mask sensitive data without affecting the stored session.
Masking on-demand privacy rules are applied through Search server.
Replay rules and UI capture
If you deploy CX UI Capture for AJAX by using the XML method of submitting client-side events, you must configure special rules to make replay work effectively.
As needed, you can configure a replay rule to disable UI Capture during replay.