Configuration through the system information (odbc.ini) file
In the Linux environments, a system information file is used to store data source information. Setup installs a default version of this file, called odbc.ini, in the product installation directory. This is a plain text file that contains data source definitions.
To configure a data source manually, you edit the odbc.ini file with a text editor. The content of this file is divided into three sections.
Note: The driver and driver manager support ASCII and UTF-8 encoding in the odbc.ini file. For additional details, refer to the Character encoding in the odbc.ini and odbcinst.ini files in Progress DataDirect for ODBC Drivers Reference.
At the beginning of the file is a section named [ODBC Data Sources] containing data_source_name=installed-driver pairs, for example:
Dynamics2=DataDirect 8.0 Microsoft Dynamics 365
The driver uses this section to match a data source to the appropriate installed driver.
The [ODBC Data Sources] section also includes data source definitions. The default odbc.ini contains a data source definition for the driver. Each data source definition begins with a data source name in square brackets, for example, [Dynamics2]. The data source definitions contain connection string attribute=value pairs with default values. You can modify these values as appropriate for your system. "Connection Option Descriptions" describes these attributes. See "Sample Default odbc.ini File" for sample data sources.
The second section of the file is named [ODBC File DSN] and includes one keyword:
[ODBC File DSN]
DefaultDSNDir=
This keyword defines the path of the default location for file data sources (see "File Data Sources").
Note: This section is not included in the default odbc.ini file that is installed by the product installer. You must add this section manually.
The third section of the file is named [ODBC] and includes several keywords, for example:
The IANAAppCodePage keyword defines the default value that the Linux driver uses if individual data sources have not specified a different value. See "IANAAppCodePage" in the "Connection Option Descriptions" for details. For supported code page values, refer to Code page values in the Progress DataDirect for ODBC Drivers Reference. The default value is 4.
The InstallDir keyword must be included in this section. The value of this keyword is the path to the installation directory under which the /lib and /locale directories are contained. The installation process automatically writes your installation directory to the default odbc.ini file.
For example, if you choose an installation location of /opt/odbc, then the following line is written to the [ODBC] section of the default odbc.ini:
InstallDir=/opt/odbc
Note: If you are using only DSN-less connections through an odbcinst.ini file and do not have an odbc.ini file, then you must provide [ODBC] section information in the [ODBC] section of the odbcinst.ini file. The driver and Driver Manager always check first in the [ODBC] section of an odbc.ini file. If no odbc.ini file exists or if the odbc.ini file does not contain an [ODBC] section, they check for an [ODBC] section in the odbcinst.ini file. See "DSN-less Connections" for details.
ODBC tracing allows you to trace calls to the ODBC driver and create a log of the traces for troubleshooting purposes. The following keywords all control tracing: Trace, TraceFile, TraceDLL, ODBCTraceMaxFileSize, and ODBCTraceMaxNumFiles.
For a complete description of these keywords and discussion of tracing, refer to ODBC trace in the Progress DataDirect for ODBC Drivers Reference.
