Creating a response file using the installer in console mode
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.
Important: After generating a response file, you must edit the response file according to the guidelines in Editing a console generated installation response file. In all scenarios, the response file must be edited to include passwords for the d2cadmin and d2cuser user accounts. Depending on your environment, the response file may require additional modification.
1. 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.
2. Make the file an executable using the chmod command. Then, press ENTER. For example:
3. 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.
4. The License Agreement appears. Press ENTER multiple times to advance through the license agreement. Make sure that you read and understand the license agreement.
To accept the terms in the License Agreement and continue with the installation, type Y.
To end the installation, type N and press ENTER.
Note: You can exit the installation program at any time by typing Quit.
5. 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.
If the directory contains an existing Hybrid Data Pipeline deployment, you are prompted to specify a different directory or upgrade the existing installation.
6. 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.
7. 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_VALIDATION and SKIP_PORT_VALIDATION validation properties set to 1. For example:
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.
8. 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.
Change the Java configuration to use an external JRE
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
9. Specify passwords for the d2cadmin and d2cuser user accounts. Continue at Step 15 in "Standalone 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 the D2C_ADMIN_PASSWORD_CONSOLE and D2C_USER_PASSWORD_CONSOLE options 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.
10. 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 standalone installation. This option cannot be used for a load balancer installation. The default location is install_dir/ddcloud/keystore. Proceed to Creating a response file for a standalone installation (console mode).
11. Specify passwords for the d2cadmin and d2cuser user accounts.
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.
To accept the terms in the License Agreement and continue with the installation, type Y.
