Tealeaf cxVerify is a Windows™ service that runs on the Tealeaf CX server.

Typically, it runs on a separate server from the primary Tealeaf CX server, but it can be installed on the primary server if needed. You can run only one Tealeaf cxVerify server at any time.

cxVerify uses an Extraction API to extract the archived session data. In a single-machine environment, data is extracted from the Long-Term Canister.

Tealeaf cxVerify system runs the following tasks.

1. Queries the Tealeaf CX Server to return a list of matching sessions.
2. Queries the Tealeaf CX Server to return the XML session document for each matching session.
3. Parses the returned XML and extracts name-value data such as URL field name and URL field value.
4. Packages the customer session data into a replayable file format.
5. Wraps the replayable session file into a PDF file, with selected metadata.
6. Writes the PDF file with the embedded session to a pre-defined directory, where it can be archived or managed by your existing systems.

DOM capture and long term storage (LTS) archiving

You can use Tealeaf cxVerify to save DOM Capture sessions as Long Term Storage (LTS) in a PDF file for meta data and electronic signature.

The long term storage (LTS) feature can archive and retrieve Tealeaf sessions (DOM + Network) for replay analysis.

Replay does not connect to your website to fetch the static content (Images and CSS) to replay the archived DOM Capture sessions.

The LTS.zip file contains the session data and all of the static content needed for Replay:

LTS limitations

The LTS feature has the following limitations:

• The LTS feature might not be a complete solution for Network Capture (for dynamically generated JavaScript), similar to Tealeaf CX RealiTea Viewer.
• Because each session is independent and stores all static content within an archive file, there is redundancy of static content. (There is no option for a self contained file.)
• Your website should not retrieve different static content from your server based on client parameters like "location" or "cookie". (For instance, an image ight be different if retrieved from a different country or cookie).

  Note: This limitation is related to Replay and LTS, rather than LTS alone.

• If you update the static data on your website between the time the session was captured and the time the LTS was generated, the new static data is used in the generated LTS. This could result in a Replay showing a different image or layout from what your customer experienced.