OLE DB Data Access Providers - Logical Diagrams

This section provides logical diagrams for OpenLink's OLE DB data access providers.

Single-Tier (Lite Edition) Drivers

Single-Tier (Lite Edition) Drivers

OLE DB Data Access Providers
Lite Bridge Logical DiagramExecutive Summary: A clientside-only solution that provides enterprise grade data access with minimal configuration.

Architectural Components: Application Instance(s), OpenLink Client Provider, ODBC Driver Manager, ODBC DSN, Data Store.

Functional Capabilities: OLE DB data access to SQL data stores via ODBC data sources.

Hardware/OS Dependencies: OpenLink client provider must be installed on a supported operating system. All architectural components on that operating system must share the same bit descriptor, i.e., 32 or 64 bit.

Other Dependencies: OpenLink client provider must be installed on a system that contains a functional ODBC DSN that connects to the target data store. The ODBC DSN may use OpenLink or non-OpenLink drivers. The ODBC drivers on that operating system must share the same bit descriptor as the OpenLink client provider, i.e., 32 or 64 bit.

Performance Levels: High.

Implementation Variances: 1) All architectural components may reside on the same machine, 2) Data store may reside on a remote machine.

Security Features:

Constraints & Limitations: Solution applies only to data stores that are accessible via ODBC DSNs.

User Users are humans or non-human agents that leverage applications to obtain or manipulate SQL data held in data repositories. Users are identified by the hostname or IP address of the machine which hosts their target application(s).
Application Instance The application instance refers to individual instances of applications that users exploit in the target architecture. Each instance of the application(s) is tasked with returning SQL data to users in a manner that is meaningful to them.
OpenLink OLE DB Client Provider The OpenLink Client Provider refers to OpenLink's OLE DB Provider.
Driver Manager The driver manager is a generic utility that loads drivers when requested to do so by client applications. OpenLink's Windows-based drivers are compatible with the Microsoft Driver Manager. OpenLink's Mac and Unix drivers ship with the iODBC Driver Manager. However, these drivers are designed for interoperability with non-OpenLink driver managers such as unixODBC and Intersolv.
OpenLink ODBC Client Driver The OpenLink client driver comprises a clientside-only install of a .dll or other library and supporting files. Single-Tier client drivers are DBMS- or bridge-specific. They establish ODBC connectivity without the assistance of server components. Multi-Tier ODBC client drivers are generic. They require OpenLink server components to complete any data requests.
OpenLink ODBC Client Driver Database native client refers to third-party database client communications software that facilitates connectivity to the target data store. This software speaks the native protocol of that data store.
ODBC DSN or JDBC URL ODBC DSN or JDBC URL refers to ODBC data sources or JDBC connection URLs that pre-exist on the client system. These DSNs or JDBC URLS often use 3rd-party data access products, but they may use OpenLink data access drivers as well. The drivers used to create the DSN or JDBC connection URL must share the same bit descriptor as the OpenLink server components.
OpenLink Server Components The OpenLink server components are architectural components that are specific to the Multi-Tier product format. The server components consist of a Request Broker and an Agent. The Request Broker is a generic, TCP-based listening service. It responds to client driver requests and loads the Agent that is suited for fulling those client requests. Agents may be DBMS- or bridge- specific. Requests for Oracle data are satisfied by one of OpenLink's Oracle Database Agents. Requests for data contained in a JDBC data store are satisfied by one of OpenLink's bridge-based JDBC agents.
Data Data refers to SQL data that is contained in the target data store.
Local IPC Connection Local IPC communications between architectural components. Local IPC communications can only occur when architectural components are hosted on the same, physical machine.
TCP/IP Connection TCP/IP-based communications between architectural components. TCP/IP-based communications can occur across machine boundaries.