Creating a Response File Using the GUI Installer
- Last Updated: June 14, 2021
- 4 minute read
Take the following steps to create a response file using the GUI installer.
-
At a command prompt, change to the directory containing the
temporary installer and supporting zip files.
Important: The installer directory must include the supporting installation zip files.
-
At a command prompt, type the appropriate command.
Important: If running the Java installer on Windows, you must either select a non-system directory as the installation directory or turn off User Account Controls.
- Java installer: java -jar PROGRESS_DATADIRECT_JDBC_INSTALL.jar -r response_file
- Windows installer: PROGRESS_DATADIRECT_JDBC_INSTALL.exe -r response_file
where response_file is the path and file name of the response file you want to create. You can specify an absolute or relative path. If the path is not specified, the specified file is created in the current working directory.
Java installer on UNIX/Linux
This example creates a response file named
installer.propertiesin the /install directory, which is relative to the current working directory.java -jar PROGRESS_DATADIRECT_JDBC_INSTALL.jar -r /install/installer.properties
Windows installer on Windows
This example creates a response file named
installer.propertiesin the C:\temp directory.PROGRESS_DATADIRECT_JDBC_INSTALL.exe -r C:\temp\installer.properties
- The Introduction window appears. Click Next.
- The License Agreement window appears. Make sure that you read and understand the license agreement. To continue with the installation, select the I accept the terms in the License Agreement option; then, click Next.
- The Install Directory window appears. In the Where Would You Like to Install? field, type the path, including the drive letter, of the product installation directory or click the Choose button to browse to and select an installation directory. Verify the installation directory. Click Next to continue.
- Select the OEM or Licensed installation option. Then, click Next to enter your product licensing information.
-
Type the IPE key (or Control Number) that was provided by
Progress DataDirect in the IPE Key field, and click the Validate button. The drivers that you purchased
appear in the Drivers box. Select the drivers you want to install, and then
click Next.
- If you are installing a 5.1 version of the product, skip to Step 10.
- If you are installing a 6.0 version of the product, proceed to the next step.
-
The OEM Installation Type window appears.
- Select Branded Installation to specify a branded installation, and proceed to Step 10.
- Select Unbranded Installation to specify an unbranded installation, and proceed to the next step.
-
Enter the information in the fields provided.
- Type your name and company name into the corresponding fields.
- Type the serial number that was provided by Progress DataDirect.
- Verify that the I want to participate box is selected to allow the installer program to gather data for the Installer Customer Experience Improvement Program. Information collected for the program is used to improve our products by identifying trends or issues that impact the user experience. For details, refer to the Progress Privacy Policy.
- Click Next and skip to Step 11.
-
Enter your product branding information as described in the following
section.

Provide the following information:
Serial Number: Type the Serial Number provided by Progress DataDirect.
User Name: Type your name.
Company Name: Type the name of the company which has purchased the OEM license.
File Prefix: Type thecharacter file prefix (maximum of 2 characters) you registered on the Progress DataDirect OEM Partner website. This prefix is added to DataDirect file names. For example, ifdxis your file prefix for the MongoDB driver,mongodb.jarbecomesdxmongodb.jar.Note: The valueddis a reserved file prefix. Specifying this value returns an error.Package Prefix: Type a package prefix for the branded driver (maximum of 64 characters). To avoid package name conflicts, the package prefix should adhere to the package naming conventions defined in the Java Language Specification. The package prefix replaces the DataDirect prefix of
com.ddtekin all the classes within the driver jar file when you brand a driver. For example, ifcom.xyzcompany.xyzdivisionis your package prefix for the MongoDB driver, the MongoDB driver class:com.ddtek.jdbc.mongodb.MongoDBDriverbecomes:
com.xyzcompany.xyzdivision.jdbc.mongodb.MongoDBDriverNote: The valuecom.ddtekis a reserved package prefix. Specifyingcom.ddtekas part of this value returns an error.Subprotocol Prefix: Type the vendor subprotocol prefix. Progress DataDirect drivers are registered with a URL subprotocol of the form
datadirect:drivername, for example,datadirect:mongodb. To replacedatadirectin the subprotocol of a branded driver with your company name, type a prefix (maximum of 32 characters) in this field. For example, ifxyzcompanyis your subprotocol prefix for the MongoDB driver, the URL:jdbc:datadirect:mongodb://server1:27017becomes:
jdbc:xyzcompany:mongodb://server1:27017Note: Contact Oracle to register JDBC subprotocol names.Note: The subprotocol cannot start withProgress DataDirector containdatadirect. Specifying either of these reserved values returns an error.Message Prefix: Type a message prefix for the branded drivers (maximum of 32 characters). After branding, driver error messages are displayed with this prefix. For example, if
xyzcompanyis your message prefix for the MongoDB driver, the driver error message:[DataDirect][MongoDB JDBC Driver] Object has been closedbecomes:
[xyzcompany][MongoDB JDBC Driver] Object has been closedNote: The message prefix cannot start withProgress DataDirector containdatadirect. Specifying either of these reserved values returns an error.Password: Type the password (maximum of 128 characters) you registered on the Progress DataDirect OEM Partner website. The password is case-sensitive. This password is locked into the branded drivers to prevent unauthorized applications from using the branded drivers.
- The Pre-Installation Summary window appears. Review the installation information. Click Previous to revise selections; or click Install to begin the installation.
- When the installation finishes, the Install Complete window appears. Click Done to exit the installer program
Refer to the installation log file for a record of any problems that may have occurred during the installation. See Installation Log File for details.
See Performing the Silent Installation for instructions on running the response file.