This article explains the several components of OutSystems. It also explains how to set up OutSystems on the cloud or on-premises.
OutSystems has the following components:
- Platform Server: The component that orchestrates all runtime, deployment, and management activities for all applications. This tool is installed in each environment.
- LifeTime: This is the console for managing the infrastructure, environments, applications, IT users, and security. This web application is typically deployed to its own dedicated environment in the infrastructure.
- Service Center: The administration console for an environment of the infrastructure.
- Service Studio: The visual development tool to create, change, and deploy your applications. This tool is installed in the developers desktop.
- Integration Studio: The development tool to create connectors to integrate OutSystems applications with other enterprise systems. This tool is installed in the developers desktop.
OutSystems covers the full application lifecycle, from development to deployment. For this reason, a typical OutSystems infrastructure has four environments:
Development Environment: The environment where applications are initially developed and tested.
Quality Environment: The environment where testers and business users experiment applications to perform quality assurance. This environment usually has few scalability and redundancy requirements.
Production Environment: The environment that hosts the application version end-users are interacting with. Usually, this environment is only accessible by the operations team.
Management Environment: Given the requirements of the infrastructure management console, this application usually runs on a dedicated environment. Learn how to size an environment for the infrastructure management console.
You can have these four environments on the cloud, on-premises, or with a hybrid configuration, where some are one the cloud, and some on-premises. Learn more about the possible OutSystems infrastructure configurations.
If you're using OutSystems PaaS, you don't need to worry about installing or licensing your infrastructure. Once you receive your OutSystems PaaS it is ready for you to develop your apps.
If you're installing OutSystems on-premises, be sure you have a valid activation code, or license files. Without them you won't be able to deploy applications to your environments. So be sure to check how OutSystems licensing works.
If you selected to setup OutSystems infrastructure using our Cloud offering you do not have to do any of the initial Platform Setup Yourself. Your Servers will be automatically setup for you and you will receive an email with access details such as address and usernames.
Nevertheless, when managing a single Environment or infrastructure on the OutSystems cloud, you should take into account the following considerations:
- Currently, our cloud provider (Amazon) does not support customizing the time zone for SQL Server. Conversions need to be done programmatically from UTC to the desired time zone.
- Custom database objects such as stored procedures are not supported. You can either implement the same logic using “Advanced Queries” (standard SQL) or through Extensions (by implementing your own C# code).
- The Multiple Database Catalogs and Schema feature is not available. This means that all applications store their data in the same database Catalog/Schema.
- The Zones feature is not available. All applications running on an environment are available in all front-end servers of that environment. However, applications can be set up to only be accessible from the internal network.
- Using the built-in SMS mechanism is not supported. You can send SMS’s by using Extensions available in OutSystems Forge.
If you selected to have some of you Environments hosted in our Cloud and the rest in your Datacenter, you should setup your on-premises environments as described in the next section and then add them to the infrastructure management console (LifeTime) we provide as part of the cloud installation.
An on-premises OutSystems infrastructure is located on the customer’s datacenter and is managed by the customer.
Before installing any component of OutSystems, make sure your hardware and software comply with the minimum requirements. For this, be sure to check:
- System requirements: the supported hardware and software for installing OutSystems;
- Network requirements: the network requirements for an environment where OutSystems is installed;
- Default Platform Server and database configurations: to install and run OutSystems, you need permission to change files in the file system, run services, and make changes to the database.
To install OutSystems in your infrastructure:
- Download the installation binaries;
- Install the Platform Server in each environment you have;
- Install the infrastructure management console;
- Configure the infrastructure management console;
- Install and configure the development tools.
Download the installation binaries
If you're looking for a specific OutSystems version, be sure to check the downloads repository.
Install the Platform Server
The infrastructure management console (Lifetime) is typically installed on a dedicated environment. Be sure to also follow the installation checklist for that environment.
Install the infrastructure management console
The installation checklist has instructions to install the infrastructure management console on its dedicated environment.
Be sure to follow the installation checklist, and only install the management console on one environment. Installing the management console on several environments might make it unable to communicate with all the environments you have.
Configure the infrastructure management console
Now it's time to configure the infrastructure management console. This will allow you to register the several environments you have, so that you can manage them from a centralized console.
Install and configure the development tools
OutSystems is now ready for you to start developing. The only thing missing is to install the development tools on your developers' desktops. Be sure to install a version of the development tools that is compatible with the version of the Platform Server installed in your environments.
After installing the development tools, configure them for developing your own extensions.