skip to main content
Product overview : Overview : OpenAccess SDK configurations : Client/Server configuration
 

Client/Server configuration

In the DataDirect OpenAccess SDK client/server configuration, the OpenAccess SDK Clients for ODBC, JDBC, ADO, and ADO.NET run on one system, while OpenAccess SDK Server runs on the system on which the data source is installed. In the client/server configuration, the OpenAccess SDK Clients and the OpenAccess SDK Server communicate over TCP/IP. This allows the clients and the data source to be on different systems. To make your data source accessible over a network, you need to develop an IP for your data source. All client/server communication issues are handled by the OpenAccess SDK client/server components.
The IP code is also independent of which OpenAccess SDK Client you choose to use. For example, if you write your IP code for use with the Client for ODBC, that same IP code can be used without any changes with the Clients for JDBC, ADO, or ADO.NET.
This means that the IP code you implement to create an ODBC driver can be used without any changes to implement a JDBC driver. Using a client/server build, the OpenAccess SDK Server configured with your IP can be accessed from the drivers for ODBC and JDBC, and from the data providers for ADO and ADO.NET.
Figure 1: OpenAccess SDK Client/Server architecture
Client/Server configuration, showing the Clients connecting to the OpenAccess SDK Server, SQL engine, interface provider, and data source.