Multiple access ports on Hybrid Data Pipeline hosts must be opened and unassigned to other functions. In turn, you must configure the firewall of each host machine to accept connections on ports the server uses (see Firewall configuration). The following tables document required ports and default port numbers.

Note:
  • Default port numbers can be modified during deployment. During installation on a Linux host, you can specify port numbers when prompted. If you are deploying the Docker image, you can map the container port (the default) to the Docker host port as an argument in the docker run command.
  • For load balancer deployments on Linux, HTTP ports are disabled when you run the enable_ssl.sh script to enable SSL. See SSL configuration (load balancer) for details.
  • For non-load balancer, single-node deployments on Linux, you may run the disable_http.sh script to disable HTTP ports. See SSL configuration (non-load balancer) and Disabling HTTP ports for details.

Server Access Ports

A Server Access Port must be available to the load balancer or across the firewall.

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.

Server Internal Ports

An Internal API Port should be opened for a cluster deployment. The Internal API Port must be available to other nodes in the cluster. For Linux installations, the Shutdown Port must be specified, but should not be available outside the firewall.

Important: The Internal API Port is not required for a single-node deployment behind a load balancer. However, if any additional nodes are added to the load balancer deployment, then an upgrade or redeployment of Hybrid Data Pipeline would be required to open the Internal API Port.
Table 2. 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.

On-Premises Access Ports

For a deployment using the On-Premises Connector, the On-Premises Access Port and the Notification Server Ports must be available to the load balancer or across the firewall. For Linux installations, the Message Queue Port must be opened and available across the firewall.

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