For LLA with Java, you also require the solidDB JDBC driver (SolidDriver2.0.jar) in which the JDBC driver and solidDB proprietary control classes are embedded.
The library contains the entire solidDB server, except that it is in the form of a callable library instead of a stand-alone executable program. The same libraries are used with C/ODBC applications and Java/JDBC applications; the driver library that you require depends on your operating system platform.
▪ For Windows:
– Dynamic library: ssolidacver.dll
– Static library: solidimpac.lib (an import library file that gives you access to the dynamic library file)
▪ For Linux, Solaris, and AIX:
– Dynamic library: solidacver.so
– Symbolic link: libssolidacver.so (gives you access to the dynamic library file)
where ver is the solidDB version number.
The LLA library for all platforms contains the following components:
▪ full solidDB server functionality
▪ the following API functions:
▪ solidDB ODBC driver functions to communicate directly with the server library, without going through the network.
▪ solidDB Control (SSC) API library functions to control task scheduling.
▪ solidDB API (SA) library functions, for example, to insert, delete, and select records from a table.
Since your application links to a library that contains these APIs, your application program can call functions from any combination of these APIs. For details on each of these APIs, see solidDB APIs and drivers for SMA and LLA.
Note Although remote applications also have access to the same APIs (ODBC, SSC, and SA), the functions for these APIs are not all in the same file. For information about remote and dual role applications, read Configurations with local and remote applications. For information about API files for remote applications, read solidDB APIs and drivers for SMA and LLA.