1. Enter the hostname of the load balancer.
    Note: The hostname should be the domain name of the load balancer. For example: www.example.com.
  2. Make the appropriate selection regarding SSL configuration based on your environment.
    Important: If an SSL certificate is not specified, the installer will not generate the configuration and certificate files required for the installation of the On-Premises Connector and the ODBC and JDBC drivers.
    • Select Yes to specify the SSL certificate file to be used with the Hybrid Data Pipeline server. The specified file must be the root certificate used to sign the certificate for the load balancer server. PEM, DER, and Base64 encodings are supported. Type the full path to the certificate file, or click Choose... to browse to the location of the SSL certificate file. Then, click Next.
    • Select No if you do not want to specify an SSL certificate.
  3. Select whether you want to use the MySQL Community Edition data store for either a system database or data source. Hybrid Data Pipeline does not provide a driver for MySQL Community Edition; however, it does support the MySQL Connector/J driver. If you choose Yes, in the Jar Path field, provide the name and location of the driver's jar file.
    For more information on the MySQL Connector/J driver, refer to the MySQL developer website at https://dev.mysql.com/.
  4. Select Kerberos for SQL Server if you plan to authenticate using Kerberos. Click Choose... to type a path or browse to the location of the configuration file krb5.conf.
  5. Select the external database you want to use to store system information from the drop down menu.
    • Select Oracle, and continue at Step 6.
    • Select MySQLCommunity, and continue at Step 7.
    • Select MSSQLServer, and continue at Step 8.
    • Select PostgreSQL, and continue at Step 9.
  6. Provide the Oracle connection information.
    1. Type the name of the host.
    2. Type the port number.
    3. Select the connection type. Do one of the following:
      • If you connect using the Oracle System Identifier (SID), select Connect using SID, then type the SID.
      • Select Connect using Service Name, then type 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. The global database name typically comprises the database name and domain name.
    4. Optionally, in the Advanced Options field, specify additional connection parameters and their values to be included the connection url. Values should be entered as a semicolon-separated list of parameter=value. For example, you may enter to following options to configure SSL: 
      encryptionLevel=Required;encryptionTypes=(AES256);
dataIntegrityLevel=Required;dataIntegrityTypes=(SHA1);
encryptionMethod=SSL;keyStore=/common/Oracle/trustStore.jks;
keyStorePassword=secret; serverType=dedicated;authenticationMethod=ntlm;
hostNameInCertificate=oracle;editionName=hybrid
    5. Click Next, and continue at Step 10.
  7. Provide connection information for the MySQL Community Edition external database.
    1. Type the name of the host.
    2. Type the port number.
    3. Type the database name.
    4. Optionally, in the Advanced Options field, specify additional connection parameters and their values to be included the connection url. Values should be entered as a ampersand-separated list of parameter=value.
    5. Click Next, and continue at Step 10.
  8. 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. Optionally, in the Advanced Options field, specify additional connection parameters and their values to be included in the connection URL. Values should be entered as a semicolon-separated list of parameter=value.
    6. Optionally, in the Advanced Options field, specify the path to the krb5.conf file to use Kerberos authentication method.
    7. Click Next, and continue at Step 10.
  9. Provide the PostgreSQL connection information.
    1. Type the name of the host.
    2. Type the port number.
    3. Type the database name.
    4. Optionally, in the Advanced Options field, specify additional connection parameters and their values to be included in the connection URL. Values should be entered as a semicolon-separated list of parameter=value.
    5. Click Next, and continue at Step 10.
  10. Provide the database credential information for the external database.
    Attention: For an installation using environment variables, leave all fields blank. Then, when prompted, skip database validation. Database validation is not required for a successful installation.
    • In the Admin Username field, 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, see External system databases.
    • In the Admin Password field, type the password for an database administrator account.
    • In the Username field, type a user name. For a list of required privileges, see External system databases.
    • In the Password field, type the user password.
    Important:
    • Administrator credentials are required at install time to add and modify required tables in the database schema. Administrator credentials are not used by the product at run time.
    • Passwords for an external database implementation are not persisted. These values must be specified in the response file with the D2C_DB_ADMIN_PASSWORD and D2C_DB_USER_PASSWORD options before running a silent install.
    • The installer attempts to validate the database. If the installer is unable to validate, you are prompted to reenter credentials or skip validation. If you skip validation, the response file must have the SKIP_DATABASE_VALIDATION property set to true. During a silent installation, the installer will complete the installation even when the database validation fails.
  11. Review the Server Access Port. The Server Access Port must be opened for the load balancer.
    Note: In most cases, the default ports work without problems. However, your environment might have already defined a function for one or more of the ports. If a default port is in use, the installer pops up a message so that you can make the necessary changes.
    Table 1. Server Access Ports
    Name Default Description
    Server Access HTTP Port 8080 HTTP port used for communication to the Hybrid Data Pipeline Web UI and API.
    Server Access HTTPS Port 8443 HTTPS port used for encrypted communication to the Hybrid Data Pipeline Web UI and API.
  12. Select whether you are using the On-Premises Connector.
    Note: An SSL certificate must be specified in Step 2 to use the On-Premises Connector.
    • If using the On-Premises Connector, select Enable On-Premises Connector. Click Next and continue to the next step.
    • If not using the On-Premises Connector, leave the check box empty and click Next. Continue at Step 14.
  13. Review the On-Premises Access Ports. The On-Premises Access Port and the TCP Notification Server Port must be opened for the load balancer.
    Note: In most cases, the default ports work without problems. However, your environment might have already defined a function for one or more of the ports. If a default port is in use, the installer pops up a message so that you can make the necessary changes.
    Table 2. On-Premises Access Ports
    Name Default Description
    On-Premises Port 40501 Port for communication between the On-Premises Connector and the Hybrid Data Pipeline server.
    Notification Server TCP Port 11280 TCP port for communication from the On-Premises Connector to the Notification Server.
    Notification Server TCP SSL Port 11443 TCP SSL port for encrypted communication from the On-Premises Connector to the Notification Server.
    Message Queue Port 8282 Port for communication between the Notification Server and the Hybrid Data Pipeline server. Required for Linux installation of Hybrid Data Pipeline. Not used in Docker deployments.
  14. Review the Server Internal Ports. The Internal API Port and the Shutdown Port must be opened.
    Important: As a matter of best practice, the Shutdown Port should not be available outside the firewall of the Hybrid Data Pipeline instance.
    Note: In most cases, the default ports work without problems. However, your environment might have already defined a function for one or more of the ports. If a default port is in use, the installer pops up a message so that you can make the necessary changes.
    Table 3. Server Internal Ports
    Name Default Description
    Internal API HTTP Port 8190 HTTP port for communication between individual nodes in a cluster deployment.
    Internal API HTTPS Port 8090 HTTPS port for encrypted communication between individual nodes in a cluster deployment.
    Shutdown Port 8005 TCP port that listens for shutdown requests.
  15. Review the installation summary. If you are satisfied with your choices, press ENTER to generate the response file.
  16. After the response files has been generated, press ENTER to exit the installer.
  17. Confirm that a response file has been generated by navigating to the response file directory you specified in Step 3 in "Creating a response file using the installer in GUI mode" and opening the response file.
  18. You must now edit the response file according to the guidelines in Editing a GUI 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.