Applications can connect to the solidDB® server by using network drivers or by linking to the server directly.
In network-based access methods, the applications and the solidDB® server are separate programs, typically communicating through the solidDB® ODBC Driver or solidDB® JDBC Driver.
Client/server access method
Direct linking is provided through linked library access (LLA) and shared memory access (SMA). SMA and LLA are implemented as library files that contain a complete copy of the solidDB® server in a library form. The SMA and LLA servers can also handle requests from remote applications which connect to the server through network communication protocols such as TCP/IP. The remote applications see the SMA or LLA server as similar to any other solidDB® server; the local SMA and LLA applications see a faster, more precisely controllable version of the solidDB® server.
LLA access method
SMA access method
ODBC
The solidDB® ODBC Driver conforms to the Microsoft ODBC 3.51 API standard. solidDB® ODBC Driver supported functions are accessed with solidDB® ODBC API, a Call Level Interface (CLI) for solidDB® databases, which is compliant with ANSI X3H2 SQL CLI.
For more details on the solidDB® ODBC Driver, see solidDB® Programmer Guide.
JDBC
The solidDB® JDBC Driver allows Java applications to access the database by using JDBC. The solidDB® JDBC Driver implements most of the JDBC 2.0 specification.
For more details on the solidDB® JDBC Driver, see solidDB® Programmer Guide.
Proprietary interfaces
solidDB® also provides two proprietary interfaces, solidDB® Application Programming Interface (SA API) and solidDB® Server Control API (SSC API). These interfaces allow, for example, C programs to directly call functions inside the database server. These proprietary interfaces are provided with the linked library access (LLA) and solidDB® shared memory access (SMA) libraries.
Note The SMA library supports only a subset of the SA API and SSC API functions.
solidDB® SA is a low-level C-language client library for accessing data in solidDB® database tables. The library contains about 90 functions that provide low-level mechanisms for connecting the database and running cursor-based operations.
In most cases, you can use the standards-based interfaces, such as ODBC or JDBC. However, in environments with heavy write loads (BATCH INSERTS AND UPDATES), solidDB® SA can provide a significant performance advantage.
For more information about solidDB® SA, see the solidDB® Programmer Guide.
solidDB® Server Control API (SSC API)
The solidDB® Server Control API (SSC API) is a set of functions that provide simple and efficient means to control the tasking system of a solidDB®. For example, the SSC API functions are used to start and stop the linked library access (LLA) and shared memory access (SMA) server.
For more information about SSC API, see the solidDB® Shared Memory Access and Linked Library Access User Guide.
solidDB® Server Control API (SSC API) for Java
The solidDB® Server Control API (SSC API) for Java is a proprietary API, named after SolidServerControl class. The SSC API for Java calls are used to start and stop the linked library access (LLA) server. The actual database connections are done with normal solidDB® JDBC API. Both the SSC API for Java classes and solidDB® JDBC driver classes are included in the solidDB® JDBC driver (SolidDriver2.0.jar).
For more information about SSC API for Java, see the solidDB® Shared Memory Access and Linked Library Access User Guide.
