The architecture of a client/server configuration in which the JVM is loaded by OpenAccess SDK is shown in the following figure. The OpenAccess SDK Client is a ready-to-use component supplied as a DLL. It implements the ODBC, JDBC, ADO, or the .NET API and contains the client/server communications layer for interacting with the OpenAccess SDK Server.
The OpenAccess SDK Server is a ready-to-use component supplied as an executable. At run-time, OpenAccess SDK Server loads the JVM and the class you registered with the OpenAccess SDK Manager for implementing the third-party SQL engine IP interface.
Figure 3: Client/Server Configuration
Steps to developing an ODBC driver for your Java data source:
1 Install the OpenAccess SDK Server and IP SDK.
2 If you are going to expose your schema by creating tables (that is, using OA_TABLES) in your backend, then use the supplied DDL files to create the required tables and populate them with the metadata for the objects you want to expose.
3 Implement the third-party SQL engine IP API for Java in a Java class and register this class using the OpenAccess SDK Manager. Refer to the OpenAccess SDK Administrator’s Guide for more information.
Implementing a client/server configuration with an OLE DB, JDBC, or .NET driver or data provider is the same except that you install the JDBC Client or ADO.NET Client on the client system.
