The Server tab allows the configuration of the following groups of settings:
The Database Properties option group allows you to select a database, create a repository and apply database permissions to individual users and groups of users working on a project. Configure the following settings:
|Connection String||In the Connection String field, specify the path to the database containing a repository containing all batches to be processed by OpenForms 360 Professional. To do so, click the ellipses button and select the desired database in the Connection Properties dialog box.|
Informs you about the status of the database. The following status values may be displayed:
|Create Repository||Allows you to create a repository. Click this button if the Repository Version value states Repository was not found to create a repository in the database to which the connection string is pointing.|
|Apply Database Permissions||Allows you to add Validators, Route Component User, and Capture Component User, all configured on the Users tab to the list of database repository users.|
Folders and Permissions
The Folders and Permissions group includes the following settings to be configured:
|Windows Group||Select a previously created group to serve as the Windows group. To do so, click the ellipses next to the field and select an Active Directory group in the Select User or Groups dialog box.|
|Storage Folder||Browse to the folder where you would like the documents routed by the OpenForms 360 route component to be stored before they are forwarded to the OpenForms 360 Professional engine for form recognition and data extraction.|
Browse to the folder where you want the OpenForms 360 Server plug-ins to be stored.
For detailed information about OpenForms 360 plug-in, refer to the OpenForms 360 Validation help or to the OpenForms 360 Validation Administrator’s Guide.
|Apply folder permissions||Click this button to grant users included in the Windows Group access rights to the Plug-in Folder and the Storage Folder.|
Populate the following fields:
|URL with Kerberos authentication||This field is populated by default with a URL where the host name is set to the DNS name of the current computer. If you do not have any special requirements for the port number and other parts of this URL, do not change this setting.|
|URL with username and password authentication||This field is populated by default with a URL where the host name is set to the DNS name of the current computer. If you do not have any special requirements for port number and other parts of this URL, do not change this setting.|
|SSL Certificate||Specify which certificate to use with HTTPS (with OpenForms 360 version 2.0 the certificate name does not need to have a certain name and it can be any name.)|
|Max Request Length (in KB)||In this field,type in a number of kilobytes to specify the maximum request length. By default this property is set to 122880 KB which would allow uploads of 120 MB.|
|Execution Timeout (in seconds)||In this field, specify a maximum amount of time for a request sent to the server to be answered. The timeout is initiated if the set time limit is exceeded. By default the execution timeout is set to 600 sec.|
Polling Interval specifies how often the OpenForms 360 Server will poll the current state of the internal database looking for new tasks posted by the OpenForms 360 route component. If there is a new task in the database, the server marks it as ready to be validated or as captured, depending on the settings of the OpenForms 360 route component.
To set the polling interval, type in the amount of time in milliseconds in the Polling Interval (in seconds) box.
Enable separation of multipage batches
Selecting this check box allows the OpenForms 360 Server to split a processed batch of documents if some of the processed documents require user validation. If for example, a processed batch contains 10 documents where 3 documents require user validation the OpenForms 360 Server splits the batch into two batches: one with 7 documents and the other with 3 documents.
The value for queue size specifies the maximum number of batches OpenForms 360 Server is allowed to submit to the DOKuStar engine for parallel processing. It allows loading as many DOKuStar cluster nodes with batches as would be necessary.
For example, suppose the DOKuStar engine has five cluster nodes. This means that the DOKuStar engine can simultaneously process only five batches. Now suppose that OpenForms 360 Server submitted seven batches — with each batch being submitted within a short period of time — so short of a time that the submitted batches have not been processed yet. Five of the batches will be handled by DOKustar cluster nodes while the remaining two batches will exist in a Pending state until one of the cluster nodes finishes its work.
This parameter is designed to limit the number of pending batches. It is advisable to set Queue size slightly greater than the number of DOKuStar cluster nodes to ensure that all cluster nodes are working when necessary.
Cache size specifies the number of batches that the DOKuStar engine will keep in its cache. DOKuStar engine cache is a temporary folder usually located at C:\Users\DOKuStar Load manager user\AppData\Local\Temp\DOKuStar Professional\3.0\Cache\project name and contains all data extracted from the batch during processing including SingleClick data (all text recognized by OCR) which is used by Validation Station.
While DOKuStar engine keeps processing new batches, old batches are deleted from the cache and consequently their SingleClick data is no longer available for Validation. If Validator did not have time to validate the batch before its Single Click data was deleted, all text recognized by OCR will be lost for the Validator.This will not prevent Validating the batch because extracted data stays intact.
The general guideline is to keep the cache size greater than the amount of batches in the To Validate state.