Skip to main content

 

 

 

Template:OutSystems/Documentation_KB/Breadcrumb_New_Layout

 

Template:OutSystems/OSLanguageSwitcher
Language:

 

 

 

 

 
OutSystems

Upgrade LifeTime management console

This article describes the process to upgrade the LifeTime management console of your OutSystems infrastructure to Release Sep.2018 (11.0.108.0) or later, and what you must take into consideration during that process.

Keeping your LifeTime management console upgraded enables you to benefit from the latest features and fixes. OutSystems releases a new LifeTime version on a monthly basis.

Context

Up to version OutSystems 10, upgrading OutSystems to a new major version means upgrading all the infrastructure - LifeTime management console and the application environments.

From version OutSystems 11 onwards, LifeTime is distributed independently from the Platform Server, which enables both components to have different upgrading pace.

LifeTime Release Sep.2018 (11.0.108.0) marks the beginning of LifeTime's own release cycle, allowing better and faster improvements in your LifeTime management console.

Upgrading LifeTime to Release Sep.2018 or later does not require the upgrade of your OutSystems application environments. You can benefit from LifeTime latest features and still keep your application environments in a previous supported version while you need. Read more about which versions of Platform Server can LifeTime manage.

Before the upgrade

Check the breaking changes for LifeTime Management Console.

If you have LifeTime plugins deployed in your LifeTime environment or other integrations with this environment - applications or systems interacting directly with the environment through OutSystems APIs made available via REST or SOAP - you must do the following:

If you are running an OutSystems version that is not supported anymore, you first need to upgrade to a supported OutSystems version.

LifeTime upgrade process

OutSystems Cloud

In the OutSystems Cloud, the process of upgrading the LifeTime management console is managed by OutSystems, coordinating with you in every step of the way, to guarantee a successful and as effortless as possible procedure:

  1. You request the upgrade of your LifeTime management console 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 LifeTime management console upgrade.

  3. On the scheduled time frame, OutSystems will upgrade the LifeTime management console in your OutSystems Cloud infrastructure. During the upgrade, your LifeTime management console and any installed LifeTime plugins will be unavailable.

  4. You will receive a notification email when the upgrade is concluded.

  5. If you have LifeTime plugins or integrations, you should republish all plugins as described below.

Self-managed (private cloud / on-premises)

If the environment is self-managed (running in your own private cloud or on-premises) the upgrade process is fully managed by you, without the direct involvement of OutSystems. However, at any time you can ask OutSystems Support for assistance if you have any questions or get any errors in the process.​

To upgrade the LifeTime management console to Release Sep.2018 or later, the following requirements must be met:

  • Your OutSystems application environments are running a supported OutSystems version. If you are running an OutSystems version that is not supported, you must upgrade to a supported OutSystems version.

  • Your LifeTime management console is installed in a dedicated environment. If your LifeTime management console is installed in a shared environment (for example, in your production environment), you must reinstall LifeTime in a dedicated environment.

After assuring the above requirements are met, do the following to upgrade the LifeTime management console:

  1. Download the latest LifeTime management console binaries from the downloads area.

  2. Follow the installation checklist that is launched when you run the LifeTime management console installation binary. During the upgrade, your LifeTime management console and any installed LifeTime plugins will be unavailable.

  3. If you have LifeTime plugins or integrations, you should republish all plugins as described below.

Hybrid infrastructure

OutSystems hybrid infrastructures have the LifeTime environment running in OutSystems Cloud, therefore the upgrade process is the same as OutSystems Cloud upgrade process.

Hybrid configuration is only supported in OutSystems licenses purchased before January 2020.

After the upgrade

If you don’t have any LifeTime plugins or integrations, your LifeTime management console is ready to use.

If you have LifeTime plugins deployed in your LifeTime environment, you should republish all plugins to avoid runtime errors:

  • Open the Service Center console of your LifeTime environment (eg. https://<lifetime_environment>/ServiceCenter).

  • Go to the Factory section, and then to the Solutions area.

  • Create a solution containing all the modules of your LifeTime plugins.

  • Publish the solution.

After the solution has been published, test all your plugins.

Test also your integrations with LifeTime environment to assure they are working correctly.

Frequently Asked Questions

How do I know which LifeTime version I’m running?
Learn how to identify your LifeTime version here.

I’m running OutSystems 10. If I want to upgrade my LifeTime to OutSystems 11, must I also upgrade my application environments to OutSystems 11?
No. You can upgrade LifeTime and keep your application environments in any supported version. LifeTime 11 is compatible with OutSystems 10 environments. Read more about which versions of Platform Server can LifeTime manage.

I’m running OutSystems 10. If I want to upgrade my LifeTime to OutSystems 11, will anything stop working due to breaking changes?
If you don’t have LifeTime plugins or other integrations with the LifeTime environment (eg. using LifeTime APIs to integrate with external tools, such as Jenkins) there will be no impact. If you have LifeTime plugins or other integrations, you should prepare your applications for the upgrade.

I’m running OutSystems 10 and I have LifeTime plugins. If I want to upgrade my LifeTime to OutSystems 11, must I also upgrade my application environments to OutSystems 11?
You can either develop your plugins in the LifeTime environment directly or upgrade all your application environments to OutSystems 11.

I’m running OutSystems 11. Must I upgrade all my application environments to the latest version whenever LifeTime is upgraded?
No. You can keep your application environments in the same Platform Server version.

Do I need to continuously upgrade LifeTime in my infrastructure?
LifeTime is now released on monthly basis. Keeping your LifeTime upgraded enables you to benefit from the latest features and fixes.

OutSystems Cloud or hybrid infrastructures

I’m getting an error in LifeTime, that is fixed in the latest LifeTime version. How can I have my LifeTime upgraded to the latest version?
You can request the upgrade of your LifeTime management console to the latest version, by opening a Support Case using any of the available mechanisms.

I have a hybrid infrastructure. What is the LifeTime maintenance window if most of my environments are self-managed (private cloud / on-premises)?
The LifeTime environment runs in OutSystems Cloud and shares its maintenance window with your non-production Cloud environments. To define the maintenance window for LifeTime, follow the steps in Define the maintenance window for LifeTime environment.

My LifeTime is being upgraded. When can I use LifeTime again after the upgrade?
You will receive a notification email when the upgrade is finished. LifeTime will be partially unavailable during the upgrade, which means you will not be able to stage deployments, activate new cloud services, or use your LifeTime plugins and integrations. Having a defined maintenance window, assures your upgrades are scheduled for the time that better fits your needs.