TECHNICAL NOTE Agile Platform 6.0 System 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 system 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... 4 3.1.3 Development Environment... 4 3.2 Scenario 2 Medium/Large Installations... 5 3.2.1 Production Environment... 5 3.2.2 Quality Environment... 6 3.2.3 Development Environment... 6 3.3 Scenario 3 - Cloud Installation... 6 4 Software Requirements Essentials...7 5 Database Requirements...7 5.1 SQL Server... 7 5.2 Oracle... 7 6 Add-ons Requirements...7 6.1 Microsoft SQL Server Integration Services... 8 6.2 Oracle Database Integration Services... 8 6.3 SAP Integration Services... 8 6.4 Multilingual... 8 6.5 SMS... 8 6.6 Business Process Technology (BPT)... 8 7 Network Requirements...9 7.1 Default ports used by OutSystems Services... 9 7.2 Mandatory IIS port mappings... 10 7.3 Connectivity needs map of open ports... 10 7.4 A note about Platform Monitoring and nodes IP addresses... 11 8 End-User Requirements... 12 8.1 Web Browsers Requirements... 12 8.2 Mobile Devices Requirements... 12 Page 1 / 12
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 a desktop configuration equivalent to the following one: CPU Intel Dual-Core processor 1GB RAM (2 GB recommended) 500 MB of hard-disk space Software Windows 7; Microsoft Windows Vista; Microsoft Windows XP (with Service Pack 2 or later); Microsoft Windows Server 2008 R2; Microsoft Windows Server 2003 R2. Internet Explorer 7.0, 8.0, or 9.0 Required software to develop Extensions with Integration Studio Platform Server.NET Stack Any edition of Microsoft Visual Studio 2008 to edit the source code of Extension Actions. SAP Wizard requires Visual Studio 2008 Standard Edition or higher; Any edition of Microsoft Visual Studio 2010 to edit the source code of Extension Actions. SAP Wizard requires Visual Studio 2010 Professional Edition or higher. NOTE: editing an extension with a higher version of Visual Studio might prevent it from being edited in earlier versions, unless a manual Visual Studio project downgrade is performed. Network Connection Minimum speed of 1Mbps both for downloading and uploading. Page 2 / 12
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 are common when using the Agile 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 Software (.NET stack) Front-end Server (P1) CPU Intel Dual Core processor 40 GB of disk space (RAID 1 is advisable) Microsoft Windows Server 2008 R2 Standard Edition; Microsoft Windows Server 2003 R2 Standard Edition. Database Server (P2) CPU Intel Dual Core processor 40 GB of disk space (RAID 1 is advisable) Microsoft SQL Server database: Microsoft SQL Server 2008 R2 Express Edition; Microsoft SQL Server 2008 R2 Standard Edition; Microsoft SQL Server 2008 Express Edition; Microsoft SQL Server 2008 Standard Edition. Oracle database: Oracle 11g R2 Standard Edition; Oracle 10g R2 Standard Edition. Page 3 / 12
3.1.2 Quality Environment Software (.NET stack) Front-end Server (Q1) CPU Intel Dual Core processor 60 GB of disk space Microsoft Windows Server 2008 R2 Standard Edition; Microsoft Windows Server 2003 R2 Standard Edition. Database Management Systems (DBMS): Microsoft SQL Server database: Microsoft SQL Server 2008 R2 Express Edition; Microsoft SQL Server 2008 R2 Standard Edition; Microsoft SQL Server 2008 Express Edition; Microsoft SQL Server 2008 Standard Edition. Oracle database: Oracle 11g R2 Standard Edition; Oracle 10g R2 Standard Edition. 3.1.3 Development Environment Software (.NET stack) Front-end Server (D1) CPU Intel Dual Core processor 80 GB of disk space Microsoft Windows Server 2008 R2 Standard Edition; Microsoft Windows Server 2003 R2 Standard Edition. Database Management Systems (DBMS): Microsoft SQL Server database: Microsoft SQL Server 2008 R2 Express Edition; Microsoft SQL Server 2008 R2 Standard Edition; Microsoft SQL Server 2008 Express Edition; Microsoft SQL Server 2008 Standard Edition. Oracle database: Oracle 11g R2 Standard Edition; Oracle 10g R2 Standard Edition. Page 4 / 12
3.2 Scenario 2 Medium/Large Installations 3.2.1 Production Environment Software (.NET stack) Front-end Server (P1) CPU Intel Quad Core processor 100 GB of disk space (RAID 1 is advisable) Microsoft Windows Server 2008 R2 Standard Edition; Microsoft Windows Server 2003 R2 Standard Edition. Deployment Controller Server (P2) CPU Intel Quad Core processor 100 GB of disk space (RAID 1 is advisable) Microsoft Windows Server 2008 R2 Standard Edition; Microsoft Windows Server 2003 R2 Standard Edition. Database Server (P3) CPU Intel Quad Core processor Start with 100 GB of disk space (RAID 1 is advisable) Microsoft SQL Server database: Microsoft SQL Server 2008 R2 Standard Edition; Microsoft SQL Server 2008 R2 Enterprise Edition; Microsoft SQL Server 2008 Standard Edition; Microsoft SQL Server 2008 Enterprise Edition. Oracle database: Oracle 11g R2 Standard Edition; Oracle 11g R2 Enterprise Edition; Oracle 10g R2 Standard Edition; Oracle 10g R2 Enterprise Edition. Page 5 / 12
3.2.2 Quality Environment Software (.NET stack) Front-end Server (Q1) CPU Intel Quad Core processor 100 GB of disk space Microsoft Windows Server 2003 R2 Standard Edition; Microsoft Windows Server 2008 R2 Standard Edition. Database Server (Q2) CPU Intel Quad Core processor 100 GB of disk space Microsoft SQL Server database: Microsoft SQL Server 2008 R2 Standard Edition; Microsoft SQL Server 2008 R2 Enterprise Edition; Microsoft SQL Server 2008 Standard Edition; Microsoft SQL Server 2008 Enterprise Edition. Oracle database: Oracle 11g R2 Standard Edition; Oracle 11g R2 Enterprise Edition; Oracle 10g R2 Standard Edition; Oracle 10g R2 Enterprise Edition. 3.2.3 Development Environment Software (.NET stack) Front-end Server (D1) CPU Intel Quad Core processor 150 GB of disk space Microsoft Windows Server 2003 R2 Standard Edition; Microsoft Windows Server 2008 R2 Standard Edition. Database Server (D2) This server is shared with the Quality environment. The specifications are identical to those detailed above for the Database Server (Q2). 3.3 Scenario 3 - Cloud Installation The 6.0 version of the Agile Platform is 100% cloud-ready allowing you to develop and deploy your applications in a cloud infrastructure for the previously described scenarios, namely using one of the following cloud providers: For a detailed comparison on these cloud providers and suggestions about which server infrastructure to choose, please refer to the Cloud Providers Overview datasheet. Note: All logos are registered trademarks of their respective owners, in several countries. Page 6 / 12
4 Software Requirements Essentials This section summarizes the previous sections regarding the basic software for working with the Agile Platform. Operating Systems Service Studio & Integration Studio Windows 7; Microsoft Windows Vista; Microsoft Windows XP (with Service Pack 2 or later); Microsoft Windows Server 2008 R2 Standard Edition or higher; Microsoft Windows Server 2003 R2 Standard Edition or higher. Platform Server Microsoft Windows Server 2008 R2 Standard Edition or higher; Microsoft Windows Server 2003 R2 Standard Edition or higher. Database Management Systems (DBMSs) Microsoft SQL Server Microsoft SQL Server 2008 R2 Express Edition or higher; Microsoft SQL Server 2008 Express Edition or higher. Oracle Oracle 11g R2 Standard Edition or higher; Oracle 10g R2 Standard Edition or higher. 5 Database Requirements The database used by the Agile Platform has some specific configuration requirements. 5.1 SQL Server The SQL Server database must comply with the following requirements: Authentication must be mixed-mode (Windows Authentication + SQL Server Authentication). All database users for the runtime Agile Platform use SQL Server authentication only. The collation of the SQL Server instance must be case-insensitive (CI_*). 5.2 Oracle The Oracle database must comply with the following requirements: The only supported NLS_CHARACTERSET is WE8MSWIN1252. This setup requires the Oracle Client Tools (11g R2) to be installed in all Front-End and Deployment Controller server machines. 6 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 please refer to the Agile Platform Editions webpage on the OutSystems website. Page 7 / 12
6.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 2008, or Microsoft SQL Server 2008 R2 There are no additional requirements for this Add-on. 6.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 (11g R2) to be installed in all Front-End and Deployment Controller server machines. 6.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 works with SAP ERP R/3 4.7, SAP ECC 6.0 or higher and it is only available for 32 bit operating systems and 64-bit operating systems running IIS in 32 bit mode. It also requires Visual Studio 2008 or Visual Studio 2010 to be installed in all developer machines and to install and use Rafael My SAP Proxy for Visual Studio 2008 and 2010. 6.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. 6.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). 6.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. Page 8 / 12
7 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 6.0, running over IIS (.NET stack), and using either Oracle or SQL Server databases. 7.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. Ports used by OutSystems Services can be changed in the Configuration Tool, in the appropriate tab: Page 9 / 12
7.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. 7.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. 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 / 1521 Controller Front-End 12001 / 1521 TCP OutSystems Deployment Service connection Front-End SQL Server / Oracle 1433 / 1521 TCP Database Connection Front-End Controller 12000 / 1521 TCP OutSystems Deployment Controller Service connection TCP Database 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 Page 10 / 12
7.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 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). Page 11 / 12
8 End-User Requirements The Agile Platform allows developing applications that run in Web browsers and mobile devices with specific requirements. 8.1 Web Browsers Requirements End-users should run Agile Platform applications in one of the following Web browsers: Browser Internet Explorer 7.0, 8.0, or 9.0, or Firefox 3.0 or 3.5, or Google Chrome. 8.2 Mobile Devices Requirements End-users should run Agile Platform applications on mobile devices with one of the following operating systems: Browser ios 4+, or Android 2.1 +, or Blackberry 6 +, or Windows Phone 7. Page 12 / 12