Configuring the Replay Server

The Replay Server manages the replay of sessions to Browser Based Replay clients. Whenever a BBR user queries for a session to replay, the query is passed through Search Server to retrieve the session, which is delivered to the user's browser through Replay Server.

Note: To effectively replay the complete session, the Replay Server must have access to the static content, including images, Javascripts, and stylesheets, that are referenced in the session.

There might be some limitations in the replay experience due to differences in how session content is rendered for display in specific devices.

During the initial installation, one Replay Server is installed as part of the cxImpact installation. This server is initially designated as the master Replay Server. By default, the Replay Server that is installed is 64-bit. As needed, more Replay Servers can be installed and configured.

During installation, a reference to the initial master Replay Server is added to the Portal Management page, which enables BBR users to request and receive sessions from the Replay Server through the Portal application.

To view or edit Replay Server configuration settings:

Log in to the Portal as an admin user.
From the Portal menu, navigate to TMS.
From the View drop-down, select Servers.
In the Servers view, select the desired server to drill down to components.
Click the Replay Server node.
Select Replay Server configuration.
In the Config Actions panel, click View/Edit.

The Configuration Editor is displayed.

After you make changes to the Replay Server configuration, the following steps are required:

Push the configuration to all servers through TMS.
Restart the Replay Server.

Configuring proxy access for Replay server

When a session is opened in Browser Based Replay, static content such as images and stylesheets is requested from the Replay Server. If the Replay Server does not have the content stored locally in a cache, then it requests the content from the origin server.

If a proxy server is in place between Tealeaf and the origin server, you must configure access for Replay Server to the origin server through the proxy.

Updating the Replay server profile for DWR POST data matching

If your site uses the DWR library for Javascript/Java™ interactions, you must update the profile stored on the Replay Server to use the appropriate POST data matching plug-in when DWR requests are detected in session data during replay.

POST data matching plug-ins are used to match requests of specified content type to their corresponding responses in session data. POST data matching plug-ins enhance the probability of properly matching each request to its corresponding response.

DWR POSTs must be passed through the pre-existing FormData plug-in for proper matching. To configure, you must include a reference to the type of hit in the plug-in FormData configuration on the Replay Server. Complete the following steps.

Login to the server hosting the Replay Server.
Navigate to the following directory:
```
<Tealeaf_install_directory>\System
```
Edit the ReplayServerProfile.xml file.

Locate the following configuration. It may be at the top of the file:


<Plugins>
    <ReplayHitMatchPlugin name="AMF" version="8.4.0.8436" interfaceVersion="1"
errorCode="0" errorMessage="">
        <HitType contentType="application/x-amf" handlesQueryString="false"
              wantResponseData="false" haveCustomOptionsDialog="false"
              haveCustomIgnoreParamDialog="false"
              haveCustomResponseDisplay="false"
              haveCustomPostDataDisplay="false" affinity="0.5">
            <URLFilter pattern="" reqVar="" reqVarValue=""/></HitType>
    </ReplayHitMatchPlugin>
    <ReplayHitMatchPlugin name="FormData" version="8.4.0.8436"
         interfaceVersion="1" errorCode="0" errorMessage="">
        <HitType contentType="application/x-www-form-urlencoded"
               handlesQueryString="true" wantResponseData="false"
               haveCustomOptionsDialog="false"
               haveCustomIgnoreParamDialog="false"
               haveCustomResponseDisplay="false"
               haveCustomPostDataDisplay="false" affinity="0.5">
            <URLFilter pattern="" reqVar="" reqVarValue=""/></HitType>
    </ReplayHitMatchPlugin>
    <ReplayHitMatchPlugin name="JSON" version="8.4.0.8436"
         interfaceVersion="1" errorCode="0" errorMessage="">
        <HitType contentType="application/json" handlesQueryString="false"
               wantResponseData="false" haveCustomOptionsDialog="false"
               haveCustomIgnoreParamDialog="false"
               haveCustomResponseDisplay="false"
               haveCustomPostDataDisplay="false" affinity="0.5">
            <URLFilter pattern="" reqVar="" reqVarValue=""/></HitType>
    </ReplayHitMatchPlugin>
    <ReplayHitMatchPlugin name="XML" version="8.4.0.8436"
         interfaceVersion="1" errorCode="0" errorMessage="">
        <HitType contentType="text/xml" handlesQueryString="false"
               wantResponseData="false" haveCustomOptionsDialog="false"
               haveCustomIgnoreParamDialog="false"
               haveCustomResponseDisplay="false"
               haveCustomPostDataDisplay="false" affinity="0.5">
            <URLFilter pattern="" reqVar="" reqVarValue=""/></HitType>
        <HitType contentType="application/msbin1" handlesQueryString="false"
               wantResponseData="false" haveCustomOptionsDialog="false"
               haveCustomIgnoreParamDialog="false"
               haveCustomResponseDisplay="false"
               haveCustomPostDataDisplay="false" affinity="0.5">
            <URLFilter pattern="" reqVar="" reqVarValue=""/></HitType>
    </ReplayHitMatchPlugin>
</Plugins>

The above configuration represents the configuration for the POST Data Matching plug-ins on the Replay Server.

Locate the FormData plugin configuration. It should look like the following:


<ReplayHitMatchPlugin name="FormData" version="8.4.0.8436"
   interfaceVersion="1" errorCode="0" errorMessage="">
    <HitType contentType="application/x-www-form-urlencoded"
         handlesQueryString="true" wantResponseData="false"
         haveCustomOptionsDialog="false" haveCustomIgnoreParamDialog="false"
         haveCustomResponseDisplay="false" haveCustomPostDataDisplay="false"
         affinity="0.5">
        <URLFilter pattern="" reqVar="" reqVarValue=""/></HitType>
</ReplayHitMatchPlugin>

Just before the </ReplayHitMatchPlugin> closing tag, insert the following configuration:


<HitType contentType="text/plain" handlesQueryString="false"
wantResponseData="false" haveCustomOptionsDialog="false"
haveCustomIgnoreParamDialog="false" haveCustomResponseDisplay="false"
haveCustomPostDataDisplay="false" affinity="0.5" enabled="1">
        <URLFilter pattern="" reqVar="" reqVarValue="" enabled="1"/>
    </HitType>

Save the file.
Through TMS, restart the Replay Server.
If you have additional Replay Servers in your environment, this change must be applied to those servers.

Note: Individual users of the CX RealiTea Viewer must apply a similar change to their local replay profiles.

Configuring proxy access for Replay server

Updating the Replay server profile for DWR POST data matching

Join the community

Academy

Search, replay, and session administration

Configuring proxy access for Replay server

Updating the Replay server profile for DWR POST data matching

Related articles

Join the community

Academy