Tealeaf target page
How the target page is used
The target page exists only to acknowledge the post. No data is saved.
The web server returns a minimal valid response, such as the following message.
<html><head></head><body>Received 895 bytes in 0.1 ms</body></html>
Sample target pages
Sample targets for ASPX, JSP, and PHP environments are provided with the UI Capture distribution.
You can modify the target page for your specific target environment. You can use these sample targets as the basis for creating target pages suitable for other environments.
Target page requirements
The Tealeaf target page ensures the proper capture of UI events, and must have the following properties:
- The page must be POSTable.
- The page must be dynamically executable, for example, ASPX, PHP, or JSP.
- The page must not be cached by Akamai or any cache service, device, or mechanism.
Target page modifications for DOM Capture
The target page is configured by default to read in up to 20,000 bytes. DOM Capture deployments have varying POST sizes, depending on the size and frequency of the DOM snapshots. You update the target page to account for the increased POST data.
Use the TLT_MAX_REQ_LENGTH field in the target page to a value that reflects the typical POST data size from the UI Capture SDK in your deployment. This setting ensures the correct capture of the UI Hits by the CX PCA.
Target page installation
Your website administrator can provide you with the policies and procedures for your installation.
In your web application's pages, references to the target page must be relative to the site root path. For www.example.com, to reference an Tealeaf target page at www.example.com/scripts/TealeafTarget.aspx, you configure the Tealeaf UI Capture to /scripts/TealeafTarget.aspx. The initial / makes it a site-root relative path.
Refer to these guidelines when you deploy the Tealeaf target page.
Typically, the Tealeaf target page is deployed independently of the core application itself in logical and physical terms. Review these guidelines with your infrastructure staff.
- Avoid deploying the Tealeaf target page behind enterprise security features, such as SiteMinder.
- If possible, deploy the Tealeaf target page on a separate application server instance from the web application. While it is a lightweight deployment, it can compete for resources with the web application. If possible, deploy it on a dedicated application server instance.
- Test the Tealeaf target page thoroughly in a test environment before deployment to production.
References to the target page
In your web application's pages, references to the Tealeaf target page must be relative to the site root path.
For www.example.com, to reference an Tealeaf target page at www.example.com/scripts/TealeafTarget.aspx, you configure the UI Capture library to POST to /scripts/TealeafTarget.aspx. The initial "/" makes it a site-root relative path.
Unit tests of the target page
To test that the target page is operating properly, you can run the following tests.
- GET: Enter the URL of the target page in your browser. If you receive a blank page or non-404 error, the page is properly handling your request.
- POST: You can use Fiddler or another traffic monitoring tool to generate a post to the page. Verify that the POST action resulted in a Status Code 200 message.