Creating a response file for a non-load balancer installation (console mode)

  1. Depending on your environment, provide the appropriate SSL certificate information.
    • Type 1 to specify a PEM file to be used by the server to establish SSL connections with ODBC and JDBC client applications. Type the full path of the PEM file. Then, press ENTER.

      Note: The PEM file must consist of a private key, a public key certificate issued by a certificate authority (CA), and additional certificates that make up the trust chain. See The PEM file for more information.

    • Type 2 to use the self-signed certificate included with the installation. Then, press ENTER.

      Note: The self-signed certificate may be used in a test environment. However, for production, a PEM file with required information should be specified. See The PEM file for more information.

  2. Choose the appropriate option depending on whether you are using MySQL Community Edition. MySQL Community Edition can be used as an external system database or as a data source. Hybrid Data Pipeline does not provide a driver for MySQL Community Edition. However, you can use the MySQL Connector/J driver to use MySQL Community Edition as an external system database or as a data source.
    • Type 1 and press ENTER, if you are using MySQL Community Edition. Type the name and location of the MySQL Connector/J jar file, and press ENTER again.
    • Type 2 and press ENTER, if you are not using MySQL Community Edition in your environment.
    Note: For more information on the MySQL Connector/J driver, visit the MySQL developer website at https://dev.mysql.com/.
  3. Select the type of database you want to use to store system information.
    • Type 1 to use the default internal database (supplied by this installation). Continue at Step 5.
    • Type 2 to use an external database. With this option, you store system information in an external database.
    Note: Users and data sources created in the internal database are specific to the internal database. They are not migrated to the external database if you subsequently modify the Hybrid Data Pipeline server to use an external database.
  4. Select the type of external system database you want to use to store system information.
    • Select Oracle, and continue to the next Step 6.
    • Select MySQLCommunity, and continue at Step 7.
    • Select MSSQLServer, and continue at Step 8.
    • Select PostgreSQL, and continue at Step 9.
  5. Enter the database port for the internal database. If your environment has already defined a function for the default port, the installer alerts you with a message so that you can specify a different port. Press ENTER and continue at Step 11.
  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), type 1, then type the SID.
      • If you connect using the Service Name, type 2,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—a name that typically comprises the database name and domain name.
    4. Optionally, when prompted for Advanced Options, 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. Press ENTER, and continue at Step 10.
  7. Provide connection information for the MySQL Community Edition external database.
    1. Type the name of the Hostname.
    2. Type the port number.
    3. Type the database name.
    4. Optionally, when prompted for Advanced Options, 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. Press ENTER, 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. Press ENTER, 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. Press ENTER, and continue at Step 10.
  10. You are prompted to provide the external database credential information for a user with administrator privileges and for a user without administrator privileges.
    Attention: For an installation using environment variables, do not enter credential information and simply press ENTER at each prompt. Then, when prompted, skip database validation. Database validation is not required for a successful installation.
    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, see External system databases.
    2. You are prompted to provide the Admin Password. Type the password for an external database administrator account.
    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, see External system databases.
    4. You are prompted to provide the User Password. 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 Ports. A Server Access Port must be available to the end user across the firewall. Best security practices recommend using an HTTPS port.
    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.
    • If using the On-Premises Connector, type 1 and press ENTER. Then continue to the next step.
    • If not using the On-Premises Connector, type 2 and press ENTER. Continue at Step 14.
  13. Review the On-Premises Access Ports. The On-Premises Access Port and a Notification Server Port must be available across the firewall. Best security practices recommend using the SSL Notification Server Port.
    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. A port for the internal API and the Shutdown Port must be opened. Best security practices recommend using the Internal API HTTPS Port.
    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 file 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 of "Creating a response file using the installer in console mode" and opening the response file.
  18. You must now 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.