General flow of session data through Tealeaf CX

1. Active session begins. Session is available for replay in Portal and RTV.
2. Session is completed.
3. Session is moved from Short Term Canister to Long Term Canister.
4. Session is indexed for search in LTC. Session becomes available for search by using completed search templates in the Portal and RTV.
5. Session data is aggregated for reporting purposes. Session data populates Portal reports.
6. Session data is trimmed from the Long Term Canister and, optionally, archived.
   Note: For testing purposes, you might want to shorten the intervals for some of the steps to hasten the testing process. These intervals can be configured by modifying the configuration options. Do not make these changes on a production server. These changes should only be applied in a testing environment and should be reverted when testing is complete.
7. Session is indexed for search in LTC:
   1. The control program for indexing (indexprogram) checks for sessions that need indexing, which is based on the Sleep Time When No Work setting.
   2. When sessions are detected that need indexing, the indexing process begins. Indexes are not committed to disk, which enables searching until the Direct Pull Timeout setting expires or the index size exceeds the Maximum Index Size threshold.
8. Session data is aggregated for reporting purposes: By default, the Data Collector polls the Long Term Canister for data to aggregate every five minutes.

   If necessary, you can restart the Tealeaf Data Collector Service through the Windows™ Services Control Panel to immediately perform a data collection. However, you must be certain that the data to be collected is already generated for this step to work.