TECHNICAL NOTE

Agile Platform 5.1

Systems Requirements

The Agile Platform architecture has been designed with a strong focus on performance,
scalability, and high-availability. This technical note describes the Agile Platform logical
and physical architectures, as well as the systems requirements you need to fulfill to set
it up.

Table of Contents
1 Infrastructure and Environments ................................................................................................. 2

2 Service Studio & Integration Studio Requirements ...................................................................... 2

3 Platform Server Requirements .................................................................................................... 3

3.1 Scenario 1 – Small Installations ........................................................................................................................................................... 3
3.1.1 Production Environment ............................................................................................................................................................ 3
3.1.2 Quality Environment .................................................................................................................................................................. 3
3.1.3 Development Environment ........................................................................................................................................................ 4
3.2 Scenario 2 – Medium/Large Installations ............................................................................................................................................ 4
3.2.1 Production Environment ............................................................................................................................................................ 4
3.2.2 Quality Environment .................................................................................................................................................................. 5
3.2.3 Development Environment ........................................................................................................................................................ 5

4 Add-ons Requirements ............................................................................................................... 5

4.1 Microsoft SQL Server Integration Services ......................................................................................................................................... 5
4.2 Oracle Database Integration Services ................................................................................................................................................. 5
4.3 SAP Integration Services ..................................................................................................................................................................... 6
4.4 Multilingual ............................................................................................................................................................................................ 6
4.5 SMS ...................................................................................................................................................................................................... 6
4.6 Business Process Technology (BPT) .................................................................................................................................................. 6

5 Network Requirements................................................................................................................ 6
5.1 Default ports used by OutSystems Services ....................................................................................................................................... 6
5.2 Mandatory IIS port mappings ............................................................................................................................................................... 7
5.3 Connectivity needs – map of open ports ............................................................................................................................................. 7
5.4 A note about Platform Monitoring and nodes’ IP addresses............................................................................................................... 8

6 End-User Requirements.............................................................................................................. 9

© 2001-2010 OutSystems - All rights reserved Page 1 / 9 www.outsystems.com

1 Infrastructure and Environments
Developing applications in the Agile Platform typically requires having an infrastructure which comprises the
following environments:
Development Environment. In development you create accounts for all developers and development
managers of the Development Team. The Development environment is where Service Studio and
Integration Studio are typically used.
Quality Environment. In quality environment is where Testers and Business Users experiment the
production candidate applications or the application versions resulting from (agile) sprints. There are
very little scalability and redundancy requirements.
Production Environment. In production, full control is given to the Operations team but is advisable to
setup read-only access accounts for development/maintenance teams to have access to analytics
information on performance and application errors.
Configure the installation of these environments to obtain the infrastructure that better suits your needs -
among the spectrum of OutSystems customers we can find tens of variations.
To take a decision, it is important to understand the Agile Platform components: Service Studio tool,
Integration Studio tool, and Agile Platform server. The first two are the Platform’s development applications,
typically used by your development team members in their desktops, while the server is the Platform’s
application delivery and management engine, which may require a more powerful server machine and
software depending on your performance and scalability requirements.

2 Service Studio & Integration Studio Requirements

Agile Platform’s Service Studio and Integration Studio development applications require the following
configuration of your desktops:
Hardware Software

1 Intel Pentium IV-compatible 2 GHz Operating Systems:

processor Microsoft Windows Server 2003 (with Service Pack 1 or later), or
1 GB RAM Microsoft Windows Server 2008 R2, or
400 MB of hard-disk space Microsoft Windows XP Home or Professional (with Service Pack 2 or later), or
Microsoft Windows Vista, or
Windows 7
Internet Explorer 7.0 or 8.0
Microsoft .NET Framework 3.5 Service Pack 1 (SP1)

Required software to develop Extensions with Integration Studio

Platform Server .NET stack

Microsoft Visual Studio 2008 Standard Edition to edit the source code of the Extension Actions.
To edit SAP Wizard use higher editions than the Standard Edition of the Microsoft Visual Studio 2008.

© 2001-2010 OutSystems - All rights reserved Page 2 / 9 www.outsystems.com

3 Platform Server Requirements
The Platform Server can be configured with different physical architectures to cope with different scalability,
performance, reliability, and security requirements. The following scenarios represent the most common
scenarios when using the Platform:
Small Installations: single team (<5 developers), one project, limited enterprise reach.
Medium/Large Installations: multiple teams (> 5 developers), multiple apps, enterprise scalability.

3.1 Scenario 1 – Small Installations

3.1.1 Production Environment

Hardware Software (.NET stack)

Front-end Server (P1)

CPU Intel® Dual Core processors at 2.0GHz Microsoft Windows Server 2003 Standard Edition (32 or 64-bit), or
with 2MB L2 cache (32 or 64-bit) Microsoft Windows Server 2008 R2 Standard Edition (64-bit)
4 GB RAM
2 x SAS 73 GB Disk Drives as RAID 1

Database Server (P2)

CPU Intel® Dual Core processors at 2.0GHz Microsoft SQL Server 2005 Standard Edition (32 or 64-bit), or
with 2MB L2 cache (32 or 64-bit) Microsoft SQL Server 2008 Standard Edition (32 or 64-bit), or
4 GB RAM Oracle 10g R2 Standard Edition (32 or 64-bit), or
2 x SAS 73 GB Disk Drives as RAID 1 for Oracle 11g R2 Standard Edition (32 or 64-bit).
System Files (Operating System) and Log files
(*.ldf)
4 x SAS 146 GB Disk Drives as RAID 10 for
Data Files

3.1.2 Quality Environment

Hardware Software (.NET stack)

Front-end Server (Q1)

CPU Intel® Dual Core processors at 2.0GHz
with 2MB L2 cache (32 or 64-bit)
4 GB RAM
1 x SAS 146 GB Disk Drive
Microsoft Windows Server 2003 Standard Edition, or
Microsoft Windows Server 2008 R2 Standard Edition
Microsoft SQL Server 2005 Standard Edition (32 or 64-bit), or
Microsoft SQL Server 2008 Standard Edition (32 or 64-bit), or
Oracle 10g R2 Standard Edition (32 or 64-bit), or
Oracle 11g R2 Standard Edition (32 or 64-bit).

© 2001-2010 OutSystems - All rights reserved Page 3 / 9 www.outsystems.com

3.1.3 Development Environment
Hardware Software (.NET stack)

Front-end Server (D1)

CPU Intel® Dual Core processors at 2.0GHz
with 2MB L2 cache (32 or 64-bit)
4 GB RAM
1 x SAS 146 GB Disk Drive
Microsoft Windows Server 2003 Standard Edition, or
Microsoft Windows Server 2008 R2 Standard Edition
Microsoft SQL Server 2005 Standard Edition (32 or 64-bit) , or
Microsoft SQL Server 2008 Standard Edition (32 or 64-bit) , or
Oracle 10g R2 Standard Edition (32 or 64-bit), or
Oracle 11g R2 Standard Edition (32 or 64-bit)

3.2 Scenario 2 – Medium/Large Installations

3.2.1 Production Environment

Hardware Software (.NET stack)

Front-end Server (P1)

CPU Intel® Dual Core processors at 2.0GHz Microsoft Windows Server 2003 Standard Edition (32 or 64-bit) , or
with 2MB L2 cache (32 or 64-bit) Microsoft Windows Server 2008 R2 Standard Edition (64-bit)
4 GB RAM
2 x SAS 73 GB Disk Drives as RAID 1

Deployment Controller Server (P2)

CPU Intel® Dual Core processors at 2.0GHz Microsoft Windows Server 2003 Standard Edition (32 or 64-bit) , or
with 2MB L2 cache (32 or 64-bit) Microsoft Windows Server 2008 R2 Standard Edition (64-bit)
4 GB RAM
1 x SAS 146 GB Disk Drive

Database Server (P3)

CPU Intel® Dual Core processors at 2.0GHz Microsoft SQL Server 2005 Enterprise Edition (32 or 64-bit), or
with 2MB L2 cache (32 or 64-bit) Microsoft SQL Server 2008 Enterprise Edition (32 or 64-bit), or
4 GB RAM Oracle 10g R2 Standard Edition (32 or 64-bit), or
2 x SAS 36 GB Disk Drives as RAID 1 for Oracle 11g R2 Standard Edition (32 or 64-bit).
System Files (Operating System)
300 GB Storage for Log files (*.ldf) and Data
Files (*.mdf)

© 2001-2010 OutSystems - All rights reserved Page 4 / 9 www.outsystems.com

3.2.2 Quality Environment
Hardware Software (.NET stack)

Front-end Server (Q1)

CPU Intel® Dual Core processors at 2.0GHz Microsoft Windows Server 2003 Standard Edition (32 or 64-bit) , or
with 2MB L2 cache (32 or 64-bit) Microsoft Windows Server 2008 R2 Standard Edition (64-bit)
4 GB RAM
1 x SAS 146 GB Disk Drive

Database Server (Q2)

CPU Intel® Dual Core processors at 2.0GHz Microsoft SQL Server 2005 Enterprise Edition (32 or 64-bit), or
with 2MB L2 cache (32 or 64-bit) Microsoft SQL Server 2008 Enterprise Edition (32 or 64-bit), or
4 GB RAM Oracle 10g R2 Standard Edition (32 or 64-bit), or
1 x SAS 300 GB Disk Drive Oracle 11g R2 Standard Edition (32 or 64-bit).

3.2.3 Development Environment

Hardware Software (.NET stack)

Front-end Server (D1)

CPU Intel® Dual Core processors at 2.0GHz Microsoft Windows Server 2003 Standard Edition (32 or 64-bit) , or
with 2MB L2 cache (32 or 64-bit) Microsoft Windows Server 2008 R2 Standard Edition (64-bit)
4 GB RAM
1 x SAS 146 GB Disk Drive

Database Server (D2)

N.B. this server is shared with the Quality
environment. The specifications are identical to
those detailed above for the Database Server (Q2).

4 Add-ons Requirements
If you are planning to use one or more Agile Platform’s Add-ons take into account their specific
requirements, in addition to the requirements you have determined so far for your Agile Platform installation
scenario.
For additional information about Agile Platform’s Add-ons, please refer to the Agile Platform Editions
webpage on the OutSystems website.

4.1 Microsoft SQL Server Integration Services

Integrate with existing Microsoft SQL Server databases making their content available to be used in your
applications. You may integrate with the following databases:
Microsoft SQL Server 2005, or
Microsoft SQL Server 2008.
There are no additional requirements for this Add-on.

4.2 Oracle Database Integration Services

Integrate with existing Oracle databases making their content available to be used in your applications. You
may integrate with the following databases:
Oracle 10g R2, or
Oracle 11g R2.
This Add-on requires the Oracle Client Tools (10g R2 or 11g R2) to be installed in all Front-End and
Deployment Controller server machines.

© 2001-2010 OutSystems - All rights reserved Page 5 / 9 www.outsystems.com

4.3 SAP Integration Services
Create your own integration adapters to retrieve and submit data to SAP making it available to be used in
your applications.
This Add-on is only available for 32-bit operating systems, and requires either Visual Studio 2005 or Visual
Studio 2008 to be installed in all Front-End server machines. However, if you intend to use Visual Studio
2008 you have to install and use Rafael My SAP Proxy for Visual Studio 2008.

4.4 Multilingual
Translate your applications into multiple languages; in Service Studio add, edit, filter, import and export your
resources for translation.
There are no additional requirements for this Add-on.

4.5 SMS
Design your applications in Service Studio to interact with SMS messages.
You have to install Kannel 1.4.1 or 1.4.3 in a separate machine, or, alternatively, develop a custom SMS
Gateway Adapter (see how in the Third-party SMS Gateway Integration technical note).

4.6 Business Process Technology (BPT)

Design business processes in Service Studio whenever a process-centric development approach is required.
From enterprise-wide workflows to complex back-office operations, center your application development
efforts on business processes design and modeling, continuously integrating them with your underlying
applications artifacts such as, user interfaces and data elements.
There are no additional requirements for this Add-on.

5 Network Requirements
The Agile Platform is frequently deployed in environments with tight security measures. To keep up with the
network security levels regarding communications, only the necessary network TCP ports should be open.
The Agile Platform framework uses: a set of OutSystems Services that perform the communication between
the Platform’s components; a database server which stores both Platform’s metadata and applications’ data;
and Microsoft Internet Information Services (IIS) as application server. All of these communicate over TCP.
In the following sections are described the default port bindings used by OutSystems Services, the
mandatory port bindings for IIS, and all the connectivity needs to ensure proper functioning of overall Agile
Platform. This information applies to Agile Platform 5.1, running over IIS (.NET stack), and using either
Oracle or SQL Server databases.

5.1 Default ports used by OutSystems Services

The list below contains the default ports used by OutSystems Services. These can be changed if necessary:
12000 – OutSystems Deployment Controller Service;
12001 – OutSystems Deployment Service;
12002 – OutSystems Scheduler Service;
12003 – OutSystems Log Service;
12004 – OutSystems SMS Connector.

© 2001-2010 OutSystems - All rights reserved Page 6 / 9 www.outsystems.com

Ports used by OutSystems Services can be changed in the Configuration Tool, in the appropriate tab:

5.2 Mandatory IIS port mappings

Due to the way OutSystems Services interact with IIS, the following must be configured in IIS to prevent
runtime errors and application misbehaviors:
The eSpaces are always deployed to the default web site (identifier: 1);
Default Web Site must at least listen on:
o Address: 127.0.01
o Port: 80
o Host headers: <none>
In the server, localhost must resolve to 127.0.0.1 (IPv4);
In case of having multiple address entries in Default Web Site, the above configuration for the Default Web
Site (127.0.0.1:80, no host headers) must be set to be at the top of all other entries.
In case of the applications are using HTTPS (enforced by OutSystems mechanisms), HTTPS must be
served in port 443.

5.3 Connectivity needs – map of open ports

In each server profile the ports that need to be open for Agile Platform to work correctly are described in the
table below. Values in green must be changed according to custom changes made in the OutSystems
Services and database server configurations; values in red should not be changed, i.e., use the presented
value.

© 2001-2010 OutSystems - All rights reserved Page 7 / 9 www.outsystems.com

If a server has both roles (Controller and Front-End), then consider the ports for both profiles on that server.
Publication and Runtime Connectivity
Source Destination Port Protocol Notes

Controller SQL Server / Oracle 1433 / TCP Database Connection

1521
12001
Controller Front-End TCP OutSystems Deployment Service connection

Front-End SQL Server / Oracle 1433 / TCP Database Connection

1521
Front-End Controller 12000 TCP OutSystems Deployment Controller Service connection

Users Front-End 80 TCP Application's HTTP access

Users Front-End 433 TCP Application's HTTPS access

The following table lists the ports that should be open to correctly monitor Agile Platform (Platform
Monitoring). A failure while opening these ports may result in unwanted warnings and error messages, even
though they may not indicate a malfunction of the OutSystems Services.
Monitoring Connectivity
Source Destination Port Protocol Notes

Controller Front-End 12001 TCP OutSystems Deployment Service Monitoring

Front-End Controller 12000 TCP OutSystems Deployment Controller Service Monitoring

Front-End Controller 12003 TCP OutSystems Log Service Monitoring

Front-End Front-End 80 TCP IIS 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 Front-End 12004 TCP OutSystems SMS Connector Service Monitoring

5.4 A note about Platform Monitoring and nodes’ IP addresses

When using Platform Monitoring in Service Center, the following behaviors are displayed:
The status of the communications from a Front-end node to each port (from the ones described above).
This is listed for all the Front-end nodes present in Platform Monitoring;
The status of the communications made over the IP address for which the Front-end node is registered
and active in Service Center.
If the communication through the combination IP/Port is not possible, Platform Monitoring will visually display
this impossibility to communicate with the service. Take a look at the example below:

In this example, we are accessing Platform Monitoring on the OSFrontEnd01

(http://192.168.1.101/ServiceCenter). This front-end is in the same subnet as OSController and
OSFrontEnd02, but the DMZ node OSDMZ apparently has a completely different IP address. This happened

© 2001-2010 OutSystems - All rights reserved Page 8 / 9 www.outsystems.com

 because the server registered itself with the external IP address 83.16.126.208 instead of using its internal
IP address is in the same subnet, 192.168.1.103.
By looking at Online Monitoring, you see what appears to be a completely offline Front-end node, but in fact
the problem is simply that OSFrontEnd01
cannot communicate to OSDMZ in the
appropriate ports using that IP address – if the
Front-end node was registered with its internal
IP address, communication would be possible.
To change the IP address that a Front-end
node uses when is registered in the controller,
simply change the appropriate setting in the
Configuration Tool and restart Deployment
Service. Once the service is operational, you
would see a fully-green Platform Monitoring
screen (unless there was, in fact, something
wrong with that node).

6 End-User Requirements
To use an application developed with the Agile Platform requires end-users to have one of the following
Internet browsers installed in their machines:
Browser
Internet Explorer 6.0 (Service Pack 1 or higher), Internet Explorer 7.0, or Internet Explorer 8.0, or
Firefox 3.0 or 3.5, or
Chrome 2.0 or 3.0

More information

If you would like to have more information about OutSystems and its products please contact our regional offices:

OutSystems US OutSystems Benelux OutSystems Portugal

2603 Camino Ramon, Suite 200 Planetenbaan 16 Rua Central Park 6, 2A
San Ramon, California 94583 - USA 3606 AK Maarssen - The Netherlands 2795-242 Linda-a-Velha - Portugal
Tel: +1 925 242 2512 Tel: +31(0) 346 583 000 Tel: +351 21 4153730
Fax: +1 925 242 2898 Fax: +31(0) 346 590 201 Fax: +351 214153731
info@outsystems.com info.nl@outsystems.com info.pt@outsystems.com

© 2001-2010 OutSystems - All rights reserved Page 9 / 9 www.outsystems.com