Before you begin:
  • 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 GUI mode. Note that an installation of the server occurs when using the installer to generate a response file.

Important: After generating a response file, you must edit the response file according to the guidelines in Editing a GUI generated installation response file.
  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:

    chmod +x ./PROGRESS_DATADIRECT_HDP_SERVER_nn_LINUX_64_INSTALL.bin

  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.

    ./PROGRESS_DATADIRECT_HDP_SERVER_nn_LINUX_64_INSTALL.bin -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 -r /home/users/johndoe/pipeline.response

  4. Choose the destination directory for the installation. Click Next to accept the default installation directory, or select Choose... to browse to a different directory, then click Next.

    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

  5. Choose the JVM you want to use for the runtime operation of the server.
    Note: By default, the JVM used to run the installer is selected. However, you may choose a different JVM by clicking Choose Java Executable and navigating to the Java executable of your preferred JVM. See Product requirements for details on JVM prerequisites.
  6. Choose whether you want to install an evaluation or licensed version of the product. Licensed installations require a valid License Key.
    • Evaluation. Select this option to install an evaluation version that is fully functional for 30 days. Click Next to continue with the installation.
    • Licensed. Select this option if you purchased a licensed version of the product. Type the license key, including any dashes, and then click Next to continue with the installation.
  7. Accept or enter the fully qualified hostname of the machine that will host the Hybrid Data Pipeline server. By default, the installer suggests the name of the current machine.

    Note the following important information. Then, click Next 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 properties set to true. 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.
  8. Select the installation type.
    • To accept the default values for all remaining options, select Typical (use existing settings) and click Next. Continue at Step 9.
    • To modify installation options, select Custom (choose configuration values) and click Next. 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
  9. Specify passwords for the d2cadmin and d2cuser user accounts.
    • For standard installation, specify the password for each account. Then, continue at Step 14 in "Creating a response file for a non-load balancer installation (GUI mode)".
    • For an installation using environment variables, specify a dummy password for each account. Then, continue at Step 14 in "Creating a response file for a non-load balancer installation (GUI 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 and D2C_USER_PASSWORD options before running a silent install (see Editing a GUI 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.
    • Select Use default location 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.
    • Select Specify location if you want to specify a location other than the default. You must specify a location for a load balancer installation. Click Next and continue to the next step.
  11. 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 the D2C_ADMIN_PASSWORD and D2C_USER_PASSWORD options before running a silent install (see Editing a GUI 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.
  12. Select 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.
  13. Specify if you are planning to use a load balancer.