Overview
JavaPOS for Datalogic Connect, also called SDS JavaPOS, is the Datalogic JavaPOS driver with one additional feature. It can communicate to and from AladdinSDS, the device integration service that is part of Datalogic Connect and runs on the POS. This page explains what the driver is, how it reaches a scanner through AladdinSDS and which files configure it.
What SDS JavaPOS Is
Datalogic JavaPOS opens a serial or USB port and talks to the scanner itself. SDS JavaPOS keeps the same JavaPOS interface toward the application but, for a device whose registry entry selects an SDS device bus, hands the communication to AladdinSDS instead of opening the port. The communication uses HTTP and WebSocket, or HTTPS and secure WebSocket (WSS) when AladdinSDS requires SSL/TLS certificates.
In everything else SDS JavaPOS behaves like Datalogic JavaPOS:
- Java platform requirements: the same as Datalogic JavaPOS, see Developing with JavaPOS.
- Application integration: comparable to Datalogic JavaPOS, see Application Integration, plus a few additional JAR files required to communicate with AladdinSDS.
- Configuration: comparable to Datalogic JavaPOS, see Configuration Files, plus additional attributes specific to the AladdinSDS communication. See Configuration Model below.
This is a preview version of JavaPOS, intended for evaluation only.
How the Integration Works
The application calls the JavaPOS API as usual. The driver sends its requests to the local HTTP API of AladdinSDS and receives barcode reads and status changes from the WebSocket feed; AladdinSDS is the only component that talks to the scanner. The diagram shows the chain.
AladdinSDS publishes both interfaces on port 9000, on localhost by default; the HTTP API is documented in the Aladdin SDS API reference and the feed in the Aladdin SDS WebSocket AsyncAPI documentation. See Local Integration for how AladdinSDS exposes them.
When AladdinSDS requires SSL/TLS, the driver connects over HTTPS and WSS and authenticates with a CA certificate and a client PKCS#12 file. When the certificate settings are missing, the driver falls back to HTTP and plain WebSocket. When they are present but wrong, or present while AladdinSDS does not require SSL/TLS, the JavaPOS Claim action fails. The cases are listed under SSL/TLS Connection Behavior.
The HTTP and WebSocket transport is provided by eight JAR files included in the SupportJars directory of the installation:
gson-2.8.6.jarkotlin-stdlib-1.9.0.jarkotlin-stdlib-common-1.9.0.jarkotlin-stdlib-jdk7-1.9.0.jarkotlin-stdlib-jdk8-1.9.0.jarokhttp-4.12.0.jarokio-3.6.0.jarokio-jvm-3.6.0.jar
These libraries support HTTP, HTTPS, WebSocket (ws://) and secure WebSocket (wss://) connections, requests and responses.
Configuration Model
Two files of the Datalogic JavaPOS framework carry the settings that SDS JavaPOS adds. Both are described in the Configuration reference.
| File | Role in Datalogic JavaPOS | What SDS JavaPOS adds |
|---|---|---|
dls.properties | Device and connection settings, see dls.properties Reference | Three keys for SSL/TLS: TrustedCACrtFile, TrustedClientP12File and TrustedClientP12PWD. Needed only when AladdinSDS requires certificates. |
jpos.xml | The JavaPOS device registry (JPOS): one JposEntry per logical device, see JPOS Device Registry Reference | A deviceBus of SDS-COM (or SDS-OEM, see the note below), which routes the entry to AladdinSDS; ipAddress and ipPort of the AladdinSDS HTTP API; and a new serialNumber element introduced for SDS communication. |
dls.properties decides how the driver connects to AladdinSDS. jpos.xml decides which scanner each logical device stands for: deviceBus selects the SDS transport, ipAddress and ipPort locate AladdinSDS (127.0.0.1 and the port AladdinSDS listens on, 9000 by default), and serialNumber identifies the scanner. Any wrong value in the SDS-specific pairs makes the device fail.
Use full paths for the CA and PKCS#12 files in dls.properties, so that SDS JavaPOS finds them regardless of the working directory of the application.
What to Read Next
- Installation: install AladdinSDS and run the SDS JavaPOS installer on Windows or Linux.
- Quickstart: set up the certificates,
dls.propertiesand the device registry, and add the support JAR files to the application. - Configuration: the reference of every SDS-specific key and property.