Standalone 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 store information on an internal database supplied by this installation. Continue at Step 5.

Type 2 to store information on an external database. Proceed to the next step.

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.

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.

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 in 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

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

8. Provide the SQL Server 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.

9. Provide the PostgreSQL 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.

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

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.

Note: If the installer is unable to validate, you are prompted to reenter credentials or skip validation. Skipping validation is often desired when performing a silent installation. See Silent installation process for details.

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.

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 6. Server Access Ports
Name	Default	Description
HTTP Port	8080	Port that exposes Hybrid Data Pipeline
HTTPS Port	8443	SSL port that exposes Hybrid Data Pipeline

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.

Table 7. 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
SSL Port	11443	SSL port for the Notification Server
Message Queue Port	8282	Port for the message queue

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 SSL Port.

Important: As a matter of best practice, the Shutdown Port should not be available outside the firewall of the Hybrid Data Pipeline instance.

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

15. Review the installation summary. If you are satisfied with your choices, press ENTER to install.

16. After the installation has finished, press ENTER to exit the installer.

17. Verify the installation by accessing the Hybrid Data Pipeline user interface from a browser. The login page should appear. For example:

where <myserver> is the fully qualified hostname of the machine where you installed Hybrid Data Pipeline.

After logging in, administrators can verify product version information by selecting About from the question mark drop-down menu. For more information on retrieving version information, refer to "Get Version Information" in the Progress DataDirect Hybrid Data Pipeline User's Guide.

Refer to installation log files for a record of any problems that may have occurred during the installation. See Server installation log files for details.

During installation, the installer generates four configuration and certificate files. These files are located in the Hybrid Data Pipeline installation directory <install_dir>/redist. Before installing a component such as the ODBC driver, the JDBC driver, or the On-Premises Connector, these files must be copied to the installer directory of the component you are installing.