Installation on web pages

Installation on web pages

When you plan the installation of the UI Capture library, consider that it does use system resources to process on the website and the IBM Tealeaf capture systems. Install the library only on the pages that you want to capture and replay.

Installing the UI Capture library can cause the following effects.

  • Page load times can increase slightly during first download. IBM Tealeaf provides strategies for minimizing the effect on load times, including caching the JavaScript after initial download.
  • More data is posted by the web page to the server, but it is not processed.
  • IBM Tealeaf must process and store the additional data.

IBM Tealeaf UI Capture is designed to minimize these burdens.

Unique HTML IDs

To capture the client events for a Document Object Model object, each object or control available with which the visitor can interact must have a unique HTML ID. Without unique IDs, IBM Tealeaf cannot properly replay the UI events in the page.

If you did not instrument your application to support unique IDs or unique names in the document object model, IBM Tealeaf UI Capture automatically generates paths to the node that support the requirement of uniqueness.

IBM Tealeaf also supports the creation of ID black lists, which forces the use of Xpath or name attribute values as identifiers. See UI Capture reference for more information.

Cookies

The web session must use cookies for sessionization. Cookies allow the client events to send messages without having to understand the sessionization mechanism.

For best results in capturing client UI events, deploy the IBM Tealeaf Cookie Injector in your web server environment. The IBM Tealeaf Cookie Injector provides unique session IDs regarding captured IBM Tealeaf session data.

1 comment on"Installation on web pages"

  1. Saved as a favorite, I really like your website!

Join The Discussion

Your email address will not be published. Required fields are marked *