mkdir /opt/openlink
cd /opt/openlink
.taz
archive, and an optional administrator
.taz
file. Download these documents using
binary-preserving methods (e.g., ftp in BIN mode, or scp), and
place them in your installation folder.sh install.sh
http://broker-host.example.com:8000/
admin
." This is the username you will use when
working with the OpenLink Request Broker's HTTP-based Admin
Assistant. (You can set up other usernames later; consider this one
similar to "root
.")admin
." This is the password associated with the
username you just set.[generic_ora{{version}}]
. For Example, the Oracle 12
parameters are located in:[generic_ora12]
.Connect Options = -H {{host}} -P {{port
number}}
.Open the file $OPENLINK_INSTALL/bin/odbc.ini
with a
suitable text editor such as vi.
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 Ingres II Data Source:
[ingres1]
Driver = /OPENLINK_INSTALL/lib/oplodbc.so
Host = requestbroker_hostname:5000
ServerType = Ingres II
Database = test
Options =
Username = ingres
Password = **********
FetchBufferSize = 99
ReadOnly = no
DeferLongFetch = no
JetFix = no
Description = Sample Ingres II Connection
Example Ingres II Data Source (utilizing a vNode):
[ingres2]
Driver = /OPENLINK_INSTALL/lib/oplodbc.so
Host = requestbroker_hostname:5000
ServerType = Ingres II
Database = vnode::database
Options =
Username = ingres
Password = **********
FetchBufferSize = 99
ReadOnly = no
DeferLongFetch = no
JetFix = no
Description = Sample Ingres II Connection
Assuming 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 ingres1
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.
Database Agent modifications are made using the Request Broker's
Rulebook (oplrqb.ini
).
This is located at {{Server Components
Installation}}/bin/oplrqb.ini
Open this document using your preferred text editor (e.g., vim, vi).
Ingres Environments are Denoted by "Environment INFORMIX{Version}".
Locate the Informix environment and confirm that the required values are in place.
[Environment INGRES_II] II_DATE_FORMAT = US II_SYSTEM = /dbs
Save these changes and exit the file.
Run "oplrqb stop
" to stop the request broker.
Run "oplrqb start
" to start the request broker with
your new rulebook settings.
OPENLINK_INSTALL
).OPENLINK_INSTALL
.
At bare minimum, these will be the OpenLink Generic ODBC Driver and OpenLink Http Administration Assistant.
install.sh
" shell script:
#sh install.sh
The installation should finish without error.Open the file $OPENLINK_INSTALL/bin/odbc.ini
with a
suitable text editor such as vi.
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 Ingres II Data Source:
[ingres1]
Driver = /OPENLINK_INSTALL/lib/oplodbc.so
Host = requestbroker_hostname:5000
ServerType = Ingres II
Database = test
Options =
Username = ingres
Password = **********
FetchBufferSize = 99
ReadOnly = no
DeferLongFetch = no
JetFix = no
Description = Sample Ingres II Connection
Example Ingres II Data Source (utilizing a vNode):
[ingres2]
Driver = /OPENLINK_INSTALL/lib/oplodbc.so
Host = requestbroker_hostname:5000
ServerType = Ingres II
Database = vnode::database
Options =
Username = ingres
Password = **********
FetchBufferSize = 99
ReadOnly = no
DeferLongFetch = no
JetFix = no
Description = Sample Ingres II Connection
Assuming 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 ingres1
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.
Need Assistance?
Contact Sales