Kofax Communication Server 10.0.0 User Manual

Page 49

Environment Guide

Version 10.00.00

120

Notes:

At least 2 cores should be reserved for optimum quality

The values are valid for a hardware that is similar or better than the following reference system:

HP Proliant DL380G8 (CPU Xeon E5-2640, dual 6-core, 2500MHz)

The total CPU usage caused by other high priority processes/threads inside the VM that is used for

KCS FoIP must be less thatn 20% from total available CPU usage.

5.5.3

Supported Link Components

The support of link components in virtual environment is limited to all KCS modules. Modules of third-party

vendors may work as well, but Kofax does not guarantee their functioning.

The major performance indication of a link server is the message throughput including document

conversion.

Therefore, tests were performed that focused on throughput to show the dependencies based on various

environment scenarios (physical machine Mod. 300, VMw

are ESX server, …).

Common parameters for performance measurements of TC/LINK-FI document conversion

Used operating system of link server(s) was Windows 2003 SP1 + all patches (available by March
2007) installed

Office 2003 Professional SP2 all patches (available by March 2007) installed

Used link package TC/LP 2.20.00., newer version of TCDCKey.DLL (2.09.01 )

All trace levels (general, TCDC, …) have been set to 0

TraceLevel on TCOSS server set to 0x1083, TraceFlags set to 0x40

Minimum duration of all TCDC conversion throughput measurements was 1 hour

Minimum duration of all Lincoln, TCIMG32 and Datalogic Library conversion measurements was 20
minutes

PDF conversion done with Acrobat Standard 7.0.8 (using script)

Alternatively PDF conversion done with Acrobat Reader 7.0.7 (no script)

Used servers

1. Physical machine Mod. 300

KCS Mod. 300

– TA11 main board, 512 MB RAM, 1 x 2,8 GHz Xeon processor, SCA hard disk

2. VMware session under ESX server - version 3.0.1

– Build 32039

VMware session 512 MB RAM, 1 x 2,8 GHz Xeon processor