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

1. 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.

Type 1 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. Then, press ENTER.

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: To download the MySQL Connector/J driver, visit the MySQL developer website athttps://dev.mysql.com/.

3. Select the type of external system database you want to use to store system information.

4. Provide the Oracle connection information.

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.

d. 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. Provide connection information for the MySQL Community Edition external database.

d. 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.

6. Provide the SQL Server connection information.

e. 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.

7. Provide the PostgreSQL connection information.

d. 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.

8. You are prompted to provide the database credential information for a user with administrator privileges and for a user without administrator privileges. After you enter the credential information, press ENTER to continue.

a. 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.

b. You are prompted to provide the Admin Password. Type the password for a administrator account for the external database.

c. 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.

Administrator credentials are only required at install time to create 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.

9. Specify the desired Java configuration.

Note: Further steps are required to integrate an external JRE. See External JRE support and integration for details.

Type 1 if you will be using an external JRE (a JRE not installed with the server).

10. Specify the fully qualified location of the Java home directory. This is the path to the external JRE. Press ENTER.

11. Specify 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.

Type 1 if you want to enable FIPS. Press ENTER and continue to the next step.

Type 2 and press ENTER if you want to use the default setting which is FIPS disabled.

12. Review the Server Access Port. The Server Access Port must be opened for the load balancer. The default is 8080.

Note: In most cases, the default port works without problems. However, your environment might have already defined a function for the port. If the default port is in use, the installer pops up a message so that you can make the necessary changes.

13. Select whether you are using the On-Premises Connector.

Note: An SSL certificate must be specified in Step 1 to use 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 15.

14. 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 19. On-Premises Access Ports
Name	Default	Description
On-Premises Port	40501	Port for the On-Premises Connector
TCP Port	11280	Port for the Notification Server
Message Queue Port	8282	Port for the message queue

15. 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 any Hybrid Data Pipeline instance.

Table 20. Server Internal Ports
Name	Default	Description
Internal API Port	8190	Non-SSL port for the Internal API
Shutdown Port	8005	Shutdown port

16. Review the installation summary. If you are satisfied with your choices, press ENTER to generate the response file.

17. After the response file has been generated, press ENTER to exit the installer.

18. 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.

19. 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.