Skip to main content
OutSystems

Configure the infrastructure management console

OutSystems Platform has a centralized management console that allows managing your environments, applications, security, and more. Learn how to configure the infrastructure management console.

Logging in the infrastructure management console for the first time

After you have installed LifeTime, open it in your browser using the http://<your_server>/lifetime URL. 

If you are installing OutSystems Platform for the first time, use the default credentials (admin/admin), and change the credentials. If you are upgrading from a previous version of OutSystems Platform, you may use Service Center administrator credentials to login into LifeTime.

Since in LifeTime the scope of roles is across environments, it is recommended that you review the users which should remain with Administrator role after importing environments. For example, a user with Administrator role in Development is also an administrator in Production.

Creating new roles

Service Center Roles are not imported when a new environment is imported to LifeTime. This is due to a difference in granularity and scope of roles in LifeTime. Therefore, you must rethink the security policy of the infrastructure.

Comparing Service Center and LifeTime roles

An IT User in LifeTime can only have one role which specifies the IT user permissions in every environment of the infrastructure. IT user permissions can be further configured by granting specific permissions per application in each of the environments.

Example 1

John Penn is an external developer and only needs permissions to publish the Mobile Sales in the Development Environment.

Permissions in Service Center

Create a role for Mobile Sales developers in the Development Environment. Assign John Penn that role.

Permissions in LifeTime

Create an External Developer role that does not have permissions in any environment, and assign John Penn with that role. Then increase John's permissions for the Mobile Sales application, letting him change and deploy that application in Development.

 

Example 2

Lisa Carlson also works on the Mobile Sales team. She is able to deploy to Development and Quality Assurance.

Permissions in Service Center

Create a role for Mobile Sales developer in the Quality Assurance environment, with the same permissions of that role in Development. In each environment assign Lisa with that role.

Permissions in LifeTime

Assign Lisa the external developer rolea and increase her permissions for the Mobile Sales application, letting her deplou in both Development and Quality Assurance.

 

Example 3

The architecture team decides to add one more module to the Mobile Sales application. The permissions must be updated to let the developers change that module.

Permissions in Service Center

In Development and Quality Assurance, change the Mobile Sales developer role to include permissions for the new module.

Permissions in LifeTime

Since the permissions are managed by application, nothing needs to be changed.

Creating new roles in LifeTime

By default, LifeTime has two built-in roles: Administrator and Developer, to address the simplest infrastructure security configuration: a single team developing all applications and an IT administrator responsible for managing the infrastructure.

If you need to enforce more complex security policies across the infrastructure, you need to create new and specific roles for IT users in LifeTime. Check the OutSystems Platform documentation to learn how to create new roles.

You can create new roles at any time in Life Time and every IT user must have a role associated.

When importing environments, if you already know which roles IT users will have, it is much easier to create those roles beforehand. Then, in the process of adding an environment, LifeTime asks you to choose the role for imported users, and having them already created allows you to set them right on that moment and in a single place. If you choose not to create your roles beforehand, you’ll have to select one of the default roles, and later on create the roles and edit each imported IT user and set the right role for him.

To create new roles, simply go to the Users & Roles tab, click on New Role and set the role name. In the next section, environments are registered and you configure the specific permissions of the role for each environment.

lifetime-new-role.PNG

Register an environment

The environments must 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 environments in LifeTime by this order. This ensures that all other environments catch up the application definition from the Development environment and that the synchronization between LifeTime and the environments is correctly performed.

Starting with the Development environment: type the address of the machine that hosts the Platform Server for the Development environment and click on Register

lifetime-register-environment.PNG

LifeTime logs in to the environment using the credentials of the user that is currently logged in and doing the operation. In case this user has no administrator permissions in the environment, LifeTime asks for the right credentials.

Next, LifeTime checks whether the environment being registered can respond to LifeTime requests. In the example above, it checks if the srvdev.mydomain.com environment can be contacted. If it is not possible, LifeTime asks for an alternative address (LifeTime External Address) through which LifeTime can be reached.

If you have setup a firewall rule to allow your environments to reach LifeTime at srvprod.mydomain.com:8088, then this is the value to be used. For more information on setting up LifeTime, or how to configure the security of your infrastructure, see the OutSystems Platform reference documentation.

Specifying permissions for custom roles 

When LifeTime is able to establish communication with an environment, the registration process continues. In case you have already created custom roles in LifeTime, you must configure those roles permissions for the new environment you are registering. 

lifetime-permissions-1.PNG

For each role, click on the Permissions link and change the current permissions in the new environment.

lifetime-permissions-2.PNG

Importing IT users

In this step, LifeTime asks you to set the role for the users imported from the environment you are adding.

lifetime-importing-users.PNG

In case an IT user already exists in LifeTime, a role is already set for that IT user and you have to do nothing because a Role in LifeTime applies to all environments including the new environment you are creating.

Background synchronization

When you finish importing IT users and click Next, LifeTime starts synchronizing the environments in background. Given that the synchronization process might take several minutes, your applications will slowly appear in the Applications area.

lifetime-background-sync.PNG

Adding other environments

To add more environments to the three predefined ones (Development, Quality Assurance, and Production), simply click on Register Another Environment and follow the same steps used to register the Development environment.

After the environment is imported, you can move and place it in the right order in the sequence of environments. Do this by clicking in the arrows placed between environments. When you are finished press the Setup Done! button. Finally, LifeTime allows you to change the name of an environment by clicking on Manage Environments and then on the Edit link of the environment.

You can also change the order of the environments by clicking the arrow between environments to change their order.

Moving LifeTime to another environment

You may wish to move LifeTime to a different environment if you initially were sharing LifeTime with a different role (e.g. Development or Production) and wish to move LifeTime to another environment.

As a best practice, OutSystems recommends hosting LifeTime in a dedicated Environment.

Moving Lifetime will cause the loss of some information like history of previous deployments and performance monitor metrics. You will not lose any application versions or application data in the environments controlled by LifeTime.

Preparation:

  1. Export a list of users with their roles and the definition of each role from LifeTime. You may wish to use the web browser Export/Print feature for convenience. This list is only needed for confirmation of correct move after the process is complete. 

Moving LifeTime:

  1. Backup the full database of all environments (LifeTime and all environments managed by them). You may need them in case you need to roll back for some reason.
  2. Install the new environment. Remember that, as a best practice, OutSystems recommends using a separate, empty environment with the single purpose of hosting LifeTime.
  3. Confirm that you have access to the password of the admin user in LifeTime. You may need it in the following steps.
  4. Unregister all environments from the current LifeTime installation.
  5. Register all environments in the new LifeTime. We recommend you register the environments by the order they are to appear in the staging sequence.

Post-move:

  1. Confirm that all users and role definition were correctly synchronized across environments. If needed, adjust user privileges in LifeTime.
  2. In the environment that hosted LifeTime before the move, access ServiceCenter and Bring Offline the LifeTime application. That way, you prevent that end users may try to access and/or register environments in the old LifeTime environment. 

Notes:

Moving LifeTime is a sensible operation; performing it incorrectly may cause LifeTime to stop working properly or cause data loss.

If you are not comfortable in performing this operation on your own, we recommend reaching out to your OutSystems account manager to find out about options for having OutSystems perform the move for you.

Language options

The default language of LifeTime is English, but you have the possibility to change it to Japanese, or Portuguese (Brazil). To do so, open the Service Center on the environment where LifeTime is installed, and set up the following Site Properties in the LifeTimeCore module: 

  • EnableLocale: set it to true to activate the translations.
  • Locale: choose either ja or pt-BR. If this site property is left empty, LifeTime screens are displayed according to the end-user browser preferences.