OpenLink Multi-tier Client Side Components (*nix) (connecting to Progress)

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.

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 Generic ODBC Driver and OpenLink Http Administration Assistant
   
   
3. Install using the "install.sh" shell script --
   
   

   
   #sh install.sh
   
   

   
   
4. The installation should finish without error.

Configuration

1. Open the file $OPENLINK_INSTALL/bin/odbc.ini with a suitable text editor such as vi
   
   
2. Locate and edit the [OpenLink] section, which is a sample OpenLink Generic ODBC data source (DSN) created during the installation process--

Sample DSN as created by installer

[OpenLink]
Driver          = /OPENLINK_INSTALL/lib/oplodbc.so
Host            = localhost:5000
ServerType      = Oracle 8.1.x
Database        = 
Options         = 
Username        = 
Password        = 
FetchBufferSize = 99
ReadOnly        = no
DeferLongFetch  = no
JetFix          = no
Description     = Sample DSN

Example Progress SQL-89/4GL Data Source-

[progress100sql89]
Driver          = /OPENLINK_INSTALL/lib/oplodbc.so
Host            = requestbroker_hostname:5000
ServerType      = Progress 100A
Database        = /dbs/progress/wrk10b/sports2000.db
Options         = -H hostname -S servicename -N tcp
Username        = 
Password        = 
FetchBufferSize = 99
ReadOnly        = no
DeferLongFetch  = no
JetFix          = no
Description     = Sample Progress SQL-89 Connection

Example Progress SQL-92 Data Source-

[progress100sql92]
Driver          = /OPENLINK_INSTALL/lib/oplodbc.so
Host            = requestbroker_hostname:5000
ServerType      = Progress 100SQL
Database        = /dbs/progress/wrk10b/sports2000.db
Options         = -H hostname -S servicename -N tcp
Username        = sysprogress
Password        = 
FetchBufferSize = 99
ReadOnly        = no
DeferLongFetch  = no
JetFix          = no
Description     = Sample Progress SQL-92 Connection

NOTE: The "-H hostname -S servicename -N tcp" parameters represent a socket based connection to the database.

Testing

Presuming the OpenLink Request Broker is already running on the target machine, you are now ready to test the connection.

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

#cd OPENLINK_INSTALL
#. ./openlink.sh
# iodbctest progress100sql92
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 Generic ODBC Driver 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.