HOME | Performance | Installation | Download | Author |
Boeireep Database Driver |
||||||||||||||||
(Generic High - Performance Database Driver) |
||||||||||||||||
IntroductionBoeireep Database Driver ( BDD ) is a middleware product of standards-based client/server that allow clients to access database on multiple servers using existing operationg system and TPC/IP network. It consists of BDD JDBC driver, BDD ODBC driver and BDD Server. The BDD ODBC driver supports Open Database Connectivity ( ODBC ) 2.X-compliant applications. The BDD JDBC driver supports Java Databse Connectivity ( JDBC ) 1.1-compliant applications. The BDD Server is the common server component for the BDD ODBC driver and the BDD JDBC driver, providing data access services between ODBC and JDBC client applications and server databases. It uses a common architecture and common functionality across its supported platforms, with only a few platform-specific differences. The BDD Server consists of BDD Request Broker and particular BDD Database Agents. The BDD Request Broker is the component responsible for connection management between client and agents. Clients make requests for connections to the BDD Request Broker which, based on the information from the client and the mapping rules in the configuration file, start an BDD Database Agent for the Client to connect to. The BDD Server provides data access services for applications using the ODBC and JDBC standard interfaces. These ODBC and JDBC calls are sent across your network from BDD clients to the BDD Server service, which passes the requests to the database engine. The database engine processes the requests and passes the results back to the BDD Server service, which returns to the client. |
||||||||||||||||
Product Features |
||||||||||||||||
BDD ServerThe BDD Server consists of BDD Request Broker and particular BDD Database Agents. The BDD Request Broker is the component responsible for connection management between client and agents. Clients make requests for connections to the BDD Request Broker which, based on the information from the client and the mapping rules in the configuration file, start an BDD Database Agent for the Client to connect to. The BDD Request Broker is a Generic server component that manages BDD service provider location, binding, instantiation. The BDD Database Agents are server based data access service providers, abstracting the underlying Call Level Interfaces (CLIs) of supported database engines via a uniform interface definition. As a result they are database specific in nature with respect to call database engines but generic in relation to the methods referenced by other Generic BDD client components. Features:
Operating Systems and Database Engines supported:
Limitations: p.s. LONGVARCHAR and LONGBINARY temporarily have maximum length 32Kb. | ||||||||||||||||
BDD JDBC driverThe BDD JDBC driver is a generic high-perfomance Type 3 Driver for JDBC, that provide easy and fast access to remote database engines from JDBC complaint Java Application, Applets, Servlets and other. Features:
Operating Systems supported:
Limitations: The BDD JDBC driver supports all
functions JDBC version 1.2 (for jdk 1.1) except for(temporaly):
DatabaseMetaData:
PreparedStatement:
ResultSet:
p.s. java.sql.Types.LONGVARCHAR and java.sql.Types.LONGBINARY temporarily have maximum length 32Kb. |
||||||||||||||||
BDD ODBC driverThe BDD ODBC driver is a generic high-perfomance 32-bit driver from ODBC complaint tools. Features:
Operating Systems supported:
Limitations: The BDD ODBC driver is a 2.x ODBC driver that supports all
core and level 1 functions plus the following level 2 functions(temporaly):
p.s. SQL_LONGVARCHAR and SQL_LONGBINARY temporarily have maximum length 32Kb. | ||||||||||||||||
Please, send your comments to : Sergei Malinin
|
||||||||||||||||
p.s Now there are
versions BDD for CA-Ingres 6.4, OpenIngres 1.x and Ingres II for OS:
WindowsNT 4.0/2000, Linux, Solaris2.x.
Details
below... |
||||||||||||||||
|
||||||||||||||||