OpenAccess SDK configurations and IP implementation

In an OpenAccess™ SDK client/server configuration, the OpenAccess SDK SQL engine works with OpenAccess SDK Server to receive SQL requests across the network, and to execute them by using the services of the data source-specific IP. A SQL request from a client is transferred to the OpenAccess SDK SQL engine through the OpenAccess SDK client/server components. The OpenAccess SDK SQL engine parses the SQL requests and uses the specified data source IP to access the data. Then the OpenAccess SDK SQL engine packages the results and sends them to the client using the OpenAccess Server.

In an OpenAccess SDK local build, the ODBC layer directly interacts with the OpenAccess SDK SQL engine in a single process space. The OpenAccess network components are not involved. Independent of the client API you plan to support, OpenAccess SDK lets you focus on writing the IP, the "glue" between the OpenAccess SDK SQL engine and your data source.

Each IP is responsible for taking low-level, record-oriented requests and performing them on the respective data source. The dialog between the OpenAccess SDK SQL engine and the IP is executed through the API described in this guide. The IP programmer does not need to know anything about parsing or executing SQL statements.

To implement an optimized IP, the IP programmer should become familiar, by reading this guide, with how the OpenAccess SDK SQL engine processes SQL statements.