10.0
Table Of Contents
- Installing ABBYY FlexiCapture 10
- Standalone Installation
- Distributed Installation
- System Requirements
- General information
- Preparing the Application Server for installation on Windows 2012
- Preparing the Application Server for installation on Windows Server 2008 R2
- Preparing the Application Server for installation on Windows 2003
- Installing the servers
- External components required for the correct operation of the system
- System components in IIS and their configuration
- This section describes the IIS configuration which is necessary for the operation of FlexiCapture. This configuration is configured automatically during installation and required no manual configuration. However, in case of errors this section can help you to check the settings specified in IIS.
- Application pools
- Authentication settings for FlexiCapture 10 Web Applications
- Handler Mappings
- ISAPI and CGI Restrictions
- Checking the operation of IIS
- Switching system components to 64-bit mode
- Database server
- Interaction of the system components
- Installing the stations
- Using Active Directory
- Using SMS
- Installing Remote Stations
- Updating your earlier ABBYY FlexiCapture 10 releases to Release 6
- Upgrading from ABBYY FlexiCapture 9.0
- Upgrading from ABBYY FlexiCapture 8.0 Professional
- Upgrading from ABBYY FormReader 6.5
- Managing Your Licenses
- Setting Up FlexiCapture 10 Distributed Installation
- Logging
- Working with Clusters
- Technical Support
© 2011 ABBYY. All rights reserved.
75
This requires in the following cases:
1) When specifying address of the Application Server on the Processing Server. To specify the address, do the following:
- start the Processing Server Monitor;
- in the Processing Server local menu, select the «Change Application Server» item;
- in the dialog that opens, specify the address: https://<server name>.
2) When working on user stations, the server address https://<server name> must be specified when you start the station or open a
project
3) Similarly, when working on Web Stations, the station URL must be entered starting from the server address: https://<server
name>/<web station name>
Recommendation for setting up FlexiCapture 10
General recommendation
To improve performance of ABBYY FlexiCapture, use the following recommendations:
- Install SQL Server and FlexiCapture Application Server on different computers. The Processing and Licensing servers can be
installed on the computer where the Application Server is installed.
- Do not install processing stations on the computes where FlexiCapture servers or SQL Server are installed.
- Do not store all data in SQL database. For these purposes, a File Storage should be used. This option must be selected when
creating a database in the Administration and Monitoring Console. If a file storage was not created when creating a database, it
cannot be connected later while working. During work, it is also impossible to disconnect the file storage which was connected
when creating the database.
These recommendations are described in more detail below.
Configuring SQL Server
RAM
The
amount of RAM available to SQL Server should be not less than the amount recommended by Microsoft for the given edition
of MS SQL Server (see the table of recommendations for different editions
).
The more RAM is available, the larger part of database can fit in RAM which allows faster access to database.
However, if FlexiCapture servers are installed on the same computer, the amount of RAM available to SQL Server must be re-
stricted in SQL Server settings so that the amount of RAM was also sufficient for FlexiCapture servers including IIS (recom-
mended amount of RAM is at least 4 GB). Thus, in order to improve performance, it is recommended that SQL Server and Flexi-
Capture Servers should be installed on different computers.
Hard disk
It is desirable to place the database file on a fast hard drive (e.g., 15000 rpm/second). If MS SQL Server is installed on the same
computer with FlexiCapture Servers, it is desirable to use one hard disk for the %temp% folder of IIS and the File Storage and
another disk – for SQL database.
Database File
The process of increasing the database file may lead to a temporary decrease in SQL Server performance, so it is recommended to
specify in database properties in Autogrowth settings that a one-time increment of the database file must be at least 100 MB.
Recovery model
To improve performance of SQL Server, it is desirable to use a Simple Recovery Mode for the database.
Rebuilding indexes
After long work of FlexiCapture, a significant increase in the size of database can be noticed. At the same time, more than 50% of
the space can be occupied not with data, but with the indexes in tables.
In order to decrease the size of database and improve performance, it is recommended that indexes should be rebuilt periodically
(e.g., once for every million pages processed). This operation should be performed on tables, which contain data to be changed
frequently. It is recommended to perform this operation от a regular bases for the Batch, Document, Page, EventLog, Task,
DocumentParameter and BatchParameter tables.
Estimating the size of File Storage
Most of the space in file storage is occupied by images being processed in the system. For each loaded file, its source image is
stored as the original; besides black-and-white image copies and image thumbnails are created. For color images, color copies
with quality loss are also created.
The level of quality loss is specified in batch type properties, in the Displayed image quality field.










