Understanding How the Full Text Utility Works (Indexer and Services)
The actual optical character recognition (OCR) function of the Full Text utility depends upon the Indexer working in conjunction with a special (Windows) Service.
Tell me about...
The Indexer component of the Full Text utility uses a third party Recognition Engine to perform the actual process of optical character recognition on files in stored in the DocuPhase Repository: extracting any found text. The extracted words or phrases are stored within the FTSData table of Microsoft SQL Server.
You can select a different Recognition Engine in order to change the accuracy and/or speed of the process. Tell me more...
Engine | Description | Available Accuracy vs Speed Settings |
||
---|---|---|---|---|
Fast | Accurate | Balanced | ||
MTX |
|
X | X | X |
MOR |
|
X | X | X |
FRX |
|
n/a | n/a | n/a |
Voting 2-Way |
Provides accurate and fast machine print OCR capabilities. | X | X | X |
Voting 3-Way |
Provides accurate and fast machine print OCR capabilities. | X | X | X |
TIP
You can select a different OCR Engine via the Options menu in Full Text Manager. Tell me more...
In general, Windows Services are used to control long-running executable Applications (e.g., Full Text Indexer) that run in their own Windows sessions. In order to process Documents 24x7 and maintain stability, the Full Text Service is used to start and stop the Full Text ndexer after the processing each page of a image/file. One of the main benefits of the Services is that it runs behind the scenes without interfering with other Users who may be working on the same server: continually monitoring the Full Text Queue for Documents that need to be Indexed.