signoPAD-API Java can run with the full range of functions on all Windows versions starting with Windows 7. Other operating systems are supported with limited functionality. See below for details.
JRE dependency
signoPAD-API Java requires version 1.8 or later of the Java Runtime Environment (JRE). Both 32 bit and 64 bit versions are supported.
The table below provides the Internet addresses where Java can be downloaded free of charge.
All components not included as standard in the JRE are included. The dependencies are listed in the following tables:
|
Dependency |
Note |
|---|---|
|
stpad-lib.jar |
signoPAD-API Java library |
|
stlic-lib.jar |
- |
|
bcprov-jdk18on.jar |
- |
|
jna.jar |
- |
|
jna-platform.jar |
- |
|
swt-gtk-linux-x86_64.jar swt-gtk-linux-x86.jar swt-win32-win32-x86_64.jar swt-win32-win32-x86.jar |
Only when using SWT Control |
|
jpen.jar jpen.dll jpen-64.dll libjpen.so libjpen-x86_64.so |
Only when using PenDisplayFacade with the
library. See |
|
jni4net.j.jar jwinpointer-se.jar |
Only when using PenDisplayFacade with the See |
‘Pure’ Java interface
signotec LCD signature pads can (depending on the configuration) be used via TCP/IP. An interface with limited functionality is available for devices connected in this way. It does not require a platform-dependent library and, as a result, can be used on all systems that can run Java applications. Please refer to chapter SigPadPureFacade for details on this interface.
Windows
In Windows, a native library from the file stpad-lib.jar is required when using SigPadFacade. The library it contains is automatically loaded with the library Java Native Access (JNA).
Alternatively, the STPadJava.dll file can be extracted from the stpad-lib.jar and its storage location can be defined with the system property jna.library.path at application start. All other .dll and .manifest files, which have been included in the version 8.0.22 and earlier, are no longer required.
Linux
In Linux, a native library from the file stpad-lib.jar is required when using SigPadFacade. The library it contains is automatically loaded with the library Java Native Access (JNA).
Alternatively, the libSTPadJava.so file can be extracted from the stpad-lib.jar and its storage location can be defined with the system property jna.library.path at application start.
OpenSSL (libssl)
When using the SigPadFacade, the OpenSSL (libssl) library in version 3.0 must be installed in the system.
libusb
When using HID or WinUSB devices, libusb 1.0.16 or higher is also required, which can be downloaded free of charge from https://libusb.info.
The authorisations for libusb must be adjusted if necessary. For this, the MODE for USB must be changed to 0666:
# libusb device nodes
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666"
udev must be restarted afterwards:
udevadm control --reload-rules
In Debian, this setting is located in the file /lib/udev/rules.d/50-udev-default.rules or /lib64/udev/rules.d/50-udev-default.rules. The setting may be in a different location when using other distributions.
Java Advanced Imaging
Supported image formats are JPEG, BMP, WBMP and PNG. ‘Java Advanced Imaging Image I/O Tools’ is required to be able to export signatures in other image formats (JPEG 2000, PNM, RAW or TIFF). These are available as the open source projects jai-imageio-core (e.g. TIFF, PNM, RAW) and jai-imageio-jpeg2000 (JPEG 2000).
Security policies
SigPadPureFacade and the SigPadApi.decryptSignatureData() method use cryptographic processes that are deactivated by default in Oracle Java up to Version 9.
The files local_policy.jar and US_export_policy.jar in the folder %JRE_HOME%/lib/security must be replaced in Versions up to Java 8u150. The files for the different Java versions can be found in the policy directory supplied.
The required policy files of the Java installation are included from Java 8u151 and must be selected with the security property crypto.policy=unlimited before the JCE framework is initialised. The signoPAD-API Java configures this property automatically as early as possible. However, if the enclosing application uses and initialises the JCE framework, it must be ensured that the security property has been set:
java.security.Security.setProperty("crypto.policy", "unlimited");
Please refer to the Java 8u151 Release Notes for further information.
JPen library
When using PenDisplayFacade, the JPen library can be used for communication with the device. JPen project page: https://sourceforge.net/projects/jpen
Depending on the system, JPen loads a native library with JNI (see JRE dependency). The folder from which the JNI loads the native libraries can be defined with the System.property java.library.path at application start.
Here is an example for the relative subfolder ‘lib’:
> java -Djava.library.path=lib
A native interface to the pen display is required for capturing with the pen. This is generally contained in the manufacturer’s drivers. In Windows, for example, JPen uses the Wintab interface. For signotec devices, all required components are contained in the ‘signotec Pen Display Manager’ driver.
JWinPointer library
When using PenDisplayFacade, the JWinPointer library can be used for communication with the device. Unlike JPen, JWinPointer only runs on Windows, requires .NET 4.5 or higher and uses the system’s own API to capture data. Furthermore, JWinPointer only supports Java 1.8.
JWinPointer must have write permissions in the user’s temp folder to store native libraries there. By default, the folder is obtained from the java.io.tmpdir environment variable. A user-defined folder can be set using the jwinpointer.library.path variable.
> java -Djwinpointer.library.path=C:\Temp
A native interface to the pen display is required for capturing with the pen. This is generally contained in the manufacturer’s drivers. For signotec devices, all required components are contained in the ‘signotec Pen Display Manager’ driver.