You can use OpenAccess SDK to implement either a client/server solution or a local solution.
To make your data source accessible through ODBC, JDBC, ADO, or .NET over a network, create the IP for your data source as described in this book. All client-side API and client/server communication issues are handled by the OpenAccess SDK components.
The IP code you write is 100% portable. It is independent of the OpenAccess SDK Client you choose to use. For example, if you write your IP code for use with the ODBC Client, that same IP code can be used without any changes with the JDBC or ADO.NET Client.
The following figure shows the architecture of an OpenAccess SDK client/server configuration. The OpenAccess SDK Client runs on the client system and the server portion runs on the system containing the SQL data source; the two communicate using TCP/IP.
The following figure shows the ODBC Client in a local, or single-tier, configuration. The client and server pieces communicate through memory.
Figure 1: OpenAccess SDK Data Access in a Local Configuration
