Pre-Installation Requirements for Single-Tier “Lite” Edition ODBC Driver for JDBC Data Sources (a/k/a ODBC-to-JDBC Bridge), for Mac OS X
- Your target data source must be SQL compliant.
- You must possess enough knowledge to establish a JDBC connection to this database using third-party or native JDBC drivers.
- You must possess third-party or native JDBC drivers that connect to your target database. A client portion of these drivers must be installed on the same machine as the Single-Tier “Lite” Edition ODBC Driver for JDBC Data Sources.
- The JDBC driver jar file (or a symbolic link to it) must be installed in the /Library/Java/Extensions/ directory which serves as Mac OS X’s default CLASSPATH. Supporting libraries (or links to them) may also need to be installed in this directory, or in one of Mac OS X’s default shared library directories (e.g., /usr/local/lib/, /usr/lib/, etc.).
- You must have a Java Runtime Environment (JRE) that is compatible with our components.
- The JRE was part of the default Mac OS X installation, for Cheetah (10.0) through Snow Leopard (10.6).
- As of Lion (10.7), you may need to manually choose to add Java, but the OS should prompt you to do so when you try to use Java components.
- All Java software shipped by Apple and installed as part of Mac OS X is compatible.
- All Java software obtainable from Oracle for Lion (10.7) and later is compatible.
Important note for Snow Leopard (10.6), Leopard (10.5), and Tiger (10.4) users: PowerPC-based applications on Intel-based Macs cannot connect through our “Lite” Edition ODBC-to-JDBC Bridge, due to limitations in Mac OS X and its JRE. Commonly problematic applications include Microsoft Query as shipped with Microsoft Office:Mac v.X through Microsoft Office:Mac 2011 (upon which Microsoft Excel 2011 and earlier depend), and FileMaker Pro v8 and earlier.
- PowerPC-native applications on PowerPC-based Macs can connect through our “Lite” Edition ODBC-to-JDBC Bridge.
- Intel-native applications, and Universal Binary applications which include Intel-native components, on Intel-based Macs can connect through our “Lite” Edition ODBC-to-JDBC Bridge.
- PowerPC-based applications on Intel-based Macs can connect through our Multi-Tier “Enterprise” Edition JDBC Bridge solution.
- You must be able to connect to the target database using the JDBC driver. OpenLink Product Support can provide minimal assistance in this area.
- You must know the driver class name of the JDBC driver.
- You must know the full details of the JDBC connection URL that connects to your target database.
Installation and Configuration of the Lite Edition (Single-Tier) ODBC Driver for JDBC Data Sources (a/k/a ODBC-to-JDBC Bridge), for Mac OS X
Review Preinstallation Documentation: Pre-Installation Requirements
- The Lite Edition (Single-Tier) ODBC Driver for JDBC Data Sources is distributed in a single disk image (.dmg) file, which contains a Macintosh Installer package (.mpkg).
- Double-click the .mpkg to start the installation process.
- You will encounter a warning message that will ask you if you are sure that you want to install the software. Click Continue.
- The installer will display a Welcome message. Click “Continue.”
- The next screen will display the Read Me file, including any last- minute updates to these documents. Please read carefully and click “Continue” when finished.
- The next screen will display the License Agreement for the Single-Tier “Lite” Edition ODBC Driver for JDBC Data Sources. Please read and click “Continue.”
- You will be prompted to “Agree” to continue the installation or “Disagree” to abort.
- You will be asked to select a Destination Volume. Generally, this should be your Mac OS X boot volume. Click on the desired disk icon and then click “Continue.”
- You may now choose the Easy Install, or if you are an experienced user, you may Customize which components are installed. We generally recommend the Easy Install.
- If you have installed OpenLink or iODBC components in the past, click “Upgrade” to continue. Otherwise, click “Install.”
- If you chose the custom option, select which of the listed components to install.
- You must have an Administration username and password to install this driver. Enter your Mac OS X Username and Password.
- You will be shown a graphical progress bar as the Installation progresses, followed by System Optimization.
- After the driver has been installed, you will be prompted to locate a license file.
NOTE – If a correctly named file already exists in $OPL_LICENSE_DIR, /Library/Application Support/openlink/bin/, you will not see this dialog. If the existing file is not valid (evaluation has expired, it’s for a different OS, it permits insufficient processor cores, etc.), you will need to manually apply a valid license file after installation is completed.
NOTE – In some environments, this dialog may be hidden by the Installer.app or other windows on your Mac. Please minimize, hide, and/or move windows until you can see and act on this dialog. If you do not answer this dialog, the installation will not complete properly, and the driver will not function as desired.
- If a license file already exists on the machine, select the ‘use existing’ option. (Previously generated license files may be re-downloaded from your ODS-Briefcase data space.)
- If you need to obtain a new trial or permanent license file, select the ‘try or buy’ option, which will load a relevant web page from which you can obtain a license file.
- When the process is complete, you will be told that the software was successfully installed. Click “Close” and the Single-Tier “Lite” Edition ODBC Driver for JDBC Data Sources is ready for use.
To configure an ODBC DSN, run the OpenLink iODBC Administrator located in the /Applications/iODBC folder:
- Click the System DSN tab:
- Click the Add button. Then, select the OpenLink JDBC Lite Driver from the list of available drivers. Select the Unicode version of the driver if and only if you are working with multi-byte character sets, as unnecessary translations can significantly affect ODBC performance:
- Click Finish.
- The Data Source tab prompts a Data Source Name and optional description.
- Click Continue.
- The Connection Tab takes the minimum requirements that are necessary to connect to your JDBC data source.
- JDBC Driver - The class name for your third-party JDBC driver, e.g., virtuoso.jdbc3.Driver
- URL String - The JDBC connection URL for your third-party JDBC driver
- Username - The username for your JDBC database
- The Options tab displays additional parameters that can be configured for the connection.
- Row Buffer Size - The number of records to be transported over the network in a single network hop. Values can range from 1 to 99.
- Hide Login Dialog - Suppresses the ODBC “Username” and “Password” login dialog boxes when interacting with your ODBC DSN from within an ODBC compliant application.
- Read Only connection - Specifies whether the connection is “Read-only.” Make sure the checkbox is unchecked to request a “Read/Write” connection.
- Drop Catalog from Meta calls - Enable this option to have the catalog name not appear for tables, views, and procedures when requesting database meta-data.
- Drop Schema from Meta calls - Enable this option to have the schema name not appear for tables, views, and procedures when requesting database meta-data.
- No support of quoted identifier - If set, the call SQLGetInfo for ‘SQL_IDENTIFIER_QUOTE_CHAR’ will return a space (" "). It can be used if the DBMS doesn’t support quoted SQL like SELECT * from “account”
- SQLStatistics disabled - Check this box to have SQLStatistics() return an empty result set. Use this if the underlying database does not support retrieval of statistics about a table (e.g. what indexes it has).
- No support of search string escape - If set, the call SQLGetInfo(SQL_LIKE_ESCAPE_CLAUSE) will return a space (" "). It can be used if the DBMS doesn’t support SQL escape patterns.
- Patch of NULL size of SQL_CHAR - If set, this option overrides the size of SQL_CHAR column type returned by the database with the value set in the text box (in bytes). With a default value of 0, the driver uses the size returned by the database.
- SQL_DBMS Name - Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver. This is required for products like Microsoft InfoPath (for which the value should be “SQL Server”).
- Click Continue to view additional preferences that can be set for the connection.
- Initialization SQL - Lets you specify a file containing SQL statements that will be run automatically against the database upon connection.
- Cursor Sensitivity - Enables or disables the row version cache used with dynamic cursors. When dynamic cursor sensitivity is set high, the Cursor Library calculates check-sums for each row in the current rowset and compares these with the check-sums (if any) already stored in the row version cache for the same rows when fetched previously. If the check-sums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest check-sums for the rowset. From the user’s point of view, the only visible difference between the two sensitivity settings is that a row status flag can never be set to SQL_ROW_UPDATED when the cursor sensitivity is low. (The row status is instead displayed as SQL_ROW_SUCCESS.) In all other respects, performance aside, the two settings are the same. Deleted rows don’t appear in the rowset. Updates to the row since the row was last fetched are reflected in the row data, and inserted rows appear in the rowset, if their keys fall within the span of the rowset. If your application does not need to detect the row status SQL_ROW_UPDATED, you should leave the ‘High Cursor Sensitivity’ checkbox unchecked, as performance is improved. The calculation and comparison of check-sums for each row fetched carries an overhead. Before enabling this option, the table oplrvc must be created using the appropriate script for the target database.
- Max Rows Override - Allows you to define a limit on the maximum number of rows to be returned from a query. The default value of 0 means no limit.
- Disable AutoCommit - Changes the default commit behavior of the OpenLink driver. The default mode is AutoCommit (box unchecked).
- Disable Rowset Size Limit - Disables a limitation enforced by the cursor library. This limitation is enforced by default. It prevents the driver from claiming all available memory in the event that a result set generated from an erroneous query is very large. The limit is not normally reached.
- Defer fetching of long data - Defers fetching of LONG (BINARY, BLOB, etc.) data unless explicitly requested in a query. This can provides significant performance increases when fields in query do not include LONG data fields.
- Multiple Active Statements Emulation - Enables use of Multiple Active Statements in an ODBC application even if the underlying database does not allow this, as it is emulated in the driver.
- Click the Finish button to save your new Data Source Name.