- Installation
- Installing GhostScript
- Updated
- Problem “error in put document in database: Illegal key size or default parameters”
Installation
1/ Disable the Windows firewall
2/ Install Java 8 – 64-bit . We recommend RedHat’s OpenJDK implementation: https://ftp.myopenbee.com/software/openjdk/java-1.8.0-openjdk-1.8.0.212-3.b04.redhat.windows.x86_64.msi
If you choose the Oracle implementation of JAVA, installing JCE version 1.8 is required.
3/ Run the installer as an administrator
4/ Recommended but optional, since version 6.9, install GhostScript (see below)
5/ You can check that it is working properly from the Web Interface.
Installing GhostScript
The processing of large files by the Tesseract version of Open Bee™ Scan OCS may cause malfunctions due to excessive RAM usage.
As of version 6.9.0, it is possible to resolve these issues by using GhostScript as a PDF pre-processing tool. We therefore highly recommend its installation.
To do this:
- Download the current version of GhostScript for Windows https://www.ghostscript.com/download/gsdnld.html (AGPLv3 license)
- Open the configuration file “conf/ocs.conf” in the Open Bee™ Scan OCS installation folder
- Specify the GhostScript installation path in the parameter “tools.ghostscript.win32” tools.ghostscript.win32 = “C:Program Files (x86)gsgs9.23bingswin32c.exe”
- Uncomment tools.ghostscript.win32, tools.ghostscript.pngDpi , and tools.ghostscript.scaleFactor parameters by removing the “#” sign tools.ghostscript.win32 = “”${OB_CONVERSION_HOME}”ghostscriptbingswin32c.exe” tools.ghostscript.pngDpi = 600 tools.ghostscript.scaleFactor = 3
- Relaunch the Open Bee™ Scan OCS service
Updated
1/ Uninstall the previous version of Open Bee™ Scan OCS from the start menu.
2/ Install the new version
Problem “error in put document in database: Illegal key size or default parameters”
This issue occurs when the Java Cryptography Extension (JCE) is not properly installed.
Source of the problem:
In an automatic java update, the “libsecurityUS_export_policy.jar” and “libsecuritylocal_policy.jar” files are not updated
Solution:
- Download the latest version of the JCE
- Replace the “local_policy.jar” and “US_export_policy.jar” jars with the newly downloaded jars
- Restart OCS