Configuring the OmniPage HOCR plugin

This section provides an overview of configuring the OmniPage HOCR plugin in the Page Process module of Tungsten Transact. For an overview of the plugin's features, see OmniPage HOCR plugin.

Administrator privileges are required for this procedure.

Prerequisites

To configure and use the OMNIPAGE_HOCR plugin, you need a batch class with a document type configured. For detailed steps, see OmniPage HOCR plugin.

OmniPage HOCR Plugin Setup

Launch Transact and navigate to Administrator > Batch Class Management.
Open the desired batch class for configuration.
In the navigation pane, expand the Modules section and select Page Process.
Select the OMNIPAGE_HOCR plugin.
The Plugin Configuration screen appears.

Configure the OmniPage HOCR plugin settings using the following table:

OmniPage HOCR Plugin Configuration Options

Property	Options	Description
OmniPage Auto Rotate/Deskew Switch	ON/OFF	Enables automatic rotation and alignment of input images based on detected orientation.
OmniPage Switch	ON/OFF	Enables or disables the OmniPage HOCR plugin.
OmniPage Valid Extensions	tif	Specifies the allowable image formats for OCR processing.
OCR Language	Multiple options	Specify the country or language(s) for OCR operations. Separate multiple values with a semicolon (;).
OmniPage Font Switch	ON/OFF	When ON, enables font style and size detection in the HOCR file, useful for potential fraud detection.
Process PDFs as EText Files	Never, Always, Automatically	Determines how PDF files containing electronic text are processed.
OmniPage Line Removal Switch	ON/OFF	Controls whether line elements are removed during OCR processing.
OmniPage Single Language Detection	TRUE/FALSE	Determines if the OCR engine should detect and process text in a single language.
Asian Full Character Set	ON/OFF	Enables processing of extended Asian character sets during OCR.

Troubleshooting

If issues occur with the OmniPage HOCR plugin, you may encounter the following error messages:

The following table lists common error messages and their possible causes:

Error Message	Possible Cause
Invalid License, so could not be verified.	Network connection failure Invalid OmniPage command License not installed or invalid Tomcat server not started
Problem in verifying License.	Unable to connect to the license server or an error occurred on the license server side.
Exception while reading from XML.	Unable to process the batch.xml file or the file is invalid.
No valid extensions are specified in resources.	No valid file extension has been selected for processing.
Image Processing or XML updating failed.	Unable to update batch XML.
File has invalid extension.	The file processed by OmniPage has an invalid extension.