This section describes the general tasks for installation. Later sections in this chapter describe each of these tasks in more detail for specific client platforms.

To load the driver files, create an installation program that will:

  1. Copy the necessary files from the installation media to the client machine. The files that must be installed on each client computer are the license file, the ODBC driver files, and supporting files (see the appropriate chapter). For the names of specific files that you must distribute, and files that you may distribute, see the appropriate chapters.
    Before your installation program copies a file to a client machine, ensure that it:
    1. Checks whether the file already exists and, if so, compares the dates of both files.
    2. Asks users if they want to overwrite an existing file with a newer version.
  2. For all drivers: Add the necessary entries to the corresponding sections of the system information files and environment variables. The entries you must make are platform-dependent. All Progress DataDirect drivers conform to the ODBC standard, and you must make the appropriate configuration entries based on this standard.
  3. For the Aha!, Apache Cassandra, Autonomous REST Connector, GitHub, Google Analytics 4, Google BigQuery, HubSpot, Microsoft Dynamics 365, Microsoft SharePoint, MongoDB, Oracle Service Cloud, Salesforce, SAP S/4 HANA, Snowflake, and TeamCity drivers: The jar file (for example, mongodb.jar) installed with the driver must be added to the runtime environment's CLASSPATH using one of the following methods:
    • Install the file in a java\lib directory that is on the same directory level as the folder containing the driver files. By default, the driver will look for the jar file in the java\lib directory that is up one level from its current location.
    • Your installer specifies the location of the jar file in the JarFile key in the [ODBCINST.INI] section of the registry. The driver uses this value before looking for the jar file in the default location. For details, see "Adding entries to registries."
    • Specify the fully qualified path to the jar file using the JVMClasspath connection option. This value overrides both the default driver behavior and the value of the JarFile key. For details, see "Adding entries to the [ODBC.INI] section of the registry."
  4. (Optional) Provide a way for the user to set driver configuration parameters for each installed driver.