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

## Use the hash mark for comments in the file 

USER_INSTALL_DIR=install_dir 
EVAL=0
LICENSED=1
BRANDED_OEM=(0 | 1)
UNBRANDED_OEM=(0 | 1)
INSTALL_OPTIONS_CREATE=(0 | 1)
KEYLIST=yyyyyyyyyy xxxxxxxxxx zzzzzzzzzz
CONFLICT_DRIVERS=PROGRESS_DATADIRECT_ODBC_datasource1_n.n.n_WIN_nn_INSTALL.iam.zip,
                 PROGRESS_DATADIRECT_ODBC_datasource2_n.n.n_WIN_nn_INSTALL.iam.zip
USERNAME=user_name 
COMPANYNAME=company_name 
SERIALNUMBER=xxxxxxxx
PREFIX=xx
PRODUCTNAME="product_name"
PASSWORD=password
MESSAGEPREFIX=message_prefix
BRANDINGSUFFIX=nn

## Optionally, overwrite a specific file
-fileOverwrite_filename=(Yes | No)
Table 1. Response File Keywords
Keyword Description
USER_INSTALL_DIR Specifies the product installation directory. Notice that the colon (:) and backslash (\) special characters must be escaped with a backslash. For example:

C:\\Program Files\\Progress\\DataDirect\\ODBC_80
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.
INSTALL_OPTIONS_CREATE Specifies whether to create default data sources. Type 1 if you want to create default data sources or 0 if you do not want to create default data sources.
CONFLICT_DRIVERS
Note: This argument is only supported by the Unified Installer.
Specifies which version of the driver to install, if more than one is available. Type 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_WIN_64_INSTALL.iam.zip

Note: The module zip files for the drivers are stored in the DriverModule folder of the installer program directory.
KEYLIST Is 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 the user name that will be written to the license file. For example, type Sales Team as the user name.
COMPANYNAME Specifies the company name that will be written to the license file. For example, type MyCompany.
SERIALNUMBER Specifies the product serial number that will be written to the license file.
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.dll.
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.dll.
-fileOverwrite_filename indicates whether the silent installer should overwite a specific file (optional). For example, if you are overwriting an existing ODBC installation and do not want to update the Progress DataDirect ODBC tracing library (C:\Windows\system32\ivtrc28.dll), then include the following line in the response file:
-fileOverwrite_C\:\\Windows\\system32\\ivtrc28.dll=No
Notice that the colon (:) and backslash (\) special characters must be delimited with a backslash.

See "Performing the silent installation" for instructions on running the response file.