Skip to main content

Managing the Applications Lifecycle



Initial Setup of an Infrastructure

This topic describes how to set up OutSystems with the following environments:

  • Development: where all continuous development is made;
  • Quality Assurance: where applications are tested for quality, acceptance, integration, etc.;
  • Pre-Production: which is always synchronized with Production, to make it easy to apply hotfixes;
  • Production: where the final application is deployed to and used by end-users.

Each one of these environments has more security restrictions than the previous: all IT users have access to Development, few have access to Quality Assurance, and only very few have access to Production.

In this example a new infrastructure with several environments is going to be created.

Create a New Infrastructure

A new infrastructure is set up by registering the environments in which you installed OutSystems into the infrastructure management console. Typically the environments are Development, Quality Assurance, and Production.

Start by the Development environment: type the environment address and click on 'Register'.

When registering an environment that has just been installed, there are not any registered IT Users on that environment, so nothing needs to be done.

Import Existing IT Users

In upgrade scenarios, where there are IT Users registered in the environments, two situations can occur:

  • The username of an IT user does not exist: the IT user is imported and it is asked to assign a default role, normally the role with lowest permissions;
  • The username of an IT user already exists: the IT user is not imported because it already exists in the infrastructure management console with security settings and password already set.

Another situation occurs when the same IT user has different usernames in different environments. OutSystems creates a new IT user, since there are different usernames in each environment. To avoid this situation, validate that the same IT user has the same username across all environments, before starting registering environments.

After IT users are imported, click again on 'Register' and the Development environment is now created.

Further Steps After Registering Development

In upgrade scenarios, where applications are already deployed in the environment, you must group all modules into applications:

  • Go to the development environment (Service Studio) and group all modules (eSpaces and extensions) into applications: create new applications and move the modules to the newly created applications;
  • Set up the environment security: create the adequate roles and grant application permissions to the registered IT users. Learn more about Typical Security Policies for an Infrastructure.

Register Additional Environments

If your factory has more than three environments, they should be registered in the same order they are used in the factory workflow. As an example you should register Development, Quality Assurance, Pre-Production and Production in this order.

To add new environments, simply click 'Register another environment' and follow the same steps used to register the Development environment. Even though OutSystems suggests naming your environments as Development, Quality and Production, you can click on 'Edit' and change the name of the environment. This way you can for example rename from 'Quality Assurance' to 'Test'.

Be sure to register each environment only once. If you try to register the same environment twice, or have two different LifeTime installations managing the same environment, an error is displayed. Learn more about LifeTime Installation and Configuration.

Manage the Infrastructure

Environments are managed in the 'Infrastructure' tab.

On each registered environment there are the following links to the environment management console:

  • Environment Health: the health status information of the current environment;
  • Configuration: configure the environment's properties.

To add or remove environments proceed as follows:

  • Add an Environment: click on 'Manage Infrastructure' and then on 'Register Another Environment' and follow the instructions described in step 1;
  • Remove an Environment: click on 'Manage Infrastructure' and then on the 'Unregister Environment' link.
  • Was this article helpful?