Installing the Multi-Tier “Enterprise” Edition Generic Client ODBC Drivers (Windows)

Data Access Drivers & Connectors Open Database Connectivity (ODBC)
1

Pre-Installation Requirements for the Enterprise Edition (Multi-Tier) Generic Client ODBC Drivers for Windows

As depicted by their architecture, these drivers provide a generic interface to ODBC, JDBC, ADO.NET, and OLE DB compliant applications that enables transparent and secure access to a wide variety of backend database management systems (dbms).

generic-uda-mt-architecture
generic-uda-mt-architecture.png417×720 130 KB

DBMS Requirements

  • There are no DBMS requirements associated with the Enterprise Edition (Multi-Tier) Generic Client ODBC Drivers.

Software Requirements

  • You need to know whether the client application is 32-bit or 64-bit. The Enterprise Edition (Multi-Tier) Generic Client ODBC Drivers must match the bit format of the client application.

Configuration Requirements

  • There are no software configuration requirements associated with the Enterprise Edition (Multi-Tier) Generic Client ODBC Drivers.

Installation and Configuration of the Enterprise Edition (Multi-Tier) Generic Client ODBC Drivers, on Windows

Review Preinstallation Documentation: Enterprise Edition (Multi-Tier) ODBC Client Components

Installation

  1. Our Enterprise Edition (Multi-Tier) Generic ODBC client is distributed in a single Windows MSI file. Simply run the appropriate installer for x86, x86_64 (Opteron, Xeon, other families), or IA_64 (Itanium family). You should see the following Welcome message:

win64instmt1.gif

  1. The next screen will display the License Agreement for use with our Enterprise Edition (Multi-Tier) Driver product. Please read this. If you agree, check the accept checkbox and continue:

win64instmt2.gif

  1. Choose the type of installation to perform, noting that typical and complete will immediately install the default or complete components respectively. Otherwise, select the custom option, which enables you to pick and choose options to install:

win64instmt3.gif

  1. Use this dialog to specify the installation directory, if you chose the custom installation option:

win64instmt4.gif

  1. You can choose which options to install, if you chose the custom installation option:

win64instmt5.gif

  1. A final confirmation screen is displayed for your review prior to performing the installation:

win64instmt6.gif

  1. The installer status bar indicates the progress and status of the the installation:

win64instmt7.gif

  1. If the installation is successful, a final dialog will be displayed indicating this:

win64instmt8.gif

Configuration

  1. Launch the ODBC Administrator appropriate to the bitness (32-bit or 64-bit) of your client application and driver.

  1. Click the Add button that appears on the System DSN tab.

  1. Select the OpenLink Generic ODBC Driver v6.0 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:

  1. Click Finish.

  2. The first DSN configuration dialog takes these values:

  • Name : A suitable name for your Data Source

  • Description : An optional description for your Data Source

  • Server : The host name or IP address of the machine containing your OpenLink Request Broker and the Broker’s listen port. A colon separates the two. For example: 192.158.12.234:5000 .

  1. Click Next.

  2. The second DSN configuration dialog takes these values:

  • Domain - The value must match a [Domain Alias], which is contained in the Server’s Session Rules Book. This Alias typically represents the name and version of an OpenLink Agent. That agent version may differ from the DBMS version to which it connects. Note that advanced users may create custom domain names that follow their own, desired conventions.

  • Database - Takes a database name or Oracle SID.

  • Options - This field passes parameters that enable users to connect to MySQL, PostgreSQL, SQLServer, and Sybase databases anywhere on the network. It also passes parameters that enable users to connect to any DBMS that does not reside on the same machine as the OpenLink Request Broker and Agent. Review Complete Settings and Usage for Connect Options

  • Secure Connection - If checked, the client sets up a secure connection to the Request Broker.

  • Connect now to verify that all settings are correct - Will attempt to connect to the database, once you click Continue.

  • Login ID - A valid database uid.

  • Password - A valid database password.

  • XA Info - Refer to OpenLink’s extensive Distributed Transaction Processing documentation for use of this field.

  1. Click Next.

  2. The third tab contains settings that are not required for a basic connection:

  • Read Only connection - Specifies whether the connection is “Read-only.” Make sure the checkbox is unchecked to request a “Read/Write” connection.

  • Defer fetching of long data - Defers fetching of LONG (BINARY, BLOB etc.) data unless explicitly requested in a query. This provides significant performance increases when fields in query do not include LONG data fields.

  • Disable interactive login - Suppresses the ODBC “Username” and “Password” login dialog boxes when interacting with your ODBC DSN from within an ODBC compliant application.

  • 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.

  • Row Buffer Size - Specifies the number of records to be transported over the network in a single network hop. Values can range from 1 to 99.

  • 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 return the value should be “SQL Server”).

  1. Click Next.

  2. Click on the ‘Test Data Source’ button to make a connection to the database to verify connectivity:

  1. A successful connection to the database has been made:

Testing ODBC DSNs on Windows, with C++ Demo

C++ Demo is a simple ODBC-based Interactive SQL processor written, as may be obvious from its name, in C++. The binary executable may be found at –

<OPENLINK_INSTALLATION_DIRECTORY>\samples\odbc

As with other sample applications we ship, when source code is available, it may be found alongside the executable.

Be sure to launch the tool appropriate to the Driver and DSN you are testing –

Driver/DSN Windows default location
64-bit 64-bit C:\Program Files\OpenLink Software\UDA\Samples\Odbc\cppdemo.exe
32-bit 64-bit C:\Program Files (x86)\OpenLink Software\UDA\Samples\Odbc\cppdemo.exe
32-bit 32-bit C:\Program Files\OpenLink Software\UDA\Samples\Odbc\cppdemo.exe
  1. The tool will launch.

  1. Select menu item Environment >> Open Connection . The ODBC Driver Manager will present a list of available ODBC DSNs. Select the DSN to which you wish to connect (“Informix 7 on Local” has been selected, below) –

  1. You will be presented with a Login Dialog. Enter the user name and password for the target database, and click Connect –

  1. You should now be connected to the chosen data source. Use the SQL >> Execute SQL menu item to get the SQL input dialog. Enter any valid SQL statement (see example in screen shot), and click OK .

  1. You will be presented with the results of your query.

  1. Close the connection by selecting the Environment >Close Connection menu item. Exiting the application through any normal Windows pattern will also close the connection.

Related