Skip to main content
OutSystems

Upgrade OutSystems Platform in OutSystems Cloud

This article explains how you can upgrade your OutSystems Platform in the OutSystems Cloud. You'll be able to assess the upgrade, understand its impacts, and plan it accordingly. 

Before you start

Make sure you checked the general guidelines in the Upgrade OutSystems Platform before proceeding. Then read this article to understand what is involved and what you should plan in advance.

Upgrading an OutSystems Platform environment may incur in downtime for that environment, or the applications hosted in it, depending on the impact of the breaking changes resulting of the upgrade. You can ask OutSystems Support for the expected downtime of your environment.

Overview

In the OutSystems Cloud, the overall upgrade process is managed by OutSystems, coordinating with you in every step of the way, to guarantee a successfully and as effortless as possible procedure, consisting of the follow high-level steps:

  1. You can request the upgrade of your OutSystems Cloud infrastructure to a supported upper version, by opening a Support Case using any of the available mechanisms;
  2. OutSystems will promptly contact you to schedule and plan the OutSystems Platform upgrade of each of the OutSystems Cloud environments:
    1. You and OutSystems will upgrade the Management Console environment. See section Upgrade the Management Environment for more details;
    2. You and OutSystems will upgrade the first OutSystems Cloud non-production environment, typically the Development Environment. See section Upgrade the Development Environment for more details;
    3. You and OutSystems will upgrade the remaining OutSystems Cloud environments. See section Upgrade the remaining Environment for more details;
    4. Keep updating your Support case with the requests to upgrade each of the environments, as the upgrade plan moves forward

If you have a hybrid configuration where your infrastructure is comprised of both on-premise and OutSystems Cloud environments, please see section Upgrade hybrid infrastructures in the OutSystems Cloud for more details.

Upgrade the infrastructure management console

In the OutSystems Cloud, the infrastructure management console is installed on a dedicated environment. This environment should be the first to be upgraded. This allows you to stage applications from one environment to the next, as you upgrade the next environments to the latest version.

OutSystems will upgrade this environment upon request. The overall steps are:

  1. Request OutSystems to begin the upgrade process of your OutSystems Cloud infrastructure;
  2. OutSystems will upgrade the Platform Server and the LifeTime components on the environment;
  3. If you have any LifeTime plugin deployed on this environment, you must upgrade the correspondent application in that environment. See Upgrading Applications in an OutSystems Platform environment for more details.

You're done, and ready to start upgrading the other environments.

Upgrade the development environment

The Development environment is usually the first OutSystems Cloud environment to upgrade after the Management Console (LifeTime) environment. If following the same staging order, this is were you'll upgrade the applications to the new version as well.

OutSystems will upgrade this environment upon request. The overall steps are:

  1. Request OutSystems to begin the upgrade process of your OutSystems Cloud Development environment, or the first non-production environment in the OutSystems Cloud;
  2. OutSystems will upgrade the Platform Server component on the environment;
  3. Your developers install the new release of the development tools (Development client tools in the downloads page) in their desktops;
  4. You upgrade and test all applications. See Upgrading Applications in the Development Environment for more details.

Upgrade the remaining environments

After upgrading the Development environment, proceed to upgrading the remaining environments in your infrastructure, preferably according to your staging order.

OutSystems will upgrade each environment upon request. The overall steps are:

  1. Request OutSystems to begin the upgrade process of your next OutSystems Cloud environment;
  2. OutSystems will upgrade the Platform Server component on the environment;
  3. If they haven’t already, your developers install the new release of the development tools (Development client tools in the downloads page) in in their desktops;
  4. You deploy all applications from the Development environment to the environment you are upgrading, using Lifetime, the Platform management console.

Upgrading hybrid infrastructures in OutSystems Cloud

In case you have a hybrid infrastructure, i.e. some environments running in OutSystems Cloud and some environments running in your own private cloud or datacenter, OutSystems will only upgrade the environments in the OutSystems Cloud. For you to upgrade your private cloud or datacenter environments, please refer to the Upgrade OutSystems Platform in your datacenter article.

Doing maintenance while upgrading environments

While upgrading, if you need to do some bug fixing in an application that's running on an environment that hasn't been upgraded, you'll need to do it on that environment. It won't be possible to go through the usual development-production pipeline, because you can't stage applications between environments in different versions.

The solution is to make the fix directly in the environment that is not yet upgraded.


As an example, imagine that you already upgraded Development and Test environments. There are still Pre-Production and Production environments  to be upgraded. You have to do a critical fix on an application in Production. In this case, use the development tools in Pre-Production to do the fix, to publish and test. Then, move the application to Production. Don’t forget to backport the fix to the other environments.

At any time, you can ask OutSystems Support for assistance.

Frequently Asked Questions

I have a VPN connection, will my connection be affected?

If you are upgrading to platform 10 from a version earlier than 9.1, the private IP addresses of your cloud environments will change.

This change is related to the migration of your cloud environments to a more recent operating system. Due to a technical limitation on our IaaS provider (Amazon Web Services), it is not possible to keep the current IP addresses. Your Cloud Private IP range will remain the same.

To address this, you need to replace all usages of the old internal IP address with the new one. OutSystems provides you the updated IP addresses after the environment has been upgraded.

I have an SSL certificate configured in my environments, will I need to reconfigure it?

If you are upgrading to platform 10 from a version earlier than 9.1.301.0, we've introduced new SSL/TLS features in this version. In this case, if you already have SSL/TLS activated in your environment, please read the following steps carefully.

After the upgrade, you'll have to configure your SSL certificates for your environments again. Please follow the steps in this knowledge base article.

After the upgrade of your Lifetime environment, you can start uploading the certificates for your remaining environments. Please note that you'll only be able to apply them to each environment after the upgrade has finished for that environment.

If you are using your own domain name to access the OutSystems platform, please read the entry below.

I am using my own domain name to access the OutSystems platform, instead of the originally provided IP / domain names. Do I need to change anything?

If you are upgrading to platform 10 from a version earlier than 9.1, OutSystems changed the way environments are made available on the internet and it affects how your domain name may be configured.

Previously, OutSystems provided you the public IP addresses of the front-ends (for non-Production environments) and a load balancer name (for Production environments). Your domain name was configured as a mapping to the public IP address (in DNS wording, an A record). Starting with this upgrade, OutSystems now provides endpoints in the form of yourcompany-environment.outsystemsenterprise.com.
To correctly configure your environment after the upgrade:

  • non-Production environments: you need to change the DNS entry, replacing the original mapping to the public IP address with a mapping to the yourcompany-environment.outsystemsenterprise.com provided to you (in DNS wording, using a CNAME entry);
  • Production environments: you should change the previous CNAME entry to the load balancer address to the new name yourcompany-environment.outsystemsenterprise.com provided to you. Load balancer names will be deprecated in the future, even though they continue working immediately after this upgrade. 

If you don't perform this step and you are using SSL certificates, they will stop working as the certificate is no longer connected to the original public IP.