UltraLite application build and deployment specifications

This section contains tables that show the build and deployment requirements for UltraLite applications.

Note

There may be versions of the UltraLite engine located in directories that contains the _dev suffix, such as the x86_dev directory. These versions contain development-time logging functionality that can be used to diagnose problems on platforms for debugging purposes. The logging output is intended for use by Sybase engineers rather than customers. For production systems, use a version of the engine that is not in a _dev directory.

Build and deployment requirements for UltraLite applications and encryption

The following table describes the minimum requirements to build and deploy an UltraLite application for all supported platforms and devices, including the requirements for UltraLite database encryption.

Platform or device	Minimum requirements	AES encryption requirements	FIPS 140-2 AES encryption requirements
Windows Mobile and desktop (UltraLite C/C++ using static linkage)	Link against: ulrt.lib¹ ulbase.lib¹	Use the DBKEY creation parameter to set the encryption key when creating or connecting to the database. Call the EnableAesDBEncryption method.	Set the DBKEY creation parameter to the encryption key when creating and connecting to the database. Set the creation parameter fips=yes when creating the database. Call the EnableAesFipsDBEncryption method. Deploy: ulfips16.dll² sbgse2.dll²
Windows Mobile and desktop (UltraLite C/C++ using dynamic linkage)	Link against: ulimp.lib^{1, 10} ulbase.lib¹ Deploy: ulrt16.dll¹	Use the DBKEY creation parameter to set the encryption key when creating or connecting to the database. Call the EnableAesDBEncryption method.	Set the DBKEY creation parameter to the encryption key when creating and connecting to the database. Set the creation parameter fips=yes when creating the database. Call the EnableAesFipsDBEncryption method. Deploy: ulfips16.dll² sbgse2.dll²
Windows Mobile and desktop (UltraLite C/C++ with the UltraLite engine)	Link against: ulrtc.lib¹ ulbase.lib¹ Deploy: uleng16.exe²	Use the DBKEY creation parameter to set the encryption key when creating or connecting to the database.	Set the DBKEY creation parameter to the encryption key when creating and connecting to the database. Set the creation parameter fips=yes when creating the database. Deploy: ulfips16.dll² sbgse2.dll²
Windows Mobile and desktop (UltraLite.NET)	Add references to: iAnywhere.Data.UltraLite iAnywhere.Data.UltraLite.resources Deploy: iAnywhere.Data.UltraLite.dll⁷ iAnywhere.Data.UltraLite.resources.dll⁸ ulnet16.dll⁶	Use the DBKEY creation parameter to set the encryption key when creating or connecting to the database.	Set the DBKEY creation parameter to the encryption key when creating and connecting to the database. Set the creation parameter fips=yes when creating the database. Deploy: ulfips16.dll² sbgse2.dll²
Windows Mobile and desktop (UltraLite.NET with the UltraLite engine)	Add references to: iAnywhere.Data.UltraLite iAnywhere.Data.UltraLite.resources Deploy: iAnywhere.Data.UltraLite.dll⁷ iAnywhere.Data.UltraLite.resources.dll⁸ ulnetclient16.dll⁶ uleng16.exe²	Use the DBKEY creation parameter to set the encryption key when creating or connecting to the database.	Set the DBKEY creation parameter to the encryption key when creating and connecting to the database. Set the creation parameter fips=yes when creating the database. Deploy: ulfips16.dll² sbgse2.dll²
Mac OS X and iOS (UltraLite C/C++)	Add to your Xcode project: libulrt.a⁹ libulbase.a⁹ (Mac OS X only)	Use the DBKEY creation parameter to set the encryption key when creating or connecting to the database. Call the EnableAesDBEncryption method.	Not applicable
Linux (UltraLite C/C++)	Link against: libulrt.a³ libulbase.a³	Use the DBKEY creation parameter to set the encryption key when creating or connecting to the database. Call the EnableAesDBEncryption method.	Not applicable
Android (UltraLiteJ)	Add to your Android project: UltraLiteJNI16.jar⁵ libultralitej16.so⁴	Use the DBKEY creation parameter or the setEncryptionKey method to set the encryption key when creating or connecting to the database. Call the EnableAesDBEncryption method.	Not applicable
BlackBerry (UltraLiteJ)	Deploy: UltraLiteJ16.cod¹¹ UltraLiteJ16.jad¹¹¹²	Use the setEncryptionKey method to set the encryption key when creating or connecting to the database. Call the EnableAesDBEncryption method.	Not applicable

¹ For Windows Mobile, this file is located in %SQLANY16%\UltraLite\CE\Arm.50\Lib. For Windows, it is located in %SQLANY16%\UltraLite\Windows\x64\Lib\VS9 or %SQLANY16%\UltraLite\Windows\x86\Lib\VS9.

² For Windows Mobile, this file is located in %SQLANY16%\UltraLite\CE\Arm.50. For Windows, it is located in %SQLANY16%\UltraLite\Windows\x64 or %SQLANY16%\UltraLite\Windows\x86.

³ This file is located in /opt/sqlanywhere16/ultralite/linux/x64/lib.

⁴ This file is located in %SQLANY16%\UltraLite\UltraLiteJ\Android\ARM.

⁵ This file is located in %SQLANY16%\UltraLite\UltraLiteJ\Android.

⁶ For Windows Mobile, this file is located in %SQLANY16%\UltraLite\UltraLite.NET\CE\Arm.50. For Windows, it is located in %SQLANY16%\UltraLite\UltraLite.NET\x64 or %SQLANY16%\UltraLite\UltraLite.NET\win32.

⁷ This file is located in %SQLANY16%\UltraLite\UltraLite.NET\Assembly\V2.

⁸ This file is located in %SQLANY16%\UltraLite\UltraLite.NET\Assembly\V2\en.

⁹ For Mac OS X, this file is located in /Applications/SQLAnywhere16/System/ultralite/macosx/x86_64. For iOS, UltraLite runtimes must be built after installation. Follow the instructions provided in install-dir/ultralite/iphone/readme.txt.

¹⁰ When linking against this library, define the UL_USE_DLL preprocessor macro when compiling. For example, specify the following:

-DUL_USE_DLL

¹¹ This file is located in %SQLANY16%\UltraLite\UltraLiteJ\BlackBerry4.2.

¹²Required for over-the-air (OTA) deployment only. Alternatively, you can create your own .jad file that deploys UltraLiteJ with your application.

Note

To use UltraLite database obfuscation on any platform or device, you must specify the creation parameter obfuscate=1 when creating the database.

Additional build and deployment requirements for synchronization and compression

The following table describes the stream, protocol option, and code requirements for building and deploying an UltraLite application that uses synchronization.

Note

The HTTPS stream option can be enabled in the UltraLiteJ API by passing the SyncParms.HTTPS_STREAM constant to the Connection.createSyncParms method

Synchronization type	Stream option specification	Protocol option requirements	Method call requirements for UltraLite C and C++
TCP/IP	"tcpip"	None	EnableTcpipSynchronization
HTTP	"http"	None	EnableHttpSynchronization
RSA TLS	"tls"	None	EnableTlsSynchronization EnableRsaSyncEncryption
RSA HTTPS	"https"	None	EnableHttpsSynchronization EnableRsaSyncEncryption
RSA FIPS 140-2 TLS	"tls"	fips=yes	EnableTlsSynchronization EnableRsaFipsSyncEncryption
RSA FIPS 140-2 HTTPS	"https"	fips=yes	EnableHttpsSynchronization EnableRsaFipsSyncEncryption

The following table describes additional protocol option and code requirements for building and deploying an UltraLite application that uses compression or end-to-end encryption:

Compression and stream encryption options	Protocol option requirements	Method call requirements for UltraLite C/C++ and UltraLiteJ
ZLIB compression	compression=zlib	C/C++: EnableZlibSyncCompression Java: setZlibCompression
RSA E2EE	e2ee_public_key=key-file	C/C++: EnableRsaE2ee Java: setE2eePublicKey
RSA FIPS 140-2 E2EE	e2ee_public_key=key-file fips=yes	C/C++: EnableRsaFipsE2ee Java: Not applicable

The following table illustrates additional build and deployment requirements for compression and encrypted synchronization.

Note

There are no additional build and deployment requirements for TCP/IP and HTTP synchronization.

Platform or device	ZLIB compression requirements	RSA TLS, RSA HTTPS, and RSA E2EE requirements	RSA FIPS 140-2 TLS, RSA FIPS 140-2 HTTPS, and RSA FIPS 140-2 E2EE requirements
Windows Mobile and desktop (UltraLite C/C++ using static linkage)	None	Link against: ulrsa.lib¹	Deploy: mlcrsafips16.dll² sbgse2.dll²
Windows Mobile and desktop (UltraLite C/C++ using dynamic linkage)	Deploy: mlczlib16.dll²	Deploy: mlcrsa16.dll²	Deploy: mlcrsafips16.dll² sbgse2.dll²
Windows Mobile and desktop (UltraLite C/C++ with the UltraLite engine)	Deploy: mlczlib16.dll²	Deploy: mlcrsa16.dll²	Deploy: mlcrsafips16.dll² sbgse2.dll²
Windows Mobile and desktop (UltraLite.NET)	Deploy: mlczlib16.dll²	Deploy: mlcrsa16.dll²	Deploy: mlcrsafips16.dll² sbgse2.dll²
Windows Mobile and desktop (UltraLite.NET with the UltraLite engine)	Deploy: mlczlib16.dll²	Deploy: mlcrsa16.dll²	Deploy: mlcrsafips16.dll² sbgse2.dll²
Mac OS X and iOS (UltraLite C/C++)	None	None	Not applicable
Linux (UltraLite C/C++)	None	Link against: libulrsa.a³	Not applicable
Android (UltraLiteJ)	None	Deploy: libmlcrsa16.so⁴	Not applicable
BlackBerry (UltraLiteJ)	None	Transfer the DER encoded file using the FileTransfer interface, or store it on an SD card.	Not applicable

² For Windows Mobile, this file is located in %SQLANY16%\CE\Arm.50. For Windows, it is located in %SQLANY16%\Windows\x64 or %SQLANY16%\Windows\x86.

³ This file is located in /opt/sqlanywhere16/ultralite/linux/x64/lib.

⁴ This file is located in %SQLANY16%\UltraLite\UltraLiteJ\Android\ARM.