How To Install and Configure the Multi-Tier Edition JDBC Drivers for PostgreSQL (Windows)

Server Components

Installation (Request Broker and Database Agent)

  1. Our Enterprise Edition (Multi-Tier) server components installers for Windows are distributed as .msi files. You need to download one Enterprise Edition Request Broker installer (ntbrzzzz.msi for all 32-bit processor architectures, wabrzzzz.msi for x86_64, or wibrzzzz.msi for IA_64) and at least one Agent installer (same architecture) for the specific target data source(s). Double-click on the downloaded request broker .MSI file to start the installation.
  2. The Request Broker installers will specifically prompt for the location of a local license file.

    Note: Agent installers do not, as their licensing is handled through the Broker.
  3. Click the "Browse" button to locate a license file on your Windows machine.
  4. Check the "I don't want to install a license file" box if you do not have one.
  5. Once Completed, run the Database agent installation by clicking on the downloaded .MSI file.
  6. The Request Broker can be started and stopped by locating the OpenLink Request Broker service in the Services panel, or by using the toolbar service shortcut provided after installation.
  7. Installation is complete, proceed to making a test connection with your Client Component installation. If you haven't installed this component, please follow one of the following
Non-Advanced Users should proceed to the Client Components installation and configuration guides
  1. Open the "ODBC Data Sources" application.
  2. Configure 64-bit drivers using the 64-bit application. Configure 32-bit drivers using the 32-bit application.
  3. Select the System DSN tab, then click Add.
  4. Select the OpenLink "Lite" Driver for PostgreSQL Data Sources from the list of available drivers. Choose the Unicode version of the driver if you are working with multi-byte character sets to avoid unnecessary translations that can impact ODBC performance.
  5. Click Finish.
  6. The first dialog prompts for a Data Source Name and an optional description. Click Next.
  7. The second dialog prompts for information that identifies the PostgreSQL database server and the listening port. It also provides a checkbox to verify basic connection parameters before setting advanced and optional settings.
    1. Host name: The hostname or IP address of the server where PostgreSQL runs.
    2. Port: The TCP port on which PostgreSQL listens.
    3. Database: The PostgreSQL database.
    4. No Transactions: Enable this option to automatically commit all transactions, which helps prevent memory errors for large transactions. For example, when exporting 10,000 records from Microsoft Access.
    5. Connect now to verify that all settings are correct: The connection will be attempted once you click Continue.
    6. Login ID: A PostgreSQL username.
    7. Password: A valid PostgreSQL database password.
  8. Click Next.
  9. The third dialog allows you to set PostgreSQL-specific parameters.
    • Enable HSODBC (Oracle Heterogeneous Services) fix: Check this box if you plan to query PostgreSQL through Oracle HSODBC.
  10. Click Next.
  11. The fourth dialog combines database-specific and optional parameters.
    • Database: The Microsoft SQL Server database.
    • Character set: The client application's character set (8-bit only; the Unicode driver always returns UCS-2 on Windows).
    • Language: The language in which you want error messages to be returned. It must be supported by the target server.
    • Packet Size: Specifies the number of bytes per network packet transferred from the database server to the client. Adjusting this value can improve performance. Use 0 for the default packet size specified in the Microsoft SQL Server configuration, -1 to compute the maximum allowable packet size, or an integer from 1 to 10 as a multiple of 512 bytes (e.g., Packet Size of 6 sets the packet size to 6 * 512 = 3072 bytes).
    • Prepare Method: This option is specific to the TDS-based driver for Sybase & Microsoft SQL Server SQL Servers. It determines whether stored procedures are created on the server for SQLPrepare calls.
    • No Quoted Identifiers: Indicates that the underlying driver does not support quoted identifiers, which is required for Jet engine-based products like MS Access.
    • Use ANSI nulls, padding, and warnings: This option affects TDS agent & Lite Driver connections to Microsoft SQL Server databases. It does not affect Sybase connectivity.
    • Map Serializable to Snapshot isolation level: Enable Snapshot transaction isolation level in the driver.
  12. Click Next to continue.
  13. The fifth dialog allows you to set optional ODBC connection parameters.
    • Read-only connection: Specifies whether the connection is read-only. Uncheck this option to perform INSERT, UPDATE, or DELETE operations.
    • Defer fetching of long data: Defers fetching of LONG (BINARY, BLOB, etc.) fields in wildcard queries, improving performance when the query does 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.
    • Row Buffer Size: Specifies the number of records to be delivered from the driver to the client application in a single batch (values range from 1 to 999).
    • Max Rows Override: Allows you to set a limit for the maximum number of rows to be returned from a query. The default value of 0 means no limit.
    • Initial SQL: Lets you specify a file containing SQL statements to be automatically executed against the database upon connection.
    • Dynamic Cursor Sensitivity: Enables or disables the row version cache used with dynamic cursors.
    • Enable logging to the log file: Check this option and provide the full path to a file to log diagnostic information.
  14. Click Next to continue.
  15. The sixth dialog enables you to set additional parameters to enhance compatibility with applications.
    • Enable Microsoft Jet engine options: Facilitates translation of certain data types for the Microsoft Jet Engine.
    • Disable Autocommit: Changes the commit behavior of the OpenLink driver.
    • Disable rowset size limit: Disables a limitation enforced by the cursor library to prevent excessive memory usage with large result sets.
    • Multiple Active Statements Emulation: Enables the use of Multiple Active Statements in an ODBC application even if the underlying database does not support it.
    • SQL_DBMS Name: Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver.
  16. Click Next to continue.

Client Components

Installation

  1. The OpenLink Generic JDBC Driver for Windows is distributed in a single .msi file.
  2. Click the Open link that appears in your Downloads dialog, or double-click the file.
  3. Click Next.
  4. Choose among the Typical, Complete, or Custom installation types.
  5. Click Next.
  6. Use the next dialog to specify the installation directory, if you chose the custom installation option:
    • Click Next.
    • You can choose which options to install if you chose the custom installation option:
      • Click Next.
      • Then click the Install button.
  7. Installation is complete.
    Click the Finish button.
  8. You may be prompted to restart your computer if you have a pre-existing OpenLink License Manager running on your computer.

Configuration

  1. The OpenLink installer should set your CLASSPATH. You should have a pre-existing JAVA_HOME directory that points to the root of your Java installation; this same directory should also be included in your PATH. No further configuration should be needed.
  2. Driver Name: opljdbc.jar, opljdbc2.jar, opljdbc3.jar, megathin.jar, megathin2.jar, megathin3.jar
    Driver Class Name: openlink.jdbc.Driver, openlink.jdbc2.Driver, openlink.jdbc3.Driver
    Connection URL: 
    jdbc:openlink://<Hostname>:[portnumber] [/UID] [/PWD] [/READONLY] [/SVT]
[/APPLICATION] [/FBS|FETCHBUFFERSIZE] [/ENCRYPTED] [/CHARSET] [/UNICODE]
[/DLF] [/DATABASE] [/OPTIONS] [/DRIVER]

    • Hostname - DNS-resolvable hostname or IP address of the machine that runs an OpenLink Request Broker instance.
    • Port Number - TCP port on which the Request Broker listens.
    • /UID - Database username.
    • /PWD - Database password.
    • /READONLY - Read-write or read-only session mode.
    • /SVT - A valid domain alias from the [Domain Aliases] section of the OpenLink server component's oplrqb.ini file. Default domain aliases represent the type of database agent to which the application intends to connect, e.g., DB2, Informix 2000, Oracle 8.1.x. Custom aliases may be any string.
    • /APPLICATION - The Application name. Enables connectivity when restrictive server-side rules screen by application name.
    • /FBS - (also /FETCHBUFFERSIZE) The number of rows to return during one fetch operation.
    • /ENCRYPTED - Encrypt outgoing OpenLink communications packets. Disabled by default. Enabled with '1', 'Y', 'y'; disabled with '0', 'N', 'n'.
    • /CHARSET - The charset of remote databases. The default value is read from System.getProperty("file.encoding").
    • /UNICODE - Enables a Unicode connection. Disabled by default. Enabled with '1', 'Y', 'y'; disabled with '0', 'N', 'n'.
    • /DLF - Defers large data fields (BLOB, CLOB, etc.) to the end of the resultset. Smaller data types are retrieved first. This enhances performance. Disabled by default. Enabled with '1', 'Y', 'y'; disabled with '0', 'N', 'n'.
    • /DATABASE - Actual database name within a particular database environment.
    • /OPTIONS - Optional connection attribute passes specialized database-native client connection parameters, such as Progress socket parameters, Oracle SQL*Net Service Names, Ingres vnodes, remote Informix instance names, or DB2 remote database aliases. Not necessary when ConnectOptions are set in the Broker Rulebook.
    • /DRIVER - An ODBC Driver name wrapped in braces ("{}"). Used for DSN-Less connections to remote ODBC Drivers.
  3. Examples:
    • jdbc:openlink://localhost:5000/SVT=Ingres II/DATABASE=iidbdb/UID=ingres/PWD=ingres
    • jdbc:openlink://192.128.13.119:5555/SVT=Oracle 8.1.x/DATABASE=ORCL/UID=scott/PWD=tiger
    • jdbc:openlink://broker-host.example.com:5050/SVT=Progress 91D/DATABASE=isports/OPTIONS=-S isports -N tcp -H progress-host.example.com
    • jdbc:openlink://broker-host.example.com:5000/SVT=SQLServer 2000/DATABASE=Northwind/UID=sa/OPTIONS= -S mssql-host.example.com