Creating a response file using the installer in console mode
- Last Updated: August 29, 2025
- 6 minute read
- Hybrid Data Pipeline
- Version 5.0
- Documentation
- Copy the product file to a temporary directory.
- Install a compatible JVM and define it on your system path. See Product requirements for details on JVM prerequisites.
After copying the downloaded product file to a temporary directory, take the following steps to generate a response file using the installer in console mode. Note that an installation of the server occurs when using the installer to generate a response file.
-
From a command-line prompt, navigate to the directory where
you saved the product file. Alternatively, place the product file directory on
your path before proceeding to the next step.
The product file has the format PROGRESS_DATADIRECT_HDP_SERVER_nn_LINUX_64_INSTALL.bin, where nn is the version of the product.
-
Make the file an executable using the chmod command. Then, press ENTER. For example:
chmod +x ./PROGRESS_DATADIRECT_HDP_SERVER_nn_LINUX_64_INSTALL.bin
-
At a command-line prompt, type the following command where
response_file is the path and file name
of the response file you want to create. You must specify an absolute
path.
./PROGRESS_DATADIRECT_HDP_SERVER_nn_LINUX_64_INSTALL.bin -i console -r response_file
The following example creates a response file named pipeline.response in the /home/users/johndoe directory.
PROGRESS_DATADIRECT_HDP_SERVER_nn_LINUX_64_INSTALL.bin -i console -r /home/users/johndoe/pipeline.response
-
You are prompted for the installation directory.
- Press ENTER to accept the default installation directory.
- Type the absolute path to the installation directory for the installation, and press ENTER.
The default installation directory is:
/opt/Progress/DataDirect/Hybrid_Data_Pipeline/Hybrid_Server
If you do not have /opt directory permissions, the installer program installs the drivers to your home directory by default. For example:
/home/users/<username>/Progress/DataDirect/Hybrid_Data_Pipeline/Hybrid_Server
-
Choose the JVM you want to use for the runtime operation of
the server.
Note: See Product requirements for details on JVM prerequisites.
- Type 1 to use the JVM that was used to run the installer.
- Type 2 to enter your preferred JVM. Then enter the full path to the Java executable.
-
Choose whether you want to install an evaluation or licensed
version of the product. Licensed installations require a valid License
Key.
- Evaluation. Type 1 to proceed with installing an evaluation version of the product (functional for 30 days). Then, press ENTER.
- Licensed. Type 2 if you purchased a licensed version of the product. Then, press ENTER. Type the license key, including any dashes, and then press ENTER.
-
Accept or enter the fully qualified hostname for your Progress DataDirect Hybrid Data Pipeline Server. By default,
the installer suggests the name of the current machine. Then, press ENTER.
Note the following important information. Then, click ENTER to continue.
- If you enter a hostname different than the hostname of the current machine, the installer will fail to validate the hostname. You are then prompted to reenter the hostname or skip validation. If you are planning on using the response file to install the product on a different machine, you should opt to skip validation.
- Before using the response file to install the product on another
machine, the response file must have the
SKIP_HOSTNAME_VALIDATIONandSKIP_PORT_VALIDATIONvalidation properties set to1. For example:SKIP_HOSTNAME_VALIDATION=true SKIP_PORT_VALIDATION=true - Running an installation in silent mode with a response file containing these settings allows the silent installation to continue even if hostname or port validation fail. When the validation fails during the silent installation process, the installer generates the file SilentInstallInfo.log in the user's home directory but completes a full installation.
Note: For non-load balancer deployments where the server is receiving queries directly, the hostname should be tied to the DNS for public access. This allows you to update IP addresses in the DNS without having to run an upgrade installation to reconfigure your deployment. -
Select your installation type.
- To accept the default values for the remaining options, type 1 and press ENTER for a typical installation. Continue at Step 9.
- To customize installation options, type 2 and press ENTER. Then, skip to Step 10.
You will need to complete a custom installation if you plan to do any of the following:
- Specify the key location. The key location serves as a location for shared files used in the installation and operation of the server. The key location should be secured on a system separate from the system that stores encrypted data, or encrypts or decrypts data.
- Enable FIPS
- Use a load balancer
- Change an SSL configuration
- Use MySQL Community Edition as a data store
- Store system information in an external MySQL Community Edition, Oracle, or SQL Server database
- Specify non-default values for ports used by the Hybrid Data Pipeline service
- Use On-Premises Connectors for secure access to on-premises data sources from the cloud
-
Specify passwords for the d2cadmin
and d2cuser user accounts.
- For standard installation, specify the password for each account. Then, continue at Step 15 in "Non-load balancer installation (console mode)."
- For an installation using environment variables, specify a dummy password for each account. Then, continue at Step 15 in "Non-load balancer installation (console mode)."
Important: Passwords for the d2cadmin and d2cuser user accounts are not persisted in the response file. These values must be specified in the response file with theD2C_ADMIN_PASSWORD_CONSOLEandD2C_USER_PASSWORD_CONSOLEoptions before running a silent install (see Editing a console generated installation response file). Best practices recommend that you follow the Hybrid Data Pipeline default password policy when specifying these account passwords. When initially logging in to the Web UI or using the API, you must authenticate as one of these users. -
Specify the key location. The key location serves as a
location for shared files used in the installation and operation of the server.
The key location should be secured on a system separate from the system that
stores encrypted data, or encrypts or decrypts data.
- Type 1 if you want to specify a location other than the default. You must specify a location for a load balancer installation. Press ENTER and continue to the next step.
- Type 2 and press ENTER if you want to use the default location for a non-load balancer installation. This option cannot be used for a load balancer installation. The default location is install_dir/ddcloud/keystore.
-
Specify passwords for the d2cadmin and
d2cuser user accounts.
- For standard installation, specify the password for each account. Then, continue to the next step.
- For an installation using environment variables, specify a dummy password for each account. Then, continue to the next step.
Important: Passwords for the d2cadmin and d2cuser user accounts are not persisted in the response file. These values must be specified in the response file with theD2C_ADMIN_PASSWORD_CONSOLEandD2C_USER_PASSWORD_CONSOLEoptions before running a silent install (see Editing a console generated installation response file). Best practices recommend that you follow the Hybrid Data Pipeline default password policy when specifying these account passwords. When initially logging in to the Web UI or using the API, you must authenticate as one of these users. -
Specify whether you want to enable FIPS on the Hybrid Data Pipeline server.
Important: To implement FIPS, your hardware must support secure random, or you must have a secure random daemon installed.
- Type 1 if you want to enable FIPS. Press ENTER and continue to the next step.
- Type 2 and press ENTER if you want to use the default setting which is FIPS disabled.
-
Specify if you are planning to use a load balancer.
- Type 1 if you do not plan to use a load balancer. For next steps, proceed to Creating a response file for a non-load balancer installation (console mode).
- Type 2 if you plan to use a network load balancer such as HAProxy. For next steps, proceed to Creating a response file for a load balancer installation (console mode).
- Type 3 if you plan to use a cloud load balancer such as AWS Application Load Balancer. For next steps, proceed to Creating a response file for a load balancer installation (console mode).