OpenLink Single-tier Components (*nix) for SQL Server
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
- Log onto the machine and create a suitable OpenLink installation directory <OPENLINK_INSTALL>
- Copy all relevant components to <OPENLINK_INSTALL>
At bare minimum, these will be the OpenLink ODBC Driver for SQL Server, OpenLink Http Administration Assistant
and OpenLink license file.
- 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.
- The installation should finish without error.
Configuration
Data Souce
Open the file <OPENLINK_INSTALL>/bin/odbc.ini with a suitable text editor such as vi.
Locate and edit the sample OpenLink SQL Server ODBC data source (DSN) created during the installation process and edit as follows--Sample SQL Server 2000 Data Source
[sqlserver]
Driver = <OPENLINK_INSTALL>/lib/sql_mt_lu.so
ServerType = SQLServer 2000
Options = -H sqlserver.hostname -P 1433
Database = database
UserName = sa
Password = **********
FetchBufferSize = 99
ReadOnly = no
DeferLongFetch = no
JetFix = no
Description = Sample SQL Server 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 sqlserver
iODBC Demonstration program
This program shows an interactive SQL processor
Driver Manager: 03.52.0507.0105
Driver: 06.02.1217 OpenLink Generic ODBC Driver (sql_mt_lt.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 SQL Server 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.