%META:TOPICPARENT{name="SingleTierInstallQuickstartUnix"}%

== <nop>OpenLink Single-tier Components (*nix) for <nop>Informix==

=== Aims and Intentions=== 

This guide is intended to enable competent system administrators to install and configure <nop>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 <nop>Informix, <nop>Informix Connect or <nop>Informix CSDK.
* You **MUST** have an INFORMIXSERVER configured in $INFORMIXDIR/etc/sqlhosts

===Installation===

# Log onto the machine and create a suitable <nop>OpenLink installation directory &lt;<nop>OPENLINK_INSTALL&gt;%BR%
# Copy all relevant components to &lt;<nop>OPENLINK_INSTALL&gt;%BR%%BR% At bare minimum, these will be the <nop>OpenLink ODBC Driver for <nop>Informix, <nop>OpenLink Http Administration Assistant%BR% and <nop>OpenLink license file.%BR%
# Install using the "install.sh" shell script --
{{{
 #sh install.sh

}}}
# 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.%BR%
# The installation should finish without error.

===Configuration===
====Environment====
Open the file &lt;<nop>OPENLINK_INSTALL&gt;/openlink.sh with a suitable text editor such as vi.%BR%
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 <nop>Informix lib and lib/esql directories --
{{{
 
 LD_LIBRARY_PATH="&lt;OPENLINK_INSTALL&gt;/informix/clientsdk.2.90.UC4.SOL_32/lib:/informix/clientsdk.2.90.UC4.SOL_32/lib/esql:$LD_LIBRARY_PATH"
  
}}}
====Driver Specific====
Open the file &lt;<nop>OPENLINK_INSTALL&gt;/openlink.ini with a suitable text editor such as vi.%BR%
Locate the [Environment <nop>Informix xxx] section that deals with the driver specific <nop>Informix configuration and edit to reflect your <nop>Informix installation --
{{{
 
 [Environment Informix 2000]
 INFORMIXDIR        = /informix/clientsdk.2.90.UC4.SOL_32
 INFORMIXSERVER     = &lt;INFORMIX_SERVER&gt;
 DELIMIDENT         = Y  ; Allow quoted identifiers
 OPL_INF_MULTISESS  = Y  ; Allow multiple sessions
 OPL_SPACEPADCHAR   = Y  ; Pad CHAR fields with spaces
 CURSOR_SENSITIVITY = LOW        ; Set to HIGH after loading oplrvc.sql
 FORCE_DORMANT      = 1  ; Set connection dormant after call
 ;FET_BUF_SIZE           = 65535         ; Size of the fetch buffer
 ;FORCE_ONLINE_DATABASE  = 1             ; Force mode to (0) SE or (1) ONLINE
 ;CLIENT_LOCALE          = EN_US.UTF8    ; Unicode connection

}}}
====Data Souce====
Open the file &lt;<nop>OPENLINK_INSTALL&gt;/bin/odbc.ini with a suitable text editor such as vi.%BR%
Locate and edit the sample <nop>OpenLink Informix ODBC data source (DSN) created during the installation process and edit as follows

====Sample Informix Data Source-====
{{{
 
 [informix]
 Driver          = &lt;OPENLINK_INSTALL&gt;/lib/inf9_mt_lt.so
 ServerType      = Informix 2000
 Database        = stores_demo
 Username        = informix
 Password        = **********
 FetchBufferSize = 99
 ReadOnly        = no
 DeferLongFetch  = no
 JetFix          = no
 Description     = Sample Informix 2000 Lite Connection

}}}

===Testing===
Use the {{{iodbctest}}} tool which is packaged with the HTTP-based <nop>OpenLink ODBC Administrator as follows -- 
{{{
 
 #cd &lt;OPENLINK_INSTALL&gt;
 #. ./openLink.sh
 # iodbctest informix
 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 <nop>SQL statements directly against the target database.

====Additional Information====

* The bitness of the ODBC Driver for <nop>DB2 is determined by the bitness of your ODBC client application.%BR%%BR%That is, if your ODBC client application is 32-bit then the Generic ODBC Driver component **MUST** also be 32-bit.