Skip to main content
OutSystems

OutSystems Platform network requirements

Network environment requirements

Open ports

The OutSystems services use the following ports: 

  • 2033 - Java RMI port used for communication between services (only used in the Java version)
  • 12000 - OutSystems Deployment Controller Service
  • 12001 - OutSystems Deployment Service
  • 12002 - OutSystems Scheduler Service
  • 12003 - OutSystems Log Service
  • 12004 - OutSystems SMS Connector (only used in the .NET version)

For each server of an OutSystems environment, localhost:

  • must resolve to 127.0.0.1 (IPv4)
  • must be accessible by HTTP

It is possible to configure some of the ports used. Check the Configuration Tool in your OutSystems installation directory to learn more.

The table below details the ports that need to be accessible in each server of an OutSystems environment for publication and runtime connectivity. If a server has both roles (Controller and Front-End), then consider the ports for both profiles on that server.

Source  Destination Port Protocol Notes
SysOps Server 22/3389  TCP Access the server through SSH or Remote Desktop
End-Users Front-End 80 TCP Applications HTTP access
End-Users Front-End 443 TCP Applications HTTPS access (always required for mobile apps)
Development Tools Front-End 80 TCP Deploy applications to the environment
Development Tools Front-End 443 TCP Deploy applications to the environment
Front-End nativebuilder.api.outsystems.com 443 TCP Generate mobile apps (more info)
Front-End Controller 12000 TCP OutSystems Deployment Controller Service connection
Front-End SQL Server / Oracle / MySQL  1433 / 1521 / 3306 TCP Database connection
Controller Front-End
 
12001  TCP OutSystems Deployment Service connection 
Controller SQL Server / Oracle / MySQL 1433 / 1521 / 3306 TCP Database connection

The following table lists the ports that should be open to correctly monitor OutSystems. A failure on opening these ports may result in warnings and error messages.

Source  Destination Port Protocol Notes
Front-End  Front-End  80 TCP IIS Monitoring
Front-End  Controller 12000 TCP OutSystems Deployment Controller Service Monitoring 
Front-End  Front-End  12001 TCP OutSystems Deployment Service Monitoring
Front-End  Front-End  12002 TCP OutSystems Scheduler Service Monitoring 
Front-End  Front-End  12003 TCP OutSystems Log Service Monitoring
Front-End  Controller 12003 TCP OutSystems Log Service Monitoring
Front-End  Front-End  12004 TCP OutSystems SMS Connector Service Monitoring
Controller Front-End  80 TCP IIS Monitoring 
Controller Front-End  12001 TCP OutSystems Deployment Service Monitoring
Controller Front-End  12002 TCP OutSystems Scheduler Service Monitoring 
Controller Front-End  12003 TCP OutSystems Log Service Monitoring 
Controller Front-End  12004 TCP OutSystems SMS Connector Service Monitoring

In case you are using a hybrid infrastructure, where some part is in OutSystems PaaS and another is managed by yourself, it is possible to create a VPN connection between the environments. Learn more here

Network latency 

Even though OutSystems is built to scale horizontally, you need to consider the network latency between the database server, the Platform Server, and the front-end servers. For this reason, it’s advisable to have all servers that make up an environment, running under the same provider.

As an example, if you are using Amazon RDS as your database server and running the Platform Server on your own infrastructure, the application’s performance will be degraded.

Network infrastructure requirements

To use LifeTime to manage your application lifecycle, you need to have bidirectional communication between the front-end of the LifeTime environment, and all other front-ends of your OutSystems Infrastructure. 

In case HTTPS is not supported, LifeTime communicates with the environments it manages by HTTP.

Applications must be deployed as follows:

Source Destination Port Protocol
LifeTime Front-End Environment Front-End  80 TCP
443
Environment Front-End  LifeTime Front-End  80 TCP
443

 

  • Was this article helpful?