Before you begin:
Note: The installer does not support changing a non-load balancer 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:

    chmod +x ./PROGRESS_DATADIRECT_HDP_SERVER_nn_LINUX_64_INSTALL.bin

  3. Run the executable by entering the product file path and pressing ENTER.
    1. Type the file name and path of the product file. For example:

      ./PROGRESS_DATADIRECT_HDP_SERVER_nn_LINUX_64_INSTALL.bin -i console

    2. Press ENTER.
    3. The Introduction step appears. Press ENTER to continue.
  4. 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.
  5. Choose the JVM you want to use for the runtime operation of the server.
    Note: See Product requirements for details on JVM prerequisites.
    • Type 1 to use the JVM that was used to run the installer.
    • Type 2 to enter your preferred JVM. Then enter the full path to the Java executable.
  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:
    • For non-load balancer deployments where the server is receiving queries directly, the hostname should be tied to the DNS for public access. This allows you to update IP addresses in the DNS without having to run an upgrade installation to reconfigure your deployment.
    • 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 installation or upgrade.
  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 23.
    • Type 2 to change values for the following configurations. Then, press ENTER to continue.
      • Change the location of the SSL certificate file
      • Enable or disable FIPS
      • Add MySQL Community Edition as a data store or external system database
      • Change the system database you are using
      • Update external system database credentials
      • Change Server Access Ports
      • Change On-Premises Connector Ports
      • Change Server Internal Access Ports
    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 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 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.
  11. 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.
  12. 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/.
  13. Choose the appropriate option depending on whether you are using Kerberos for SQL Server authentication.
    • Type 1 and press ENTER, if you are authenticating using Kerberos. Type the path to the configuration file krb5.conf, and press ENTER again.
    • Type 2 and press ENTER, if you are not using Kerberos authentication in your environment.
  14. Select the type of external database you want to use to store system information.
    • Select Oracle, and continue at Step 15.
    • Select MySQLCommunity, continue at Step 16.
    • Select MSSQLServer, and continue at Step 17.
    • Select PostgreSQL, and continue at Step 18.
  15. 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 19.
  16. 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 19.
  17. 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. Press ENTER, and continue at Step 19.
  18. Provide 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 19.
  19. 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 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.
    • 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.
    • 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.
    • You are prompted to provide the User Password. Type the user password.
    • The installer validates the connection. Press ENTER to continue.
  20. Review the Server Access Port. The Server Access Port must be opened for the load balancer.
    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.
  21. Take the appropriate action depending on whether you are using the On-Premises Connector.
    • If you are not using the On-Premises Connector, skip to the next step.
    • 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 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.
  22. 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 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.
  23. Review the summary. If you are satisfied with your choices, press ENTER to upgrade.
  24. After the upgrade has finished, press ENTER to exit the installer.
  25. Verify the installation by accessing the Hybrid Data Pipeline user interface from a browser. The login page should appear. For example:

    https://<myserver>/

    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.

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

What to do next

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.

Important: If you previously configured server-side SSL in a deployment using a load balancer, you must rerun the enable_ssl.sh script on each server node to re-enable SSL. See SSL configuration for details.