Our OpenLink Single-Tier JDBC to ODBC Bridge is a Type 1 JDBC driver that enables connectivity from JDBC applications to local ODBC data sources. The Bridge is a single component,client only, install on a JDBC data-consuming machine. No components need be installed on the database server. The Bridge is bound to the ODBC Driver manager, locally, enabling connectivity to any ODBC DSN that is present on the server. This driver is available for Windows and Mac OS X Operating systems

Connecting JDBC-compliant applications to ODBC-accessible data sources remains an important requirement for many brownfield enterprise projects. Naturally, these kinds of projects ultimately boil down to the use of open standards based data-flow as a critical component, as with all pursuit of enterprise agility.

Connecting JDBC-compliant applications to ODBC-accessible data sources remains an important requirement for many brownfield enterprise projects. Naturally, these kinds of projects ultimately boil down to the use of open standards based data-flow as a critical component, as with all pursuit of enterprise agility.

The steps below will guide you through installation and configuration of our Lite Edition (Single-Tier) ODBC-JDBC Bridge Drivers for Windows. Once successfully installed, the JDBC Data Sources on your Windows-based PC will be accessible to any ODBC compliant application running there.

Pre-Installation Requirements

DBMS Requirements

• Your target data source must be SQL compliant.
• You must have all information necessary to configure a JDBC connection to the data source.

Software Requirements

• You need to know whether the client application is 32-bit or 64-bit 58. The Single-Tier “Lite” Edition ODBC Driver for JDBC Data Sources must match the bit format of the client application.
• You must have JDBC drivers that connect to the target data source. The client portion of these drivers must be installed on the same machine as the Single-Tier (“Lite” Edition) ODBC Driver for JDBC Data Sources.
• You must have a JVM (Java Virtual Machine) that is compatible with the Single-Tier “Lite” Edition ODBC Driver for JDBC Data Sources –
  • Generally, the latest JVM from http://java.com/ 9 is the best choice.
  • If using the 32-bit ODBC Driver, you must have the 32-bit JVM, even on 64-bit Windows.
  • If using the 64-bit ODBC Driver, you must have the 64-bit JVM, which is automatically presented only to 64-bit IE but may be manually selected for download using any browser.
  • It is generally best to install both 32-bit JVM and 64-bit JVM on 64-bit Windows.

    Making a connection to SQL Server on Microsoft Azure from an OpenLink ODBC Driver (Connector)

    About the installation and configuration of ODBC connectivity to SQL Server on Microsoft’s Azure Cloud Platform using the OpenLink ODBC Drivers for macOS from a variety of applications, including Microsoft Excel.

    Our OpenLink Single-Tier JDBC to ODBC Bridge is a Type 1 JDBC Driver that enables connectivity from JDBC applications to local ODBC data sources. The Bridge is a single component,client only, install on a JDBC data-consuming machine. No components need be installed on the database server. The Bridge is bound to the ODBC Driver manager, locally, enabling connectivity to any ODBC DSN that is present on the server. This driver is available for Windows and Mac OS X Operating systems.

    Limitations:

    15-day trial

    Using the Data Services Platform JDBC Driver

    The BEA AquaLogic Data Services Platform (DSP) JDBC driver gives client applications a means to obtain JDBC access to the information made available by data services. The driver implements the java.sql.* interface in JDK 1.4x to provide access to an DSP server through the JDBC interface. You can use the JDBC driver to execute SQL92 SELECT queries, or stored procedures over DSP applications. This chapter explains how to install and use the Data Services Platform JDBC driver. It covers the following topics:

    About the Data Services Platform JDBC Driver

    The JDBC driver is intended to enable SQL access to data services. The Data Services Platform JDBC driver enables JDBC and ODBC clients to access information available from data services. The JDBC driver increases the flexibility of the DSP integration layer by enabling access from database visualization and reporting tools, such as Crystal Reports. From the point of view of the client, the DSP integration layer appears as a relational database, with each data service function comprising a table. Internally, DSP translates SQL queries into XQuery.

    There are several constraints associated with the Data Services Platform JDBC driver. Because SQL provides a traditional, two-dimensional approach to data access (as opposed to the multiple level, hierarchical approach defined by XML), the Data Services Platform JDBC driver can only be used to access data through data services that have a flat data shape; that is, the data service type cannot have nesting.

    Also, SQL tables do not have parameters; therefore, the Data Services Platform JDBC driver only exposes non-parameterized flat data service functions as tables. (Parameterized flat data services are exposed as SQL stored procedures.)

    To expose non-flat data services, you can create flat views to be used from the JDBC driver.

    Features of the Data Services Platform JDBC Driver

    The Data Services Platform JDBC driver has the following features:

    • Supports SQL-92 SELECT statements
    • Implements JDBC 3.0 API
    • Supports Data Services Platform with JDK 1.4
    • Usable from both Java and ODBC clients

    Notes:

    • The Data Services Platform JDBC driver contains the following third party libraries: Xerces Java - 2.6.2 : xercesImpl.jar, xmlParserAPIs.jar, and ANTLR 2.7.4 : antlr.jar.
    • The driver also contains the following DSP product libraries: wlclient.jar, ld-client.jar, Schemas_UNIFIED_Annotation.jar, jsr173_api.jar, and xbean.jar.