Previous PageNext Page

3.3.3 ODBC.INI

The ODBC.INI file is located in the Chili!Soft ASP instance subdirectory of the Chili!Soft ASP installation directory. This file contains data source name entries for each database configured for use with a particular instance of Chili!Soft ASP. Use a text editor to change data source entries in ODBC.INI.
 
The following example shows a list of data source entries in an ODBC.INI file:
 

[ODBC Data Sources]

My_Oracle_DB=Sample Oracle 7 dsn

Test_MySQL=MySQL dsn

My_Sybase_DB=Sample Sybase dsn

The following example shows configuration information for an Oracle database:
 

[My_Oracle_DB]

Driver=/opt/odbc/lib/ivor712.so

Description=Sample Oracle 7 dsn

ServerName=OracleTNSName

LogonID=odbc01

Password=odbc01

EnableScrollableCursors=1

3.3.3.1 DB2 Setup

Required software for the machine running Chili!Soft ASP:
 

Platform Requirements
Solaris
 
  • IBM DB2 Client Application Enabler (CAE) for Solaris, version 2.1 or higher
  • IBM DB2 Software Development Kit (DB2 SDK) for Solaris, version 2.1 or higher
AIX:
 
  • IBM DB2 Client Application Enabler (CAE) for AIX, version 2.1 or higher
  • IBM DB2 Software Development Kit (DB2 SDK) for AIX, version 2.1 or higher
HP-UX
 
  • IBM DB2 Client Application Enabler (CAE) for HP-UX, version 2.1 or higher
  • IBM DB2 Software Development Kit (DB2 SDK) for HP-UX, version 2.1 or higher

Note:

The DB2 Server must be installed as the Server Version (not the Local Version)

Binding
To bind the Merant SQL files for DB2 enter the following commands:
 

Solaris:

db2=> BIND odbcv1sol.bnd blocking all grant public

HP-UX:

db2=> BIND odbcv1hp.bnd blocking all grant public

AIX:

db2=> BIND odbcv1aix.bnd blocking all grant public

3.3.3.2 DBASE Setup

The dBASE ODBC driver support dBASE IV and V in the UNIX environment. The driver runs the SQL statements directly on dBASE-compatible files.
 

Note:

You do not need to own dBASE products to access these files.

3.3.3.3 Informix Setup

The Informix ODBC driver requires Informix-Connect or ESQL-C 7.23.
 
The INFORMIXDIR environment variable must be set to the directory where the Informix client is installed. The INFORMIXSERVER variable must be set to the name of the Informix server as defined in your $INFORMIXDIR/ext/sqlhosts file. For further details, refer to the Informix Dynamic Server Administrator's Guide, Volume 2 or the Informix UNIX Installation Guide.
 
The following command will set the INFORMIXDIR environment variable for C-shell users:
 

Setenv INFORMIXDIR /databases/informix

for Bourne- or Korn-shell users, use the following command:
 

INFORMIXDIR=/databases/informix;export INFORMIXDIR

3.3.3.4 Microsoft Access Setup

Chili!Soft ASP includes the SequeLink ODBC 4.5.1 client drivers that allow your UNIX system to connect to Microsoft Access databases running on Windows NT 3.51 or 4.0 systems. SequeLink also requires server software to be installed on the Window NT system. Please contact Chili!Soft for instructions on how to download the required server software. To configure the SequeLink client:
 
From the Chili!Soft ASP instance subdirectory of the Chili!Soft ASP installation directory type:
 

./setsqlnk

Select option [2] New to create a new SequeLink DSN. Follow the options, filling in the information when prompted.
 
  • Name: The name of the SequeLink DSN that you want to create.
  • Description: Optional
  • Transliteration: Leave this AS IS.
  • Select a network: Select TCP.
  • Host: Enter the IP address of the NT server where your database resides.
  • ServerType: Select NT Server.
  • User: Enter the user for accessing the NT server.
  • Password: Enter the password for the user to access the NT server.
  • Select a Database service: Select ODBC MS Access.
  • Name: Enter the name of the NT service that you created when installing the SequeLink Server software.
  • Database: Enter the name of the database you want this DSN to connect to (for example, E:\DATA\PUBLISH.MDB). Note the Windows syntax for providing the path information.
  • Select option [6] Test. The setup utility should return "Test Passed". If you receive an error, select option [4] to edit your DSN information.
  • After completing SequeLink setup, select option [0] to exit.
  • Open the ODBC.INI file in the Chili!Soft ASP instance subdirectory of the Chili!Soft ASP installation directory.
  • A default DSN section named [SQLNK] is provided. Either edit the existing section or make a copy of the section and change SQLNK to the DSN you will use in ASP pages. If you create a new DSN name, be sure to add a new entry at the top of the file.
Inside the SQLNK section, enter the SequeLink DSN name you just created for the parameter "SqlnkDSN="
 

3.3.3.5 Microsoft SQL Server Setup

Chili!Soft ASP includes the SequeLink ODBC 4.5.1 client drivers that allow your UNIX system to connect to Microsoft SQL Server databases running on Windows NT systems. SequeLink also requires server software to be installed on the Window NT system. Please contact Chili!Soft for instructions to download the required server software. To configure the SequeLink client:
 
From the Chili!Soft ASP instance subdirectory of the Chili!Soft ASP installation directory type:
 

./setsqlnk

Select option [2] New to create a new SequeLink DSN. Follow the options, filling in the information when prompted.
 
  • Name: The name of the SequeLink DSN that you want to create.
  • Description: Optional
  • Transliteration: Leave this AS IS.
  • Select a network: Select TCP.
  • Host: Enter the IP address of the NT server where your database resides.
  • ServerType: Select NT Server.
  • User: Enter the user for accessing the NT server.
  • Password: Enter the password for the user to access the NT server.
  • Select a Database service: Select MS SQL Server.
  • Name: Enter the name of the NT service that you created when installing the SequeLink Server software.
  • Database: Enter the name of the database you want this DSN to connect to.
  • User: Enter the SQL Server user for accessing the database.
  • Password: Enter the password for accessing the SQL Server database (required).
  • Select option [6] Test. The setup utility should return "Test Passed". If you receive an error, select option [4] to edit your DSN information.
  • After completing SequeLink setup, select option [0] to exit.
  • Open the ODBC.INI file in the Chili!Soft ASP installation directory.
  • A default DSN section named [SQLNK] is provided. Either edit the existing section or make a copy of the section and change SQLNK to the DSN you will use in ASP pages. If you create a new DSN name, be sure to add a new entry at the top of the file.
Inside the SQLNK section enter the SequeLink DSN name you just created for the parameter "SqlnkDSN=".
 

3.3.3.6 MySQL Setup

Source-code for the MyODBC driver for the MySQL database can be downloaded off the Internet from http://www.mysql.org. On Solaris, Chili!Soft ASP includes a pre-built version of MyODBC (version 2.50.22) for your convenience, but we do not provide support for either MyODBC or MySQL.
 
With version 2.50.22 of the MyODBC driver for Unix, the driver is not able to read any information out of the ODBC.INI file. Any attributes you place in the ODBC.INI file will have no effect (with the version 2.50.22 driver. With later versions, this may change.) All attributes for your MySQL database must be passed in via a database connection string, for example:
 

Connection.Open "Driver={MySQL}; SERVER=your.mysql.host; DATABASE=your db name; UID=userID; PWD=password"

If the SERVER attribute is omitted, the MyODBC driver assumes MySQL is on localhost. With this type of connection string, the DATABASE attribute may not be omitted. With this connection string, the [mysql] default entry in the ODBC.INI file will be used. The following example shows the default ODBC.INI entry for MySQL:
 

[mysql]

Driver=/opt/casp/odbc/lib/libmyodbc_mysql_26.so

You may also connect to a MySQL database by using a DSN (data source name) in your connection string, but you must still provide the other important attributes in the connection string. With the following connection string:
 

Connection.Open "DSN=test_mysql; SERVER=your.mysql.host; DATABASE=your db name; UID=userID; PWD=password"

you must have an entry in your ODBC.INI file for test_mysql, like so:
 

[test_mysql]

Driver=/opt/casp/odbc/lib/libmyodbc_mysql_26.so

With this type of connection string, you may omit both the SERVER and DATABASE attributes. If you omit SERVER, MyODBC will assume localhost. If you omit DATABASE, MyODBC will use the DSN (in this case, test_mysql)as the name of the database.
 
Because MyODBC only provides support for Forward-only cursors, the Chili!Soft ADO control uses the ODBC Driver Manager's cursors. Via the Driver Manager's cursor support, MySQL users have access to Forward-only and Static cursors. Keyset and Dynamic cursors are not available with MySQL.
 

Note:

If you are using Solaris 2.51, substitute libmyodbc_mysql_251.so as the name of the driver. If you are using AIX, you must download the MyODBC driver source code from http://www.mysql.org and build it on your platform. Enter the location of the resulting libmyodbc_mysql.so file as the Driver attribute in the MySQL database section.

3.3.3.7 OpenIngres Setup

The host OpenIngres database must be INGRES 1.2 or later. The II_SYSTEM environment variable must be set to the parent directory of the directory where the Ingres client is installed.
 
For example, if your Ingres product is installed in /databases/ingres, the following syntax is valid for C-shell users:
 

Setenv II_SYSTEM /databases

for Bourne- or Korn-shell users the following syntax is valid:
 

II_SYSTEM=/databases;export II_SYSTEM

3.3.3.8 Oracle Setup

Oracle SQL*Net is required to access remote Oracle databases. The Oracle ODBC driver depends on the executables located in $ORACLE_HOME/bin and the interface libraries in $ORACLE_HOME/rdbms/lib. The $ORACLE_HOME environment variable identifies the location of your client components, it is created by the Oracle installation process.
 

3.3.3.9 Sybase Setup

The Sybase ODBC driver relies on the Sybase Open Client Library and the appropriate Sybase Net Library to gain access to the Sybase server. Before the data source can be used, the required Sybase libraries must be installed in the $SYBASE source tree.
 
Set the SYBASE environment variable to the directory where you installed the System client. For C-shell users, the following syntax is valid:
 

setenv SYBASE /databases/sybase

for Bourne- or Korn-shell users, the following syntax is valid:
 

SYBASE=/databases/sybase;export SYBASE

Include the directory containing the System client shared libraries in the LD_LIBRARY_PATH (on Solaris) LIBPATH (on AIX), or SHLIB_PATH (on HP-UX) environment variables. For C-shell users, use:
 

setenv LD_LIBRARY_PATH /database/sybase/

lib:$LD_LIBRARY_PATH

for Bourne- or Korn-shell users, use:
 

LD_LIBRARY_PATH=/database/sybase/

lib:$LD_LIBRARY_PATH;export LD_LIBRARY_PATH

3.3.3.10 Text file Setup

The text ODBC driver provides an option for defining the structure of an existing file. To define the structure of a text file, you must create a QETXT.INI file using a text editor. Specify the attributes of all defined tables in this file. Any attributes specified in ODBC.INI or a connection string are overridden by settings in the QETXT.INI file. See the Merant documentation for a description of the QETXT.INI file.
 

Copyright © 2000 Chili!Soft

Previous PageTop Of PageNext Page