Types of ODBC Drivers ODBC defines two types of drivers: ?

Single-tier The driver controls ODBC calls to the database(s) only, communications services are assumed to be handled by the relevant DBMS vendor(s) to which the driver provides access. ?Multiple-tier The driver controls both ODBC calls and the manner in which these calls are transferred to the relevant database(s) over your communications infrastructure, this term implies multiple tier of development on the part of the ODBC driver developers. One system can contain both types of configurations. The following paragraphs describe single-tier and multiple-tier configurations in more detail. Single-Tier ConfigurationConfiguration In a single-tier implementation the ODBC driver developer/vendor has embarked on a single tier of development i.e. implementing the ODBC standards data access components only, leaving the communications services required in networked environments to be developed and provided by the vendors of the relevant database engine(s) supported by this type of ODBC driver. The diagram below illustrates the architecture of a single-tier ODBC driver in a network environment.

Multiple-Tier Configuration In a multiple-tier configuration the ODBC Driver developer/vendor embarks on multiple tiers of development, with the sole purpose implementing the communications services required by all ODBC Drivers in networked environments. Multiple Tier ODBC Driver can come network ready out of the box or require the purchase of a 'middleware' module responsible for handling the communications services required by the ODBC Driver. The OpenLink High-Performance ODBC Driver is example of an advanced and very sophisticated implementation of a multiple tier ODBC Driver, the illustration in the next section of this document illuminates the multiple tiers of development effort encapsulated within this ODBC Driver. OpenLink Multi-Tier ODBC Driver Architecture

OpenLink ODBC Drivers makes advanced use of Distributed Object & Component Technology (a concept employed by emerging Objects Technologies, such as OLE 2.0, DSOM etc..), all its components take the form of in-process servers exemplified by the encapsulation of each OpenLink component within a Dynamic/Shared Library or Executable program. OpenLink ODBC Drivers are made up of four key component Objects ;1.Generic ODBC Driver 2.OpenLink Request Agent 3.OpenLink Request Broker

4.OpenLink Database Agents The diagram below illustrates the components that make up the OpenLink HighPerformance ODBC Driver.

The Generic ODBC Driver Component (OPLODBC.DLL) This is the upper most abstraction layer within the OpenLink Multi-Tier architecture, it is a database independent implementation of the Microsoft ODBC 1.0 specification, conforming to the following levels within the specification: Core, Level 1, most of Level 2, and Extensions. ODBC compliant applications establish session with our Generic ODBC Driver via the ODBC Driver Manager. The OpenLink Request Agent Component (OPLWSOCK.DLL) The next layer within our OpenLink Multi Tier Driver's Architectures, is an in-process server called the "OpenLink Request Agent". The Request Agent's main responsibilities, are to provide the following services to the Generic OpenLink ODBC Driver ;1.Database Session Establishment - via the OpenLink Request Broker. 2.Message Relaying - between the Generic OpenLink ODBC Driver, and one, or more OpenLink Database Agents. The OpenLink Request Broker Component (OPLRQB) This in process server is responsible for spawning or replicating one or more OpenLink Database Agents, and then associating these Database Agents with the OpenLink Request

Agent. The OpenLink Request Broker applies a "Rule Book" approach to the process of spawning, replicating, and associating Database Agents with the OpenLink Request Agent. This unique feature enables centralized, flexible and Multi dimensional management, of your OpenLink ODBC based Client-Server infrastructure. OpenLink Database Agent Components These in-process servers are the only components within the OpenLink ODBC Multi Tier architecture that are database specific. The architecture of all OpenLink Database Agents are exactly the same, it is only the methods that make up standard OpenLink Database Operations that is database specific. OpenLink Database Agents act as data access servers for the OpenLink Request Agent on one hand, while on the other hand they act as Clients to the database server processes, of the relevant databases that they support. The OpenLink Database Agents Architecture is a high level abstraction of the SQL Access Group's Call Level Interface (CLI) Spec. Thus, OpenLink Database Agents are built using the relevant Database Engines Call Level Interface. OpenLink Database Agents are available for the following databases engines : Oracle 6 & 7, Informix, Progress, Sybase, Ingres, Unify 2000, MS SQL Server, and SQLBase.