While the biggest part of the communication with the Application Server is incoming traffic from the Clients there are also other connections that must or shall be allowed. Table 1 summarizes the connections and
Connection |
Mandatory |
Firewall settings |
Connection To Redbex Application Server Database |
|
The Application Server needs a connection to the Application Server Database. Your firewall needs to be configured to allow those connections. The actual configuration needed depends on your SQL Server Network Configuration. E.g. if your SQL server uses TCP/IP the default port. Please refer to the Sql Server Documentation for more details. |
Incoming connections from Redbex Clients |
|
Clients to the Redbex Application Server must be able to connect to the application server using the communication protocol defined during installation (i.e. in your instance configuration). Open the configured ports for incoming traffic. See chapter Step 7: Web service configuration for the default ports suggested by the installer. |
Outgoing connections to the Redbex Distribution Server |
|
The Application Server needs connection to Pöyry Infra GmbH's Redbex Distribution Server to download product updates, licenses, etc. Configure your firewall to all outgoing TCP connections to distribution.redbex.com (137.117.204.95) on port 80. |
Outgoing SMTP connections |
|
The Redbex Application Server needs access to an SMTP server in order to send emails. Since the access data for new users is sent via email access to an SMTP server is mandatory (if you have more than one user in your installation) Allow all outgoing SMTP connections to the SMTP Server you want to use (as configured in the global settings) |
Outgoing FTP |
|
The Application Server can load data from FTP servers and can store data to FTP servers. If you plan this functionality you will have to configure the firewall to allow outgoing connections to the used FTP servers. |
Google Maps API |
For creating map views with Google Maps background images Redbex accesses the Google Maps Static API. If you want to use this functionality you will have to open your firewall |
|
Bing Maps API |
For creating map views with Microsoft Bing Maps background images Redbex accesses the Microsoft Bing Maps API. For creating map views with Google Maps background images Redbex accesses the Microsoft Bing Maps API. |
|
twilio.com |
Redbex uses the Twilio API. In order to be able to send SMS from Redbex this API must be accessible. The twilio service is hosted in Amzon's Elastic Cloud. You need to ensure that your firewall allows outgoing UDP and associated return traffic to any IP address in Amazon’s published range of public IPs. For more details see: |
|
Log Entries |
|
Redbex supports logging to the cloud based log service logentries.com. To use this functionality the Application Server must be allowed to communicate with the API of this service. For this ports 80,514, 443, 10000 and 20000 shall be opened outgoing for following IP addresses: 46.51.172.0 54.247.179.233 46.137.78.79 54.217.226.43 54.217.226.19 54.217.226.25 |
WMS, WFS Services |
|
The Redbex Application Server can make use of WMS (Web Map Services) and WFS (Web Feature Services). To access these services the appropriate Connections must be allowed. |
Table 1: Summary of Internet connections of the Application Server.
