Instructions

U.are.U SDK - Developer Guide 64
JavaPOS
THIS CHAPTER DESCRIBES HOW TO USE THE JAVAPOS API.
The U.are.U JavaPOS API is built on the U.are.U Java API. This JavaPOS API is geared for Point of Sale applications
and has the following features:
• Fully compliant with JavaPOS 1.13. The U.are.U JavaPOS API conforms to the specifications for the
Biometrics device category in Chapter 5, “Biometrics,” of the UnifiedPOS Retail Peripheral Architecture, Version
1.13 (July 15, 2009).
The complete UPOS documentation is available at http://www.nrf-arts.org/UnifiedPOS/default.htm.
• Backward compatible with previous DigitalPersona JavaPOS product (U.are.U UPOS for JavaPOS SDK),
with only a few caveats. This new API is the result of merging the previous JavaPOS SDK with the U.are.U SDK:
the internal architecture has been completely rewritten. For users of the previous SDK, the updated SDK means an
upgraded internal architecture for more robust performance -- up to ten times faster for identification. If you are
upgrading an existing application, see Upgrading from U.are.U UPOS for OPOS/JavaPOS on page 20 for more
details.
• In addition to the JavaPOS API, the U.are.U SDK includes a JavaPOS Device Service object, which can be
used with any JavaPOS Device Control for the Biometrics device category.
• Because the JavaPOS API is built as an adjunct to the Java API, applications can use both the JavaPOS
standard operations AND use the U.are.U Java API (described in The JAVA API on page 29). Java methods
can be used to access streaming features or to import data.
Terminology Note
The U.are.U JavaPOS API conforms to the standard terminology used by the 2009 JavaPOS specification, whereas the
other APIs in the U.are.U SDK generally use terminology that matches evolving industry standards. If you are going to
use the U.are.U Java API along with JavaPOS, you need to note that in JavaPOS, the extracted fingerprint data
(template) is stored in a biometric information record (BIR). The templates created through enrollment and capture are
equivalent to Fingerprint Minutiae Data (FMD) records in the other APIs of the U.are.U SDK. Note that JavaPOS
templates include a 10- or 45-byte JavaPOS header in addition to the data itself.
Working with Fingerprint Data in JavaPOS
The U.are.U JavaPOS API provides two types of fingerprint data: raw images and fingerprint templates. The data flow
for JavaPOS applications is the same as described in the topic Understanding the Data Flow on page 11 except that
JavaPOS data has additional JavaPOS headers and JavaPOS does not use the FID/FMD terminology used by U.are.U.
Note that there is no easy method provided in the API for converting data from JavaPOS BIRs to FMDs.
Fingerprint Data for Raw Images (Captures)
Per the JavaPOS specification, raw fingerprint scans (images) are available in the RawSensorData property when
StatusUpdateEvent triggers.
Fingerprint Data for Captures and Enrollment Templates (BIRs)
The U.are.U JavaPOS API now supports four different JavaPOS biometric information record (BIR) formats, as set by
the Algorithm property: