Versions Compared

Version Old Version 1 New Version Current
Changes made by

Sebastian Koch

Sebastian Koch

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column
width400px

The Site Controller software requires communication with the azeti Middleware Engine to send out data and to receive configurations. Therefore some network ports must be opened to run the overall solution properly. Different types of communication is involved and it is mandatory to configure your firewall accordingly for proper functionality.

SIte Controller to azeti CloudEngine

The SiteController Site Controller software running on your edge device requires outgoing traffic towards its destination azeti Control Panel Engine server.

User Browser to azeti CloudEngine

The azeti Cloud Engine is a web application that uses the websockets WebSockets technology for communication and thus requires ports to be opened between the azeti Cloud Engine Server and the users web browser.

Column
width400px
Panel
borderColorlightgrey
bgColor#f0f0f0
titleOn this page:

Table of Contents

Firewall Between User's Web Browser and azeti

...

Engine

PortFirewallDirectionSource hostDestination hostProtocolDescription
80optionaloutgoingTomcatUser's Web BrowserHTTPWeb application
debugging
(testing/dev)
8081optionaloutgoingActiveMQUser's Web BrowserWebsocketsWeb application
debugging
live updates (testing/dev)
443mandatoryoutgoingTomcatUser's Web BrowserHTTPSWeb application (production)
8082mandatory

outgoing

ActiveMQ

User's Web Browser

Secure WebsocketsWeb application live updates (production)

Firewall Between Site Controller and azeti

...

Engine

PortFirewallDirectionSource hostDestination hostProtocolDescription
1883optional outgoingActiveMQSiteControllerMQTTSiteController from/to azeti Cloud Broker in VPN environments
8883optionaloutgoingActiveMQSiteControllerMQTT + TLSSiteController from/to azeti Cloud Broker in Internet environments

Full Networking Within azeti

...

Engine Installation

Port
FirewallDirectionSource hostDestination host
ApplicationProtocolDescription
1883
 
outgoing
ActiveMQ
 
MQTT
SiteController
Site Controller from/to azeti
Cloud
Engine Broker in VPN environments
8883
  
ActiveMQ
 
MQTT + TLS
SiteController
Site Controller from/to azeti
Cloud
Engine Broker in Internet environments
8081
  
ActiveMQ
 
WS
 
Web browser to ActiveMQ web sockets
8082
  
ActiveMQ
 
WSS
 
Web browser to ActiveMQ web sockets
61613
  
ActiveMQ
 
STOMP
 
Internal connection Back-end/ActiveMQ
61614
  
ActiveMQ
 
STOMP+TLS
 
Internal connection Back-end/ActiveMQ
61616
 
 
ActiveMQ
  
JMS
        5432  PostgreSQL          8083  InfluxDB   8086  InfluxDB          80  Tomcat HTTP 443  Tomcat HTTPS
Internal connection Back-end/ActiveMQ
5432PostgreSQLTCP/Postgres-specificInternal connection Back-end/PostgreSQL
8083InfluxDBHTTPInternal connection Back-end/InfluxDB admin interface
8086InfluxDBHTTPInternal connection Back-end/InfluxDB
80TomcatHTTPWeb application (dev/test)
443TomcatHTTPSWeb application (production)