This is documentation for Apprenda 7 and 8.
Documentation for older versions are also available.

Ports Used by Apprenda

This page explains the ports used by Platform services to communicate with each other. If communication is blocked on any of these ports by a firewall, the Platform's ability to operate will be affected. 

Ports Used During Installation or Upgrades

The following table lists ports that are used during Platform installation or upgrade in addition to the ports used during normal Platform operations. In some cases the ports will also be used after the installation or upgrade by different Apprenda components. The table lists each Apprenda component, the Platform Server Roles where each component can be found, the inbound connections from which the component will receive information, and the port(s) on which it communicates:

Apprenda Component Platform Server Role(s) Inbound Connections(s) Inbound Port(s)
Apprenda Platform Installer Windows server from which the Apprenda Installer is run Any Windows server

WMI: 135 and a WMI Fixed Port*

TCP 445

Outbound: TCP 80 or TCP 443

Helper Windows Service Any Windows server Any Windows server TCP 33000
Linux Updater Any Linux server Apprenda Platform Installer TCP 12065

Port TCP 445 must be open for installations and upgrades and, optionally, can be configured for continued use by the Platform Repository during runtime.

*Windows Management Instrumentation (WMI) is required by the Platform Installer. For increased security, It is recommended that a fixed port is configured for this service before Platform installation. For more information on setting this up, please see the Microsoft WMI documentation (https://msdn.microsoft.com/en-us/library/bb219447(v=vs.85).aspx).

Linux server installation and upgrade must be done manually, and this port will not need to be opened.

Ports Used By the Platform

The following table lists the ports that will be used by the Platform during normal intra-cloud Platform communication. The table lists each Apprenda component, the Platform Server Roles where each component can be found, the inbound connections from which the component will receive information, and the port(s) on which it communicates:

Apprenda Component Platform Server Role(s) Inbound Connections(s) Inbound Ports
Cache Platform Cache (Windows server) Windows Host, WCF Services, .NET UIs, Load Management, Linux Container, Linux Workloads Configured during Installation
Linux Workloads (guest application components), including Java Web Applications (WARs) and Linux Services Linux Server WCF Services, .NET UIs, Load Management, Linux Workloads Configured through Platform Registry settings
Load Management Load Manager Windows Host, .NET UIs

TCP 25254, TCP 25255

TCP 80 or TCP 443

.NET UIs (guest application components and Platform components) Windows Web Server Load Management  TCP 8080
Platform Coordination Platform Coordinator (Windows server) Windows Host, WCF Services, .NET UIs, Load Management, Linux Container, Linux Workloads, Platform Coordination (internal cluster communication)

Platform component communication: TCP 2181 

Lead election and communication: TCP 2182

Internal cluster communication: TCP 2183

Platform SQL Server Instances SQL Server* Windows Host, WCF Services, .NET UIs, Load Management, Linux Container, Linux Workloads, Cache, Platform Coordination, Platform SQL Server Instances

Default instance: TCP 1433

Default SQL Browser: UDP 1434

Windows Host, WCF Services, .NET UIs MS DTC: 135 and MS DTC Dynamic or Fixed Port(s)**
Platform Repository Network Share Windows Host, WCF Services, Linux Container, Load Management Dependent on network share configuration
WCF Services (guest application components and Platform components) Windows Web Server and Application Server Windows Host (Router), WCF Services, .NET UIs, Linux workloads TCP 33000,TCP 34000
Windows Host (Router), WCF Services, .NET UIs, Platform SQL Server Instances MS DTC: 135 and MS DTC Dynamic or Fixed Port(s)**
Windows Host Windows Web Server and Application Server WCF Services, .NET UIs, Load Management, Linux Container, Linux Workloads, Apprenda Platform Installer

TCP 12001, TCP 12004, TCP 12005, TCP 12065

Logger: TCP 15000

Router: TCP 11000, TCP 12000, TCP 20000, TCP 22000

Bootstrap API: TCP 49152 - 65535

WCF Services, .NET UIs, Platform SQL Server Instances MS DTC: 135 and MS DTC Dynamic or Fixed Port(s)**
AD FS (Federation Broker) Application Server Same requirements as WCF Services and Windows Hosts
Client Browser TCP 443***
Windows Services Windows Web Server and Application Server Load Management, WCF Services, .NET UIs, Linux Workloads Configured through Platform Registry settings

*SQL Server Clustering requires a different port configuration than a single SQL Server instance for Platform communications. For more information, please see Microsoft documentation on SQL Server requirements here https://msdn.microsoft.com/en-us/library/cc646023.aspx.

**Microsoft Distributed Transaction Coordinator (MS DTC) is required by the Platform depends for distributed transactions. For increased security, it is recommended that a fixed port or port range is configured for this service before Platform installation. For more information on setting this up, please see the Microsoft MS DTC documentation (https://support.microsoft.com/en-us/kb/306843).

***Port configuration requirements may depend on the environment, especially when a reverse proxy is used in front of an AD FS farm (Federation Broker). For more information, please refer to Microsoft documentation on AD FS requirements here https://technet.microsoft.com/en-us/windows-server-docs/identity/ad-fs/design/ad-fs-requirements/

Ports Used by Clouds in a Hybrid Cloud Platform

The following table lists the ports that will be used during normal Platform communication between Clouds in a Hybrid Cloud Platform. The table lists Apprenda components, the Platform Server Roles where each component can be found, the inbound connections from which the component will receive information form external clouds or locations, and the port(s) on which it communicates:

Apprenda Component Platform Server Role(s) Inbound Connections(s) from External Cloud/Location Inbound Ports
Load Manager Load Manager Windows Host,  .NET UIs Inbound and Outbound: TCP 80, TCP 443
Platform Repository Network Share Windows Host, WCF Services, Linux Container, Load Manager Dependent on network share configuration and location
Platform SQL Server Instances SQL Server Windows Host. WCF Services, .NET UIs, Load Management, Linux Container, Linux Workloads, Cache, Platform Coordination

Default Instance: TCP 1433

Default SQL Browser: UDP 1434 or custom configuration and location

Windows Host. WCF Services, .NET UIs MS DTC: 135 and MS DTC Dynamic or Fixed Port(s)*

Ports and protocols required for connections to the Platform Repository and Platform Databases may change based on their configuration and location on your Platform.

*Microsoft Distributed Transaction Coordinator (MS DTC) is required by the Platform depends for distributed transactions. For increased security, it is recommended that a fixed port or port range is configured for this service before Platform installation. For more information on setting this up, please see the Microsoft MS DTC documentation (https://support.microsoft.com/en-us/kb/306843).

Ports Affected by Platform Registry Settings

It should noted that ports used by guest application Java Web Application components (WARs), Linux Service components, and Windows Services components are determined by settings configured by the Platform Operator in the Platform Registry:

Name Explanation Values
Hosting.Linux.WorkloadDynamicPortRangeMax Highest port number allowable for Java Web Application components (WARs) for guest apps. Any valid port number; default at installation is 65535.
Hosting.Linux.WorkloadDynamicPortRangeMin Lowest port number allowable for Java Web Application components (WARs) for guest apps. Any valid port number; default at installation is 1024.

Hosting.LinuxService.MaxPortsPerComponent

Maximum allowable number of ports per Linux Service component for guest apps. Any positive integer.

Hosting.LinuxService.PortRangeHighLimit

Highest port number allowable for Linux Service  components for guest apps. Any valid port number.

Hosting.LinuxService.PortRangeLowLimit

Lowest port number allowable for Linux Service  components for guest apps. Any valid port number.

Hosting.UserInterface.PortRangeLowLimit

Lowest port allowable for .NET User Interfaces (guest applications). Any valid port number; default at installation is 8081.

Hosting.UserInterface.PortRangeHighLimit

Highest port allowable for .NET User Interfaces (guest applications). Any valid port number; default at installation is 8090.
Hosting.WindowsServices.MaxPortsPerComponent Maximum allowable number of ports per  Windows Service component for guest apps. Any positive integer.
Hosting.WindowsServices.PortRangeHighLimit Highest port number allowable for Windows Service components for guest apps. Any valid port number.
Hosting.WindowsServices.PortRangeLowLimit Lowest port number allowable for Windows Service components for guest apps. Any valid port number.
Highest port number allowable for Linux Service  components for guest apps.