Index Program (IndexProgram.exe)
Index Program loops continuously, looking for indexing to be done until a stop is requested. If it finds indexing to be done, it checks for disk space and then starts the process.
Index Program retrieves a list of non-indexed sessions. Work files are then generated, each containing a list of non-indexed sessions to be indexed in a single batch.
- The number of work files generated is based on the Batch work file parameter and the number of available processes.
The following types of files are valid for indexing:
- TLA - Captured Tealeaf® Archive files
- TLC - Canister Tealeaf Archive files
- TLA and TLC files are not normally generated during the capture process, but the system can be configured to do so for troubleshooting purposes.
- Filename.ano.yyy - Annotation files
- If the file is filename.ano.xxx, it is indexed
using dtSearch's native indexing for files of type xxx.
The work filename is TeaLeafWork_nnn_mmm or WORKTeaLeafWork_1045006104_00000001
where:
nnn is the UNIX time at the time of creation.
mmm is a counter to ensure uniqueness.
- If the file is filename.ano.xxx, it is indexed
using dtSearch's native indexing for files of type xxx.
The work filename is TeaLeafWork_nnn_mmm or WORKTeaLeafWork_1045006104_00000001
- DOC - Microsoft Word files
- PDF - Portable Document Format (Adobe Reader) files
- Annotation, PDF, and DOC files can be added as attachments to sessions through IBM® Tealeaf CX RealiTea Viewer. For more information on adding comments and file attachments to indexes, see "RealiTea Viewer (RTV) User Manual" in the IBM Tealeaf RealiTea Viewer User Manual.
- XML - XML files
The number of files generated is based on the following formula:
(Number
of Index Processes) x (Batch work files)
The maximum number of entries in each file is specified by the Workfile Batch setting. See Indexing Options tab.
You may specify additional HTTP response content types for indexing. See Adding HTTP response content types for indexing.