OpenLink Single-tier Components (*nix) for Ingres

Aims and Intentions

This guide is intended to enable competent system administrators to install and configure OpenLink Multi-tier client side components on *nix style operating systems in a few steps as possible.

This guide does not explain any of the non-pertinent features encountered along the way. Such explanations may be found in the full documentation.

Prerequisites

  • You MUST be proficient in using a Unix shell.
  • You MUST be proficient in using a Unix editor such as vi
  • You MUST be in possession of relevant database connectivity details such as Database name, Username, password, etc.
  • You MUST have installed, and available; a full installation of Ingres Net and the Ingres Name Server Started.
  • You MUST have configured an Ingres Net vNode (using netutil) if connectivity is to a remote database.

Installation

  1. Log onto the machine and create a suitable OpenLink installation directory <OPENLINK_INSTALL>
  2. Copy all relevant components to <OPENLINK_INSTALL>

    At bare minimum, these will be the OpenLink ODBC Driver for Ingres, OpenLink Http Administration Assistant
    and OpenLink license file.
  3. Install using the "install.sh" shell script -- 


     #sh install.sh

  4. You should take care to enter correct information when prompted pertaining to ports, passwords, etc and ensure that you note these down for future use.

  5. The installation should finish without error.

Configuration

Environment


Open the file <OPENLINK_INSTALL>/openlink.sh with a suitable text editor such as vi.

Locate the section that deals with the location of shared libraries pertaining to your system (LD_LIBRARY_PATH, LIBPATH or SHLIB_PATH) and add to it the location of your Ingres lib directory -- 

 
 LD_LIBRARY_PATH="<OPENLINK_INSTALL>/lib:/ingres/ingres/lib:$LD_LIBRARY_PATH"

Driver Specific


Open the file <OPENLINK_INSTALL>/openlink.ini with a suitable text editor such as vi.

Locate the [Environment Ingres II] section that deals with the driver specific Ingres configuration and edit to reflect your Ingres installation -- 

 
 [Environment Ingres II]
 II_SYSTEM          = /ingres/
 II_DATE_FORMAT     = US
 ING_SET            = set lockmode session where readlock=nolock
 CURSOR_SENSITIVITY = LOW        ; Set to HIGH after loading oplrvc.sql

Data Souce


Open the file <OPENLINK_INSTALL>/bin/odbc.ini with a suitable text editor such as vi.

Locate and edit the sample OpenLink ODBC data source (DSN) created during the installation process and edit as follows--

Sample Ingres Data Source (database on same machine)

 
 [ingres]
 Driver            = <OPENLINK_INSTALL>/lib/ingii_mt_lt.so
 ServerType        = Ingres II
 Username          = ingres
 Password          = **********
 Database          = database
 FetchBufferSize   = 99
 ReadOnly          = No
 JetFix            = No
 NoRowSetSizeLimit = No
 NoAutoCommit      = No
 NoLoginBox        = No
 Description       = Sample Ingres II Lite Connection

Sample Ingres Data Source (remote database using vNode)

 
 [ingres]
 Driver            = <OPENLINK_INSTALL>/lib/ingii_mt_lt.so
 ServerType        = Ingres II
 Username          = ingres
 Password          = **********
 Database          = vnode::database
 FetchBufferSize   = 99
 ReadOnly          = No
 JetFix            = No
 NoRowSetSizeLimit = No
 NoAutoCommit      = No
 NoLoginBox        = No
 Description       = Sample Ingres II Lite Connection

Testing


Use the iodbctest tool which is packaged with the HTTP-based OpenLink ODBC Administrator as follows -- 

 
 #cd <OPENLINK_INSTALL>
 #. ./openLink.sh
 # iodbctest ingres
 iODBC Demonstration program
 This program shows an interactive SQL processor
 Driver Manager: 03.52.0507.0105
 Driver: 06.02.1217 OpenLink Generic ODBC Driver (oplodbc.so) 

 SQL>


You should now be able to issue SQL statements directly against the target database.

Additional Information

  • The bitness of the ODBC Driver for DB2 is determined by the bitness of your ODBC client application.

    That is, if your ODBC client application is 32-bit then the Generic ODBC Driver component MUST also be 32-bit.
Referenced by...