Kofax RPA Installation Guide
Be aware that loss of data may occur when storing data in Oracle, Sybase or MySQL. On Oracle, an
empty string is converted to null. On Sybase, an empty string is converted to " " (a single space). On
MySQL, millisecond precision is lost when storing dates. For details, see the ObjectKey Caveats section
in the Storing Data in Databases topic in the Kofax RPA help.
Note For correct display of data in the Kofax Insight Dashboard, make sure Java correctly sets the
time according to your time zone on RoboServers and computers running Management Consoles. See
the Timezone Data Versions in the JRE Software on the Oracle web site for the latest updates in time
zones. If necessary, use the Timezone Updater Tool to update the time zone information.
Document Transformation prerequisites and limitations
Install all the latest Windows updates before installing and using Kofax RPA Document Transformation.
Prerequisites
The maximum document size for transformation is 100 MB. Kofax RPA imposes a file size limit for a
transformed document to enable protection against the denial-of-service attacks. You can lower the
file size value to protect against such an attack. To change the document size limit, edit the following
parameter in the Web.config file in the Kofax DTS\Transformation Services directory in the
Kofax RPA installation folder.
<httpRuntime targetFramework="4.5.1" maxRequestLength="104857600"/>
The following are other requirements you need to observe.
• Do not install Kofax RPA Document Transformation on the computer running Kofax Transformation
or Kofax TotalAgility.
• You can re-use existing KTM, KTT, and RTTI projects version 6.2 or earlier.
• You cannot re-use KTA projects, because KTA does not provide a way to export a KTA Extraction/
Classification group to a complete .fpr file.
Limitations
The following Kofax Transformation features are not supported.
• Rich client user modules (Doc Review, Validation, Verification, Correction)
• ThinClient user modules other than validation (Verification and Correction)
• Multiple steps of Validation
• Configuration Sets for migration between systems
• A2iA engines
• Reporting settings
Desktop Automation requirements and prerequisites
The following sections list components that must be installed and configured on the automation devices
(remote computers you want to automate) before you can use the Desktop Automation feature in Kofax
RPA.
Java Access Bridge
To automate Java programs or Java applets on remote devices with Kofax RPA, install Java 32-bit on
your device (JRE or JDK) and enable the Java Access Bridge in the Java Runtime Environment used
by the application. We recommend using the latest available Java version.
For JRE 7 or Later
To enable Java Access Bridge for Java version 7 or later, navigate to the bin directory in the Java
installation directory and run the following command.
13