A silent installation configuration file is a text file that you create, for example, silent.config. This file must contain the following arguments:

USER_INSTALL_DIR=installation directory
EVAL=0
LICENSED=1
BRANDED_OEM=1
UNBRANDED_OEM=0
CONFLICT_DRIVERS=PROGRESS_DATADIRECT_ODBC_datasource1_n.n.n_platform_nn_INSTALL.iam.zip,
PROGRESS_DATADIRECT_ODBC_datasource2_n.n.n_platform_nn_INSTALL.iam.zip
KEYLIST=key value 
USERNAME=user name 
COMPANYNAME=company name
SERIALNUMBER=serial number value 
PREFIX=xx
PRODUCTNAME=product_name
PASSWORD=password
MESSAGEPREFIX=message_prefix
BRANDINGSUFFIX=nn
CROSS_BRAND=platform

## Optionally, overwrite a specific file
-fileOverwrite_filename=(Yes | No)
Table 1.
Keyword Description
USER_INSTALL_DIR Specifies the full path to the directory where you want to install the drivers. This cannot be the same directory as the temporary installation directory.
Note: For cross-platform branding, you should specify a unique 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 in the configuration file or by overriding the install directory when performing the silent installation from a command-line. See "Performing a silent installation" for details.
EVAL Specifies whether this is an evaluation install. Type 0 to specify a licensed installation. Note that the silent installation method does not support evaluation installs.
LICENSED Specifies whether this is a licensed install. Type 1 to specify a licensed installation. Note that the silent installation method does not support evaluation installs.
BRANDED_OEM Specifies whether branded drivers are installed. Type 1 for branded a installation or type 0 for an unbranded installation. The type of installation specified for this keyword much match that of the UNBRANDED_OEM keyword.
Note: If you specify a branded installation, the PREFIX, PRODUCTNAME, PASSWORD, MESSAGEPREFIX, BRANDINGSUFFIX keywords are enabled.
UNBRANDED_OEM Specifies whether unbranded drivers are installed. Type 1 for an unbranded installation or type 0 for a branded installation. The type of installation specified for this keyword much match that of the BRANDED_OEM keyword.
Note: If you specify an unbranded installation, the PREFIX, PRODUCTNAME, PASSWORD, MESSAGEPREFIX, BRANDINGSUFFIX keywords are ignored.
CONFLICT_DRIVERS
Note: This argument is only supported by the Unified Installer.
Specifies which version of the driver to install if multiple versions of the driver are available. Type the a comma-separated list of the names of the module zip files for versions of the drivers that you want to install. For example, the following is the module file for the 8.0.1 version of the 64-bit MongoDB driver:

PROGRESS_DATADIRECT_ODBC_MONGODB_8.0.1_LINUX_64_INSTALL.iam.zip

Note: The module zip files for the drivers are stored in the DriverModule folder of the installer program directory.
KEYLIST Specifies your product license key, including dashes. If specifying multiple keys, separate them using a space. For example: 123-456-7890 234-567-8901 345-678-9012.
USERNAME Specifies your name.
COMPANYNAME Specifies your company name. The company name can include spaces.
SERIALNUMBER Specifies the serial number provided for your purchased product.
PREFIX Specifies the 2-character file prefix you registered through the Partners section of the Progress DataDirect Web site. This prefix is added to the driver and license file names. For example, if you brand the SAP ASE driver with the prefix gf, the Branding Tool renames this file to gfasenn.so.
PRODUCTNAME Specifies your product name. The product name is case-sensitive and can contain up to 63 characters.
PASSWORD Specifies the password you registered through the Partners section of the Progress DataDirect Web site. The password is case-sensitive. This password is locked into the branded drivers to prevent unauthorized applications from using the branded drivers.
MESSAGEPREFIX Specifies the message prefix for the branded drivers (maximum of 32 characters). After branding, driver error messages are displayed with this prefix. For example, if xyzcompany is your message prefix, the driver error message:

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

becomes:

[xyzcompany][Oracle 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.
BRANDINGSUFFIX Specifies an optional 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 SAP ASE Wire Protocol driver with the prefix gf and the branding suffix 17, the files are renamed as gfase17.so.
CROSS_BRAND In 64-bit Linux environments, specifies which AIX, HP-UX, Linux, or Solaris version of the product is installed when performing cross-platform branding. This is useful when you are building your application for multiple platforms out of the Linux environment. Valid values are aix32, aix64, hpia32, hpia64, hprisc32, linux32, linux64, solaris32 (SPARC), solaris64 (SPARC), solarisx32, or solarisx64.
Note: For cross-platform branding, you can override the value of the CROSS_BRAND keyword when performing the silent installation from a command-line. This provides a method to perform installations for multiple platforms without having to edit the configuration file. See "Performing a silent installation" and "Cross-platform branding" for details.
-fileOverwrite_filename Indicates whether the silent installer should overwrite a specific file (optional). For example, if you are overwriting an existing ODBC installation and want to update the Progress DataDirect for ODBC uninstaller (/home/john/Progress/uninstall_ODBC_80.lax), then include the following line in the response file:

-fileOverwrite_/home/john/Progress/uninstall_ODBC_80.lax=Yes