IBM Support

Explain the "Free text" search.

Question & Answer


Question

Explain the "Free text" search.

Answer

Contents

Problem

Explain the "Free text" search.

Solution
A Free text search searches the request and the response for every term that is indexed.? In the response it includes every word that is considered meaningful.?? Noise words single letters HTML tags Javascript code are excluded from indexing.Imagine how much space it would add to the indexes if the words HTML BODY HEAD INPUT were indexed every time they occurred. To see (approximately) what is indexed in a response and what is searchable:
  1. Use RealiTea Viewer (RTV).? Notice the response view of a typical page.?
  2. Right-click in the Response view.
  3. Select the Indexed view.?
  4. Alternatively use the dropdown menu on the right side of the RSP button on the toolbar.? This gives you a good idea of the words you can search by to find that particular page.

In a request specific things are included by default in Standard Indexing mode:

[AppData] Section
Everything is indexed in this section.? If you need to index something else in the request you would add it here:

[Env] Section
Only the following fields are indexed:
? http_referer
? http_remote_addr
? local_addr
? referer
? remote_addr
? remote_host
? StatusCode
? URL

[Timestamp]
Only the following fields are indexed:

? NT_Grade
? RT_Grade
? WS_Grade

[URLFields] Section
Everything is indexed in this section.

There are also a number of session attributes indexed:

? TltStsBrowser
? TltStsCanisterID
? TltStsEventText
? TltStsEventUniqueId
? TltStsEventUniqueIdHour
? TltStsFirstPage
? TltStsFirstUse
? TltStsIPaddr
? TltStsLastUse
? TltStsLastPage
? TltStsLoginID
? TltStsNumHits
? TltStsSesnID
? TltStsSesnIdx
? TltStsUserDef*
? TltStsUserID

Free Text searches search for and find any of this data from a request in addition to searching the response data described above.

As you can see from this list cookies are not automatically added to the indexes.? Most sites have many cookies that contain personalization information that is long meaningless strings of encoded data often unique to every hit. Indexing these by default leads to extremely large indexes.? TeaLeaf takes the approach that if there is a specific cookie that should be indexed or searchable simply add a Privacy ReqSet action that copies the cookie and its value into the [appdata] section of a request.? It is indexed and searchable.? In older versions the IndexFields RTA rule is used for this purpose but this technique is deprecated for performance reasons.

An "and on same page" search does not return any results if any of the search criteria are session-level (e.g. TLTSts* variables or session-level events) because such items do not appear on any particular page but rather at the session level of the hierarchy.
Article Reference
00000192
Applies to version(s): 4.5;4.6;5.0;5.1;6.0;6.1;6.2;7.0;7.1;7.2
"
[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSERNK","label":"Tealeaf Customer Experience"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

More support for:
Tealeaf Customer Experience

Software version:
All Versions

Document number:
776649

Modified date:
08 December 2018

UID

ibm10776649

Manage My Notification Subscriptions