Take the following steps to configure system database failover during initial installation of the service.

  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. Run the executable.
    • Console mode

      ./PROGRESS_DATADIRECT_HDP_SERVER_nn_LINUX_64_INSTALL.bin -i console

    • GUI mode

      ./PROGRESS_DATADIRECT_HDP_SERVER_nn_LINUX_64_INSTALL.bin

      Note: If the installer cannot continue with a GUI installation, a message is displayed and the installation continues in console mode
  4. Specify an installation directory.
  5. Provide the hostname of the machine on which you are installing the Hybrid Data Pipeline server.
  6. Select the Custom installation type.
  7. Provide the following information as prompted by the installation program.
    • Passwords for default accounts
    • Key location
    • SSL certificate information
  8. Select the type of external system database you want to use to store system information.
    Note: Failover configuration is supported for the Oracle, SQL Server, and PostgreSQL databases.
    • Select Oracle, and continue at Step 9.
    • Select MSSQLServer, and continue at Step 10.
    • Select PostgreSQL, and continue at Step 11.
  9. Provide the Oracle connection information.
    1. Provide the name of the host.
    2. Provide the port number.
    3. Provide the required connection type information.
      • If you connect using the Oracle System Identifier (SID), enter the SID.
      • If you connect using the Service Name, enter the database service name that specifies the database that is used for the connection. The service name is a string that is the global database name—a name that typically comprises the database name and domain name.
    4. When prompted for Advanced Options, specify alternate servers with the AlternateServers connection property in a connection string. For example: 
      AlternateServers=(server2:1521;SID=ORCL2,server3:1521;SID=ORCL3)

      See The AlternateServers connection property for further details.

      Important: User credentials and schema details for alternate servers should be same as those of the primary server. In addition, all alternate servers should be regularly synced with the primary database server.
    5. Optionally, specify additional connection parameters in the Advanced Options connection string. Settings should be entered as a semicolon-separated list of parameter=value pairs. For example, you may enter to following options to configure SSL: 
      encryptionMethod=SSL;trustStore=/common/Oracle/trustStore.jks;
trustStorePassword=secret
    6. Continue at Step 12
  10. Provide the SQL Server connection information.
    1. Type the name of the host.
    2. Type the port number.
    3. Type the database name.
    4. Type the name of the schema.
    5. When prompted for Advanced Options, specify alternate servers with the AlternateServers connection property in a connection string. For example: 
      AlternateServers=(server2:1433;ServerName=sqlserv2,server3:1433;ServerName=sqlserv3)

      See The AlternateServers connection property for further details.

      Important: User credentials and schema details for alternate servers should be same as those of the primary server. In addition, all alternate servers should be regularly synced with the primary database server.
    6. Optionally, specify additional connection parameters in the Advanced Options connection string. Settings should be entered as a semicolon-separated list of parameter=value pairs.
    7. Continue at Step 12
  11. Provide the PostgreSQL connection information.
    1. Type the name of the host.
    2. Type the port number.
    3. Type the database name.
    4. Type the name of the schema.
    5. When prompted for Advanced Options, specify alternate servers with the AlternateServers connection property in a connection string. For example: 
      AlternateServers=(server2:5432;ServerName=pgserv2,server3:5432;ServerName=pgserv3)

      See The AlternateServers connection property for further details.

      Important: User credentials and schema details for alternate servers should be same as those of the primary server. In addition, all alternate servers should be regularly synced with the primary database server.
    6. Optionally, specify additional connection parameters in the Advanced Options connection string. Settings should be entered as a semicolon-separated list of parameter=value pairs.
    7. Continue at Step 12
  12. Provide the database credential information for a user with administrator privileges and for a user without administrator privileges.
    Note: Administrator credentials are only required at install time to create the database schema. Administrator credentials are not used by the product at run time.
    1. Type the administrator user name. The administrator user must have certain privileges that are specific to the database vendor. For a list of required privileges, refer to External system databases in the Deployment Guide.
    2. You are prompted to provide the Admin Password. Type the password for a administrator account for the external database.
    3. You are prompted to provide the username for a user who does not have administrator privileges. Type a user name. The standard user must have certain privileges that are specific to the database vendor. For a list of required privileges, refer to External system databases in the Deployment Guide.
    4. You are prompted to provide the user password. Type the user password.
  13. Specify port numbers and On-Premises Connection configuration information as prompted.
  14. Review the installation summary, and proceed with the installation.
  15. Perform installations on any additional nodes supporting the service.

Results:

The Hybrid Data Pipeline service has been deployed with a system database configured to failover to alternate servers should the primary server hosting the system database become unavailable.