Skip to main content

RTV administration

RTV administration

Adding plugins

POST Data Matching plug-ins are DLL files that are created by Tealeaf developers.

When new plug-ins are available, you can make them available for RTV to use by completing the following steps.

  1. Acquire the DLL file.

    For RTV to detect the plug-in, the file name must have a TLReplayPlugin prefix and a .dll extension:

    
TLReplayPlugin*.dll
  2. Copy the plug-in into the RTV installation directory.
  3. If you are in RTV, close the application.
  4. Start RTV.
  5. From the RTV menu, select Tools > Options.
  6. Click the Plugins tab.
  7. Click Add.
  8. Select the plug-in.
    Note: UNC paths are not supported.
  9. Click Open.

    The plug-in is displayed in the plug-ins tab and is usable by RTV.

  10. If there is already a plug-in that is a match for the same content type, you must configure the plug-in affinity.

When a plug-in is newly deployed to RTV, you must configure the CX Passive Capture Application to capture the new content type.

Interpreted pages

Some web applications may interpret pages before it delivers them as rendered HTML to the browser. For example, your application can use executable files (.exe) as a URI, and the file generates an HTML text page on the web server that is delivered to the browser. RTV must know whether an unusual file extension must be interpreted as a delivered HTML text page.

By default, the standard file extensions for file types that are commonly used on the web are included and selected. These selected files are interpreted as part of a user impression.

  • If your application uses a different file extension and if the file does not deliver the CONTENT_TYPE information in the response headers, you must add and select that file extension.
  • If the response header contains a CONTENT_TYPE and that CONTENT_TYPE is already known by RTV, you do not have to add the file extension here. For example, there is no .jsp or .do file extension that is listed here, since most Java™ Platform, Enterprise Edition servers using these file extensions include the correct CONTENT_TYPE in the response.

Access to the Event Manager

RTV is configured to connect to the Portal server, through which RTV can access the Event Manager. Use the cxImpact Options tab to build the URL to access the Event Manager.

  • The value for the Portal server in this tab must match the value for the Portal Server in Search Server configuration.
    Note: If you use security transport to connect to your Portal, you must enter the protocol identifier. For example: https://OurPortal" scope="external". The transport protocol for the Portal is defined in the Portal Server definition in the Portal Management page.

    If you don't use HTTPS, the protocol identifier is optional.

    Don't use localhost unless you use RTV on the Portal server.

  • All other queries or references to the Portal Server from RTV are managed through Search Server.
  • The Event Manager is a Portal-based utility for creating and managing Tealeaf events.

If Portal authentication is enabled: In the cxImpact Options tab, you must populate the RTV user's Portal ID and password to connect to the Canister to search, retrieve sessions, and edit events.

Note: If no data is entered when you install RTV, the first time you use RTV under Portal Authentication, you are prompted for your user name and password.

If NT authentication is enabled: The user ID and password settings do not apply. Connection information is managed through the NT domain into which the user is already logged.

Mobile licensing

Through the cxImpact Options tab, you can review status of the CX Mobile license and perform updates as needed.

In the Mobile License area, you can review the current state of the license. If CX Mobile has been licensed, you must acquire the license from one of the servers to which the license has been deployed.

Note: Before you apply any changes to the mobile license used by RTV, this updated license must be applied through the Portal to the rest of the Tealeaf CX solution.

If CX Mobile is not licensed, an Invalid message is displayed.

Note: When CX Mobile module is not licensed, the following limitations are applied to replay of mobile-based sessions:
  • No display of mobile-specific events, such as scroll and touch
  • No display of mobile device data during replay
  • No use of a mobile skin (Extended user agent parsing is also required)
  • No display of device orientation changes
  • No resizing of the screen to the mobile browser dimensions

The underlying data is captured independent of the license; enabling the license allows mobile-based replay of sessions that are already captured.

Note: Updates to the mobile license do not affect sessions that are currently loaded at the time of the update. Any opened sessions must be closed and reopened to apply the new mobile license.
  1. To check for an updated mobile license, click Update.
  2. Enter the server name and port number for the Search Server where this license information can be acquired.
    • Typically, this value points to the Portal Server and uses the port number 19000.
    • The default values are acquired from the Search Server to which RTV is configured to acquire sessions. You can change the values in this dialog or connect to a different Search Server.
  3. To update the license, click OK.
  4. RTV queries the Search Server for an updated mobile license. If one is available, it is downloaded for use in RTV. The license expiration date is updated to reflect the new mobile license.

Related articles

  • Acoustic Campaign

    • Customers

    About acoustic

    © Copyright 2024 Acoustic, L.P. All Rights Reserved.