The installer enables you to brand the drivers. After verifying your product key, you will be prompted for the company name, branding password, and other information.

To install the Progress DataDirect Drivers for ODBC from downloaded files:

  1. At a command prompt, switch the directory containing the installer files; then, type the command:
    • Standard branding:

      ./installer_filename -r  configuration_file - i console

      where:

      installer_filename
      is the full name of the installer's binary file you extracted in Step 4 of "Branding the drivers on UNIX and Linux."
      configuration_file
      is the absolute path and file name of the configuration file you want to create. For example, /opt/tmp/silent.config.
    • Cross-platform branding:

      ./PROGRESS_DATADIRECT_ODBC_8.0_LINUX_64_INSTALL.bin -r configuration_file -i console -DCROSS_BRAND=platform

      where:
      configuration_file
      is the absolute path and file name of the configuration file you want to create. For example, /opt/tmp/silent.config.
      platform
      is the platform and bitness of the product that you want to install. Valid values are aix32, aix64, hpia32, hpia64, hprisc32, hprisc64, linux32, linux64, linuxia64, linuxppc32, linuxppc64, linuxzos64, power864, solaris32 (SPARC), solaris64 (SPARC), solarisx32, or solarisx64. You can override this value when performing the silent installation. For details, see "Performing a silent installation."
      Note: Cross-platform branding allows you to install branded versions of the product for AIX, HP-UX, Linux, and Solaris platforms in the 64-bit Linux environment. This feature is typically used to reduce the effort of installing and branding drivers for multiple platforms by running platform-specific installers on a single operating system (Linux x64) and then using the installed binaries in the building/packaging of your application. Only the Unified Installer supports cross-platform branding. For details, see "Cross-platform branding."
  2. The Introduction step appears. Press ENTER.
  3. The product license agreement appears. Press ENTER to page to the end of the agreement. At the end, you are asked to accept the agreement:
    • Enter Y to accept the license agreement and continue with the installation.
    • Enter anything other than N to abort the installation.
    Note: You can exit the installer program at any time by typing quit or return to the previous step by typing back.
  4. You are prompted to enter the absolute path to the installation directory. Proceed as follows:
    • If you are using a single-driver installer, proceed to the next step.
    • If you are using the Unified Installer, skip to Step 6.
    Note: For cross-platform branding, you should specify a unique the location of the installation directory for each platform; otherwise, the installer program will overwrite the preceding installation. You can do this by changing this value or by overriding the install directory when performing the silent installation. See "Performing a silent installation" for details.
  5. You are prompted for the type of installation to perform. Enter 2.
  6. You are prompted to enter the Control # that was provided by Progress DataDirect. Type the Control # and then press ENTER. Proceed as follows:
    • If you are using a single-driver installer, skip to Step 8.
    • If you are using a Unified Installer, proceed to the next step.
  7. You are prompted to select the version of the driver you want to install. The installer program only allows you to install one version of each driver. Type the number that corresponds to the version of the driver you want to install. Press ENTER to proceed.
  8. The installer prompts you for product registration information. Enter your name, your company name, and the serial number provided by Progress DataDirect; then, press ENTER.
  9. You are prompted to specify a branded or unbranded type of installation.
    • Type 1 to specify a branded installation; then, proceed to the next step.
    • Type 2 to specify an unbranded installation. This option allows you to install the standard, unbranded, version of the product with an OEM license. Skip to Step 11.
  10. You are prompted to enter the branding information for your driver:

    New Prefix specifies the 2-character prefix that you registered with Progress DataDirect to encode the driver and license files. See "Before branding the drivers" for details. When entering the 2-character prefix, be sure to enter it as uppercase if using letters. For example, if you brand the MongoDB driver for Linux with the prefix gf, the installer renames this file to gfmongonn.so.

    Warning: Do not make up a prefix. Register for it through the Progress DataDirect Web site. Registering a prefix through the Web site guarantees that each OEM customer has a unique 2-character prefix. A unique prefix prevents shared library conflicts with other embedded drivers that may be on a user’s system when your application is running.
    Message Prefix specifies an error message prefix for the branded drivers. The restrictions are:
    • The name is case-sensitive.
    • A maximum of 30 characters is allowed.

    After branding, driver error messages are displayed with this prefix. For example, if xyzcompany is your message prefix, the driver error message:

    [DataDirect][MongoDB ODBC Driver] Object has been closed

    becomes:

    [xyzcompany][MongoDB ODBC Driver] Object has been closed

    Note: To continue using the DataDirect message prefix, specify a value of DataDirect. Be aware that when DataDirect is your message prefix, the installer program uses Progress Software Corporation as the company name, regardless of the value specified in the Company Name field.
    Product Name specifies the name of your product. The restrictions are:
    • The field is case-sensitive.
    • A maximum of 63 characters is allowed.

    Branding Suffix optionally specifies a branding suffix for the branded drivers. The suffix can consist of a maximum of two numeric characters (0 to 9).

    After branding, the driver file names are displayed with this suffix. For example, if you brand the Amazon Redshift Wire Protocol driver with the prefix gf and the branding suffix 17, the files are renamed as gfrsft17.so.

    New Password specifies the password that you registered with Progress DataDirect for invoking your driver files after you brand them. See "Before branding the drivers" for details. You must use this password in your applications to invoke the drivers. The password protects your branded drivers from being used by other applications.
    Important: For security purposes, the value of the password prompt is not populated to the response file by the installer. You will need also need to manually add the password value to the generated response file with a text editor before executing your silent installation. The password entry takes the following form: PASSWORD=password. For more information on manually editing the response file, see Creating a configuration file using the GUI.
  11. The Pre-Installation Summary step provides the opportunity for you to review the information you have entered, and you are prompted to accept or change the information:
    • Press ENTER to accept the information and begin the installation.
    • To change the information, type back and then press ENTER. You are prompted for the information again.
  12. After completion of the installation, a message appears indicating that you have installed the software successfully. Press ENTER to close the installer.
    Important: Your product license may limit the number of CPUs that can exist on the machine on which the product is installed. If you need to upgrade your product license, contact your Progress DataDirect sales representative.
    Note: For TLS/SSL-enabled drivers: Some releases of the product install multiple versions of the OpenSSL library file. By default, the installer brands the most secure installed version; however, you may want to brand a different version of the library based on the needs of your application. For details, see "Branding OpenSSL library files on UNIX and Linux."
See "Performing a silent installation" for instructions on running the configuration file.