About Remote Database Validation
Use the remote database validation feature to look up information in a database to provide values for index fields used in your Tungsten Capture document class, even if the database resides at the central site and you are working at a remote site.
In other words, this feature allows the Tungsten Capture database validation mechanism to be used from a remote Tungsten Capture Network site that does not have direct access to the target database. When this option is selected, database validations on remote sites send all database validation requests to the Tungsten Capture Network. The Tungsten Capture Network Service that handles the request then connects to the database.
A remote workstation invoking a database validation requires no additional network connection capabilities beyond what would be required to run the Tungsten Capture Network Remote Synchronization Agent (RSA) in a full-time connected configuration. The Tungsten Capture Network Web Server (TCN Web Server) is used to connect to the database via a Tungsten Capture Network Service.
If remote database validation is not enabled, then a remote site that performs database validation in the Validation or Verification module must have access to all referenced validation databases. Databases can be located at the central site or another network location (accessed via UNC path), or they may be copied locally to each remote site. Using a UNC path is the preferred method.
Data Caching
If your validation data does not change much, data caching may improve performance.
You can cache validation lookup data in local memory at a workstation and within one or more Tungsten Capture Network Services at the central site.
You can set the number of different database validation results to cache on a workstation (whether on a remote site or at the Tungsten Capture Network Server) between 1 and 5,000 results for each validation database.
When the cache is full and a new database lookup result is retrieved, the oldest cached result is removed and the new result is added.
By default, the workstation cache is cleared if the Validation or Verification module is closed or if 24 hours have passed without the cached data being accessed. You can optionally specify that cached database results are to be discarded at any interval between one minute and 24 hours, in one minute increments. The cache within the Validation or Verification module is not shared; each of these modules stores its own cache, and the cache is cleared when the module is closed.
The Tungsten Capture Network Server cache works in the same way as the remote site (workstation) caches, except the Tungsten Capture Network caching is performed through the Web server to a database connection, and the cached data is stored within the Tungsten Capture Network Service. The Tungsten Capture Network Service must have access to all referenced databases.
The Tungsten Capture Network Service cache is cleared when the service is stopped or restarted. Tungsten Capture Network Service cache limits and cache expiration functionality use the same rules as workstation caching.
Configuring the Tungsten Capture Network Service
Various permissions are necessary for the Tungsten Capture Network Service to function properly. If you are using remote database validation, the remote site transmits a request to the Tungsten Capture Network Service (through the Web server), and the Tungsten Capture Network Service accesses the database wherever it is located. This means that all configured Tungsten Capture Network Services must have access to all validation databases that may be needed at the remote sites.
In other words, any file paths and/or ODBC connections needed to perform the remote database validation must be accessible to all the Tungsten Capture Network Services at the central site. This may require adding permissions to the Windows user configured for the Tungsten Capture Network Service.