Feedback

Feedback

Did this article resolve your question/issue?

   

Article

List of ports required for Hybrid Data Pipeline (HDP)

Printable View

Information

 
TitleList of ports required for Hybrid Data Pipeline (HDP)
URL NameList-of-ports-required-for-Hybrid-Data-Pipeline-HDP
Article Number000113957
EnvironmentProduct: Hybrid Data Pipeline (HDP)
Version: All supported versions
OS: All supported platforms
Database: All supported databases
Application: Installer
Question/Problem Description
When installing Hybrid Data Pipeline, which ports need to be made available?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Below is the list of the ports and what they are used for:

8080 – non-SSL primary access to Hybrid Data Pipelines features including the following ODBC/JDBC connectivity, OData, UI, Management API, Admin API
8443 – SSL primary access Hybrid Data Pipeline features including the following ODBC/JDBC connectivity, OData, UI, Management API, Admin API

40501 – On-Premises access port for connections to the data access service from the On-Premises Connector
11280 – TCP port for connections to the notification server from the On-Premises Connector
11443 – SSL port for connections to the notification server from the On-Premises Connector

8282 – Message Queue port used for communication between the data access service and the notification server for On-Premises Connector.  
8190 – Internal API port used for direct communication between nodes.
8090 – Internal API SSL port used for direct communication using SSL between nodes.
8005 – Shutdown port used to stop the Hybrid Data Pipeline server from running.

If using a standalone installation without a reverse proxy and do not have a need for the On-Premises Connector, then open port 8443 externally for ODBC/JDBC, OData, UI, and API access.  The user could open port 8080, but that is not recommended as that is the non-SSL port.  If your organization does not allow opening port 8443, then use iptables to configure port 443 to redirect to port 8443.  Ensure that the system can access ports 8190 or 8090 for direct communication between components on the node, but these ports do not need to be made available externally.  Also, allow access to the message queue port so that the data access service can communicate to the notification server.

If using a standalone installation with a reverse proxy, then ensure the reverse proxy is accessible externally and that the reverse proxy can forward requests to port 8080 since the reverse proxy will handle the SSL termination.

If using a standalone installation with the OPC, then choose to open ports 40501 and ports 11280 and/or 11443 depending upon whether SSL or non-SSL communication is required from the On-Premises connector to the Hybrid Data Pipeline server.

If installing a cluster behind a load balancer, then make sure that the load balancer is accessible externally and that it can forward requests to port 8080 on each of the Hybrid Data Pipeline nodes.  Additionally, the Hybrid Data Pipeline server nodes must be able to communicate to the message queue port (8282) and the internal API ports (8090, 8190), but these only need to be accessible from the different nodes in the cluster.

For all cases, the shutdown port just needs to be accessible so that the stop script can shutdown the server cleanly.
Workaround
Notes
Last Modified Date8/31/2022 12:52 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.


Copyright © 2022 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.

Progress, Telerik, Ipswitch, Chef, Kemp, Flowmon and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.

Terms of Use Privacy Center Security Center Trademarks License Agreements Code of Conduct Careers Offices
Do Not Sell My Personal Information