Load balancer upgrade (console mode)

Note: The installer does not support changing a standalone deployment to a load balancer deployment during an upgrade, or vice versa. To make such a change, you would need to uninstall the server and then reinstall it. See Uninstalling Hybrid Data Pipeline server and Installing the Hybrid Data Pipeline server for details.

After copying the product installation file to a temporary directory, take the following steps to upgrade a load balancer deployment with the installer in console mode.

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:

3. Run the executable by entering the product file path and pressing ENTER.

4. The License Agreement appears. Press ENTER multiple times to advance through the license agreement. Make sure that you read and understand the license agreement.

To accept the terms in the License Agreement and continue with the installation, type Y.

5. You are prompted for the installation directory. Type the absolute path to the installation directory of the installation you want to upgrade. Then, press ENTER.

6. You are prompted to upgrade the existing installation or go back to enter a different installation directory. Type 1 to upgrade the existing installation. Then, press ENTER.

7. Choose whether you want to upgrade with an evaluation or licensed version of the product. Licensed installations require a valid License Key.

Evaluation. Type 1 to upgrade with an evaluation version of the product that is fully functional for 30 days. Then, press ENTER.

Licensed. Type 2 if you purchased a licensed version of the product. Then, press ENTER. Type the license key, including any dashes, and then press ENTER.

8. Accept the fully qualified hostname for your Hybrid Data Pipeline Server. By default, the installer suggests the name of the current machine. Then, press ENTER.

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

9. Select how you want to continue the upgrade.

Type 1 for an Express upgrade to persist previously established values. Then, press ENTER and continue at Step 24.

Type 2 to change values for the following configurations. Then, press ENTER to continue.

Note: The following elements of an installation cannot be modified when performing an upgrade of a load balancer installation: key location, load balancer hostname, and On-Premises Connector enablement.

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

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

12. Specify whether you want to enable FIPS on the Hybrid Data Pipeline server.

Important: To enable FIPS, your hardware must support secure random, or you must have a secure random daemon installed.

Important: When you enable FIPS during an upgrade, the environment uses the encryption key for the system database that was generated during the original installation of the server. This encryption key, while generated with a FIPS compliant algorithm, was not generated with a FIPS certified implementation of the algorithm.

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

13. Depending on your environment, provide the appropriate SSL certificate information.

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 SSL certificate file. Then, press ENTER.

Type 2 to use the SSL certificate file that was specified during the previous installation or bypass the specification of an SSL certificate. Then, press ENTER.

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

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

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

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

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

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

20. You are prompted to 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.

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 upgrade. See Silent upgrade process for details.

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.

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

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.

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

22. Take the appropriate action depending on whether you are using the On-Premises Connector.

If you are using the On-Premises Connector, review the On-Premises Access Ports. The On-Premises Access Port and the TCP Notification Server Port must be opened for the load balancer.

Important: If you changed any values for On-Premises Access Ports during an upgrade, you will need to reconfigure the load balancer to use the new ports.

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

23. 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 31. Server Internal Ports
Name	Default	Description
Internal API Port	8190	Non-SSL port for the Internal API
Shutdown Port	8005	Shutdown port

24. Review the summary. If you are satisfied with your choices, press ENTER to upgrade.

25. After the upgrade has finished, press ENTER to exit the installer.

26. 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 name or IP address of the server hosting your load balancer device.

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 upgrade. See Server installation log files for details.

If you changed any values for On-Premises Access Ports during an upgrade, you will need to reconfigure the load balancer to use the new ports.