Using a Network Share to Store the API Database

ABBYY FineReader Server allows you to keep its API database, OCRServerClient.db, on a network share, for which you can configure shared access, logging, and synchronization.

This is useful in the following cases:

  • In the case of a distributed installation.
  • When ABBYY FineReader Server is deployed on a cluster.
  • When the disk subsystem of the Server Manager machine is not powerful enough.

Network share requirements

  • The network share must support file locking (e.g. SMB).
  • The COM API Identity must have read/write permissions for the network share.
  • The Web API Identity must have read/write permissions for the network share.

For more information, see Access permissions required by the Open API.

Recommended settings

For local API database (default settings) JournalMode = Wal SynchronousMode = Normal
For remote API database JournalMode = Delete SynchronousMode = Full

To apply new settings, do the following:

  1. Select the appropriate COM/Web API Identity (for more information, see Access permissions required by the Open API).
  2. Make sure that no other processes are using the COM API. In particular, be sure to stop the FineReader Server Application Pool in IIS, as well as all the dllhost.exe processes that are being used to host the COM API.

    Stopping dllhost.exe processes

  1. Delete the old database files found in C:\ProgramData\ABBYY FineReader Server 14.0\SC14WF (including OCRServerClient.db).
  2. Place the OCRServerClientSettings.xml file containing the required settings into the C:\ProgramData\ABBYY FineReader Server 14.0\SC14WF folder on the machine where the Web API is installed.

Sample database settings

Local API database

Remote API database

26.03.2024 13:49:49

Please leave your feedback about this article

Usage of Cookies. In order to optimize the website functionality and improve your online experience ABBYY uses cookies. You agree to the usage of cookies when you continue using this site. Further details can be found in our Privacy Notice.