Common Port Usage

Listed below are some of the default ports that Urbancode uses with their products. Please note that NOT ALL may be listed and also that THEY CAN BE CHANGED BY THE USER. There are several combinations of ports that could occur, so many that they cannot be listed here:

               48127!        2,151,158,770,844,441,733,375
48127c5  =  ------------  ~  002 hextillion, 151 quintillion, 158 quadrillion, 770 trillion
            5!(48127-5)!     844 billion,    441 million,     733 thousand,    375 combinations
This assumes only using the registered ports available!



Always-Open Ports (Ephemeral)

There are some ports that will always need to be open that we are unable to determine what their value will be. While we do our best to provide you (the customer) with the ports we use by default, you will always have another port open in addition to the default port per connection. We cannot manage this port as it is determined by the Operating System. More information on these types of ports can be found, here.

AnthillPro 3.5 Versions

  • Server
    • Web UI: 8080
    • Web UI w/SSL: 8443
    • Remoting Port: 4567
  • Agent
    • All Communication Ports are determined by the agent during install time. Versions of anthillpro prior to 3.6 had all agents on a different port when attempting to connect to the server.
  • Derby Database
    • Database Port: 11366


AnthillPro 3.6+ Versions

  • Server
    • Web UI: 8080
    • Web UI w/SSL: 8443
    • Remoting Port: 4567
    • JMS Port: 7915
  • Agent
    • No ports are opened for communication by default. Agents connect directly to a server or a relay, whereby the ports are specified on those.
  • Derby Database
    • Database Port: 11366


AnthillPro AgentRelay™

  • JMS port: 7916 (note that this defaults to unsecure)
  • HTTP Proxy port: 20080


AnthillPro Distributed Web

  • Web UI: 8081 (or 8443 if SSL is selected)
  • JMS Port: 7917


AnthillPro Sample Communications Diagrams

Server & Agent Scenario

DEVICE COMMUNICATIONS DEVICE
Server (TCP) 8080 [HTTP] Agent
(TCP) 7915 [JMS]


Server, Agent, AgentRelay™ & Agent Scenario

DEVICE COMMUNICATIONS DEVICE COMMUNICATIONS DEVICE
Server (TCP) 8080 [HTTP] Agent
(TCP) 7915 [JMS]
(TCP) 8080 [HTTP] AgentRelayâ„¢ (TCP) 20080 [HTTP PROXY] Agent
(TCP) 7915 [JMS] (TCP) 7916 [JMS PROXY]


Server, Agent, AgentRelay™, Agent, Distributed Web, Agent, AgentRelay™ & Agent Scenario

DEVICE COMMUNICATIONS DEVICE COMMUNICATIONS DEVICE COMMUNICATIONS DEVICE
Server (TCP) 8080 [HTTP] Agent
(TCP) 7915 [JMS]
(TCP) 8080 [HTTP] AgentRelayâ„¢ (TCP) 20080 [HTTP PROXY] Agent
(TCP) 7915 [JMS] (TCP) 7916 [JMS PROXY]
(TCP) 8080 [HTTP] Distributed Web (TCP) 8081 [HTTP PROXY] Agent
(TCP) 7917 [JMS PROXY]
(TCP) 7915 [JMS] (TCP) 8081 [HTTP PROXY] AgentRelayâ„¢ (TCP) 20080 [HTTP PROXY] Agent
(TCP) 7917 [JMS PROXY] (TCP) 7916 [JMS PROXY]


Complexity Diagram

A sample of how one can imagine a setup incorporating a server, agents, distributed web, and AgentRelay™'s.

ComplexCommunicationDiagram.png

CAS

Content Addressable Storage

REST Web Services: 8484 (note that this defaults to unsecure; no SSL default)

  • Derby Database
    • Derby Database Port: 11388

uDeploy

  • Web UI: 8585 (note that this defaults to unsecure; no SSL default)
  • JMS Port: 7918
  • Derby Database
    • Derby Database Port: 11377