Instructions

U.are.U SDK - Developer Guide 21
Upgrading from previous SDKs
OPOS. If you do not update your application to specify a specific format, new templates will be created with 45-
byte headers. Enrollment, identification and verification will continue to work with both new templates with 45-
byte headers and previous templates that have the shorter headers. See Working with Fingerprint Data in JavaPOS
on page 64 and Working with Fingerprint Data in OPOS on page 71 for more information.
• New FAR Security Setting. We have tightened the FAR security setting to align with our current corporate
standard. The new standard is 100 times more strict. Please update your code accordingly. We recommend that
you allow the FAR setting to be configurable at run-time within your application. See Determining an Acceptable
Level of Error on page 15 for more information on setting FAR.
• Enrollment no longer stops at four retries. The previous enrollment process would fail after four unsuccessful
scans. If your application is dependent on having exactly four tries, then you may need to adjust your code.
• Errors and exceptions may be handled differently. Because of the extensive architectural changes to this
version of the OPOS and JavaPOS APIs, exceptions and error codes may not be identical. You should double
check carefully that the new API handles errors and exceptions as expected for your application.
For specific details about upgrading your existing application, consult JavaPOS on page 64 or OPOS on page 71.