Important: To query your data, you must define the tables in your schema using the Add Tables (AddTables) option. Although you can set this value manually, we recommend generating a value for this option using the Configure Logical Schema tool in the Configuration Manager. The Configuration Manger is currently supported only on Windows platforms, but you can use an evaluation or licensed copy of the Windows driver to create your Add Tables value for the Linux driver. See Installing and setting up the driver (Windows) for details.

This section provides you with an overview of the steps required to install and set-up the driver. After completing this procedure, you will be able to begin accessing data with your application.

To begin accessing data with the driver:

  1. Install the driver:
    1. After downloading the product, extract the contents of the product file.
    2. From the installer directory, run the installer's binary file to start the installer. The file for the installer program takes the following form:
      PROGRESS_DATADIRECT_ODBC_nn_LINUX_xx_INSTALL.bin
    3. Follow the prompts to complete installation.

    The installer program supports multiple installation methods, including command-line and silent installations. For detailed instructions, refer to the Progress DataDirect for ODBC Drivers Installation Guide.

  2. Configure the environment variables:
    1. Check your permissions. You must log in as a user with full r/w/x permissions recursively on the entire product installation directory.
    2. Run one of the following product setup scripts from the installation directory to set variables: odbc.sh or odbc.csh. For Korn, Bourne, and equivalent shells, execute odbc.sh. For a C shell, execute odbc.csh. Executing the setup script:
      • Sets the ODBCINI environment variable to point to the path from the root directory to the system information file where your data source resides. For details, see "ODBCINI."
      • Sets the library path environment variable for your Linux operating system, LD_LIBRARY_PATH, to include the directory containing your JVM’s libjvm.so file. For details, see "Library search path."
  3. Configure the driver using one of the following methods:
    • odbc.ini file: You can begin using the driver immediately by editing the odbc.ini file in the installation directory with a text editor. The following demonstrates a data source definition with the minimal options used to authenticate using OAuth 2.0 refresh token grant flow. 
      [ODBC Data Sources]
Google Analytics 4=DataDirect 8.0 Google Analytics 4
      [Google Analytics 4]
Driver=<install_dir>/lib/xxgoogleanalytics428.yy
...
Description=My Google Analytics 4 Data Source
...
AddTables='{myTableDefinitionString}'
...
ClientID=ab123c45-def6-7g89-gh1i-m2345no67891.apps.googleusercontent.com
...
ClientSecret=12a3=bCD/EfGh4Ijk+Lm5P67qR8s=//TuV+WXy1Zabcd
...
RefreshToken=1//12a3=bCD/EfGh4Ijk+Lgd8g-44tk3c527831
...
      See Configuration through the system information (odbc.ini) file for more information.
      Note: The ClientID, ClientSecret, and RefreshToken options are not required to be stored in the data source. They can also be sent separately by the application using the SQLConnect ODBC API. For SQLDriverConnect and SQLBrowseConnect, they will need to be specified in the data source or connection string.
    • Connection string: The driver also supports using connection strings for DSN (data source name), File DSN, or DSN-less connections. See Using a connection string, DSN-less connections, for more information. For examples, see Connection string examples.
    Note: For most connections, specifying the minimum required connection options is sufficient to begin accessing data; however, you can provide values for optional connection options to use additional supported features and improve performance.
  4. Set the values for any additional options that you want to configure. For additional information on optional features and functionality, see the following resources:
    • Connection string examples provides connection string examples that can be used to configure common functionality and features. You can modify and combine these examples to create a string that best suites your environment.
      Note: The options and values described in "Connection string examples" apply to all configuration methods.
    • Connection option descriptions provides a complete list of supported options by functionality.
    • Performance Considerations describes connection options that affect performance, along with recommended settings.
  5. Connect to your instance and begin accessing data with your applications, BI tools, database tools, and more. To help you get started, the following resources guide you through accessing data with some common tools:
    • Example Application: The example application is a command-line tool that allows you to test connect, execute SQL statements, and practice using the ODBC API in environments that do not support GUIs.
    • Supported SQL statements and extensions: This section describes the syntax used for SQL statements supported by the driver. You can modify and use the provided examples for your application or tool.

This completes the deployment of the driver.