11.0

Setting Up the Licensing Server

The Licensing Server service can be added to the cluster identically to the Processing Server service.

The same serial number should be activated (the serial number must support at least two activations). The serial

number must not change depending on the node provided by the Licensing Server.

The stations must be restarted after the service switches between the cluster nodes. The Processing Server stops

and automatically starts in 5 minutes. The remote stations continue working with their tickets if the same serial number

is used for all of the cluster nodes.

A separate log file with page use statistics is created on each cluster node in the folder

%allusersprofile%\ABBYY\FlexiCapture\11\Licenses. To obtain summary statistics, the values from all of the nodes

must be added. If a serial number which allows two activations is activated on the nodes Node1 and Node2, then

pages are counted for the Node1 license when Node1 is running and for Node2 license when Node2 is running. If the

page limit specified for the serial number is 100 pages, then, besides the main 100 pages, 100 more pages are added

to be used when working on the other node.

Setting Up the Application Server (and clustering the Administration and

Monitoring Console and Web Stations)

The ABBYY FlexiCapture 11 Application Server can be deployed on an NLB cluster to balance workloads and speed

up query processing.

Detailed information about Network Load Balancing technology can be found on the Microsoft website.

Setting Up an NLB Cluster for the Application Server

In this section, you will find step-by-step instructions for setting up an NLB cluster for the Application Server.

The Administration and Monitoring Console and Web Stations are clustered together with the Application Server.

A detailed overview of NLB cluster settings can be found on the Microsoft website.

Note. The addresses, computer names, domain names, etc. used below are not mandatory and may be changed by

the administrator.

Setting Up the Cluster

To set up the cluster, complete the following steps:

1. Install the Application Server on each cluster node. The database, File Storage Folder, Processing Server,

Licensing Server, and Application Server clients must be located on a different computer, which must be ac-

cessible to all nodes in the cluster.

2. In Windows Features, add Network Load Balancing to each node in the cluster. This can be done by clicking

the Add Features link in the main window of the Server Manager (Start -> Administrative Tools -> Server

Manager).

3. Assign an IP address to the cluster via which the cluster can access the nodes as a unit. (This is a virtual

cluster address.)

If a single network interface is used for client/cluster traffic and other network traffic on the nodes (as is usual in

Multicast mode), each host in the cluster must have a dedicated IP address (in addition to the virtual address,

which is common to all cluster nodes). A host will use its dedicated IP address instead of the virtual cluster ad-

dress for incoming connections to the cluster nodes over Telnet, SSH and other protocols, and for outbound

connections from the cluster nodes.

All cluster nodes must receive all incoming cluster traffic. The balancing algorithm determines which cluster node

should respond to a given query. The choice between Unicast and Multicast depends on your network configura-

tion.