Skip to main content

RTV administration

RTV administration

Configuring and testing plugins on CX RTV

Use the CX RTV client to perform configuration and to test plugin operations.

Install CX RTV on your local Windows™ system and verify that the appropriate plugins are available in RTV.

Through the Plugins tab in RTV, you can define the affinity value of each plugin. Because it's possible to deploy multiple POST data matching plugins for a single content type, you can configure the affinity value for each plugin to indicate the priority and, hence, the order in which the plugins are used.

Multiple plugins might be used when one plugin is required to handle a specific URL or area of the site, with the other plugin being the default plugin for the content type elsewhere on the site.

Affinity values range from 0.0 to 1.0. Plugins with a greater affinity value are used for evaluating the same content type first.

When the Replay Rules are deployed to the Replay Server, the affinity values defined in RTV are applied to the BBR plugins.

Complete the following tasks in the order listed.

Configuring PCA to capture new content types

By default, the PCA captures content types used by most standard web applications. For rich internet applications, the PCA typically must be configured to allow the content types in use for your web application.

In hits captured by Tealeaf, the content type value is inserted into the [env] section of the request. In the example below, the content type is set to text/xml:


[env]
HTTP_CONTENT_TYPE=text/xml

When this value matches the value inserted for the plugin content type, the associated plugin is used for matching purposes.

  1. In RTV, select Tools > Options?.
  2. Click the Plugins tab.
  3. For each listed plugin:
    1. Select the plugin.
    2. Click Properties.
    3. Copy the entire string. Paste it into a text file for safekeeping.
    4. Repeat the above for each listed plugin.
  4. Verify that the PCA is capturing each of the content types that you have listed in the text file.
  5. If the content type is not being captured, it must be inserted into the appropriate capture type list in the Pipeline tab of the PCA Web Console.
    Note: When you enable a new capture type, the PCA begins immediately capturing the content. Depending on the volume of content, the new capture stream can affect performance and processing throughout the Tealeaf system.

Searching for sessions by content type

After you have enabled capture of the appropriate content types and waited a sufficient period of time for Tealeaf to capture sessions using this type, you can perform the following steps to locate a session in which the content type appears.

The basic method for locating these sessions is to specify a search using URLs to pages that use this content type.

Note: If you are unaware of the appropriate URL to use, you should contact your web development team. You can also contact Tealeaf Professional Services for assistance.

Verifying the plugin

To verify the plugin is working, complete the following steps.

  1. Load a session using the content type into RTV. You can load from the Portal session list.
  2. In the toolbar, click the Request button.
  3. Step through the requests of the session until you locate the appropriate entry in the [env] section of the request: 
    
HTTP_CONTENT_TYPE=text/xml

    where text/xml is replaced by the content type that you are testing.

  4. From the RTV menu, select View > Page Load Details.
  5. In the Page Load Details column, scan the Method column. Look for a value that includes parentheses. For example: 
    
Post(244)
  6. Page objects such as the above indicate that the POST data was matched. Right-click the object and select the PostData option.
  7. You can review the contents of the sub-menu to identify the data that was matched. If the sub-menu is empty, no data was matched for the POST.

Deploying configuration to Replay Server

After you have installed the DLL files on the Replay Server, you can use the following steps to apply the plug-in configuration from your installation of RTV to the Replay Server, which provides these configuration options to each BBR user in the environment.

Before you enable POST Data Matching plugins to BBR through Replay Server, the plugin DLL files must be installed on the Replay Server.

The following steps deploy all replay rules in your RTV configuration to the Replay Server. You should create a copy of your replay rules file and modify it to remove any personal replay rules that you want deployed before deploying the copy to Replay Server.

  1. From the RTV menu, select Tools > Options.
  2. Click the Profiles tab.
  3. To modify your profile rules for plugins, click Edit Raw Profile.

    At the top of the file are the listed plugins currently installed in RTV:

    
<Plugins>
    <ReplayHitMatchPlugin name="AMF" version="8.3.0.8326" 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.3.0.8326" 
          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="FormDataCustom" version="8.3.0.8326" 
          interfaceVersion="1" errorCode="0" errorMessage="">
        <HitType contentType="application/x-www-form-urlencoded" 
                handlesQueryString="true" wantResponseData="true" 
                haveCustomOptionsDialog="false" 
                haveCustomIgnoreParamDialog="false" 
                haveCustomResponseDisplay="false"
                 haveCustomPostDataDisplay="false" affinity="0.4">
            <URLFilter pattern="http://stuff.com/page1.asp" reqVar="" 
                      reqVarValue=""/></HitType>
    </ReplayHitMatchPlugin>
    <ReplayHitMatchPlugin name="XML" version="8.3.0.8326" 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>
  4. Make any modifications as necessary.
  5. To save your changes, click Save Changes & Exit.
  6. Enter the master Replay Server in the Default Profile textbox.
  7. Click Upload Settings to Server.

Your replay profile has been applied to the Replay Server.

Related articles

community icon

Join the community

Ask questions, share best practices, and connect with fellow marketers.

Ask a question

Academy

Read how-to articles, guides, and more to help you on the path to success.

Learn more