Jayson Cauyan
Rank: #3089
155Views
10Comments
Solved
OutSystems 10 to 11. In place upgrade or migrate?
Question
Installation

We're currently planning on which is the best solution in order for our applications to run at the latest version of OutSystems. Is it great to proceed with the inplace upgrade or migrate to the up and running OutSystems 11 version (seperate app and db server?


Plan 1 - Upgrade Plan:

1. Existing OutSystems 10 Platform is running in 2012 Win OS Version on which is not compatible with OutSystems 11. Is it okay or safe to proceed with the OS upgrade?

2. If yes, we will proceed with OS upgrade to 2016 and version upgrade from 10 to 11. Is there any other things we need to look forward before initiate the version upgrade


Plan 2 - Migration Plan:

1. What are the things we need to consider or do you have recommended procedure on doing it? Currently, we have done setting up the OutSystems 11 Platform with version 11.7.2 Buid 5739 on a seperate server.

2. if we will proceed with the migration from OutSystems 10 to 11 PRD to PRD and DEV to DEV, How could we successfully migrate the live data? As of this writing, we were able to migrate the .oap using IPP.


Thank you.

0
0
on 2020-03-10
Copy link to comment
ronny
Rank: #1071
Solution
See solution in context
0
0
on 2020-12-10
Copy link to comment
Jayson Cauyan
Rank: #3089
Solution

Listed below are the recommendation steps for your upgrade:


  • Upgrade SQL version
  • Upgrade Windows OS version
  • Upgrade OutSystems Version from 10 to 11
  • Follow the installation checklist
  • Upgrade LifeTime environment first before any environment (LifeTime > Dev > UAT > Production)
  • Create WBS and coordinate with affected users or involved teams (i.e. BPM, Process Owners, Development team and etc,)
  • Review the following – OutSystems Download
  • System Requirements
  • Side effected and breaking changes
  • Documentation
  • OutSystems product releases
  • Use the stable platform release - LifeTime Management Console 11.7.3 (for LifeTime) and Platform Server 11.9.1 (for Platform)
  • Check the application breaking changes prior to the upgrade (c/o Development Team)
  • Upgrade OutSystems Platform
  • End of Mainstream Support for OutSystems Platform 10
  • Any critical issues, you may file a support case using your activation code found in your Service Center.
  • Have a database backup and server snapshot in-place before each activity.
See solution in context
0
0
on 2020-12-01
Copy link to comment

Hi Jayson,


I'd rather go with option #2. And the reasons for that being:

  • You can prepare the infrastructure before-hand: set the DB and App servers;
  • Rollback would be easier: With option #1 you'd have to revert the infrastructure (e.g. VM snapshots/fresh install) and restore the database backups. With option #2, you just have to shutdown OS11 infrastructure and startup OS10 infrastructure.

In a nutshell option #2 is simpler to execute and involves less risk. The only tricky part is that you have to migrate the database from OS10 infrastructure to OS11 infrastructure. However Outsystems has a detailed guide you can find here:
https://success.outsystems.com/Support/Enterprise_Customers/Maintenance_and_Operations/Migrate_an_Environment_Using_a_Database_Clone


If you have downtime requirements, meaning during the upgrade you apps should be live, you have to go with option #1. With option #2 while migrating the database you must take you DB offline, since in case of rollback you'd loose data. With option #1, and assuming you have multiple front-ends and the database server supports OS11, it is possible to do an upgrade without downtime.


IG 


4
0
on 2020-03-10
Copy link to comment
Jayson Cauyan
Rank: #3089

Thank you so much and will consider also your kind inputs. 

0
0
on 2020-03-16
Copy link to comment
ronny
Rank: #1071

Hi Jayson,

I also have similar situation as yours and in rush to migrate to outsystems 11 before 31 dec 2020 outsystems 10 end of support.

If you are okay, can share how you manage to upgrade using plan 2 migration plan?


Any issue when you try to connect the new app server in outsystems 11 with the new database cloned from the old outsystems 10 database?


In my case, my old outsystems 10 database is in Oracle 11g and my dba will clone the database and restore to new database server in 19c

1
0
on 2020-11-26
Copy link to comment
Jayson Cauyan
Rank: #3089

Hi,


Rather than migrating applications from one server to another, we decided to proceed with the in-place upgrade. First, you will need to upgrade the SQL and Windows OS version based on the system requirements of the OutSystems 11 version you are planning to upgrade. Review breaking changes on the app and upgrade it. Just make sure to back up the database and snapshot of your server.

0
0
on 2020-11-27
Copy link to comment
ronny
Rank: #1071

Replying to Jayson Cauyan's comment on 27 Nov 2020 00:43:28

Hi Jayson,


If you are okay, can share why you decided not to do plan #2 migration? 

My infra team reluctantly does not agree if we upgrade the old server windows os. They prefer a fresh new vm with the new windows os server.


For plan #2, do we actually need to do following

1. Fresh installation of new vm with outsystems 10

2. Migrate the current outsystems 10 to the new vm

3. Upgrade the new vm to outsystems 11


I am wondering whether fresh installation of new vm with outsystems 11 and connect to the current outsystems 10 database will be okay to ensure all application and data are migrated.

Thanks

0
0
on 2020-11-27
Copy link to comment
Tim Timperman
Rank: #256

We had a similar issue at a customer with unsupported windows versions. What we did was a fased upgrade. This guaranteed we did not have to move data around while keeping some rollback possibilities.

1. Get your new VMs/server(s) with a supported windows server version. Install OutSystems server 10 on 1 (or more) of them, and include that server as a frontend in your existing environment.

2. Turn off the deployment services on the old servers -> this ensures the updated applications are not deployed to these servers. They keep serving the users. Make the new server the deployment controller.

3. Upgrade the environment to 11 (basically on that 1 new server). 

4. Add extra servers, by immediately installing platform 11 on them.

5. Kill off the old servers.

Some more information: https://success.outsystems.com/Support/Enterprise_Customers/Upgrading/01_Upgrade_OutSystems_Platform

0
0
on 2020-11-27
Copy link to comment
ronny
Rank: #1071

Replying to Tim Timperman's comment on 27 Nov 2020 10:55:18

Hi Tim,

Thank you so much for the steps. 

If you are okay, can check with you on the following?

Can check what config file you need to copy from the old deployment controller server to the new server after step 2?

For the republishing all modules using deployment controller os11, is it to be done only after step 3? 

Will it cause any issue that old outsystems 10 front end still up during step 3?

Do you need to request for new license to upload into the new os11 deployment controller?


Thank you so much for the help

0
0
on 2020-11-30
Copy link to comment
Jayson Cauyan
Rank: #3089
Solution

Listed below are the recommendation steps for your upgrade:


  • Upgrade SQL version
  • Upgrade Windows OS version
  • Upgrade OutSystems Version from 10 to 11
  • Follow the installation checklist
  • Upgrade LifeTime environment first before any environment (LifeTime > Dev > UAT > Production)
  • Create WBS and coordinate with affected users or involved teams (i.e. BPM, Process Owners, Development team and etc,)
  • Review the following – OutSystems Download
  • System Requirements
  • Side effected and breaking changes
  • Documentation
  • OutSystems product releases
  • Use the stable platform release - LifeTime Management Console 11.7.3 (for LifeTime) and Platform Server 11.9.1 (for Platform)
  • Check the application breaking changes prior to the upgrade (c/o Development Team)
  • Upgrade OutSystems Platform
  • End of Mainstream Support for OutSystems Platform 10
  • Any critical issues, you may file a support case using your activation code found in your Service Center.
  • Have a database backup and server snapshot in-place before each activity.
0
0
on 2020-12-01
Copy link to comment
Tim Timperman
Rank: #256

Replying to ronny's comment on 30 Nov 2020 17:50:34

Can check what config file you need to copy from the old deployment controller server to the new server after step 2? All the necessary copying is needed when you add the new server to the farm. More info in this article. I don't think any extra copy is needed when switching deployment controller.

For the republishing all modules using deployment controller os11, is it to be done only after step 3? YES

Will it cause any issue that old outsystems 10 front end still up during step 3? The system database will already be upgraded at that point, but it should not pose too many issues. Check this article for more information on zero-downtime upgrades.

Do you need to request for new license to upload into the new os11 deployment controller? Normally no, but if you do need, it's a simple download from https://www.outsystems.com/Licensing

0
0
on 2020-12-03
Copy link to comment
ronny
Rank: #1071
Solution
0
0
on 2020-12-10
Copy link to comment