Linked Library Access (LLA) enables Java applications to start a local solidDB server that is loaded into the Java Virtual Machine context from a dynamic library. The Java application is then able to connect to the solidDB server and use the services that the solidDB server provides through a standard JDBC API.

When you use LLA with Java/JDBC, you link the following components into a single executable process:

The layers in the executable process are, from top to bottom:

Java commands in your client are executed by the JVM. If the command is a JDBC function call, the JVM calls the appropriate function in ssolidacver. The function call is direct, it does not go through the network (through RPC). The calls are made using Java Native Interface (JNI). You do not need to write any JNI code yourself; you simply have to call the same JDBC functions that you would call if you were a remote client program.

Accessing a solidDB database from with LLA is identical to accessing a solidDB database through RPC — with one exception: to access the database services, the application using LLA must first start the LLA server. You can start the LLA server with a proprietary API called solidDB Server Control (SSC) API for Java (named after SolidServerControl class. The actual database connections are done with normal solidDB JDBC API. Both the SSC API for Java and solidDB JDBC driver can be found in the .jar file named SolidDriver2.0.jar.

When the local solidDB server is started, it is loaded into the Java Virtual Machine context from the dynamic library. The Java application can then connect to the solidDB server and use the services the server provides through a standard JDBC API.