Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
262:upgrade_from_712 [2026/11/19 15:00] – [Recommended upgrade procedure] Goetz, Sebastian262:upgrade_from_712 [2026/11/19 15:55] (current) – Goetz, Sebastian
Line 1: Line 1:
 ====== How to upgrade from Stages 7.12 to version 26.2 ====== ====== How to upgrade from Stages 7.12 to version 26.2 ======
 +
 +An upgrade from Stages 7.12 to 26.2 is a major version step. This page is divided into two parts:
 +
 +  * **[[#part_1plan_the_upgrade|Part 1 – Plan the upgrade]]** describes the organizational preparation and testing. It is relevant for **all customers**.
 +  * **[[#part_2conduct_the_upgrade|Part 2 – Conduct the upgrade]]** describes the technical installation steps. It is relevant for **administrators of on-premise installations**. For Stages Managed Service instances, these steps are performed by UL.
 +
 +===== Before you start: availability and limitations =====
  
 **Version 26.2 is currently only available on Stages Managed Service instances. On-premise usage will be made available later this year.** **Version 26.2 is currently only available on Stages Managed Service instances. On-premise usage will be made available later this year.**
Line 9: Line 16:
   * **Migrate Metamodel script** – adapts the process content so that it matches a new metamodel   * **Migrate Metamodel script** – adapts the process content so that it matches a new metamodel
  
-//Note: The workspace settings **Group** and **Common Elements** no longer exist in 26.2. Their functionality now has to be modeled via **workspace collections**. For details see [[262:collectionmigration|Migrate process interface handling to workspace collections]].//+===== Part 1: Plan the upgrade =====
  
-Please [[[email protected]|contact our customer care team]] to request an upgrade of your Stages Managed Service instance.+To ensure a smooth transition without disrupting your productive process work, we strongly recommend the following procedure.
  
-//Note: All process release automations have to be finished before an upgrade can be performed// (see report [[reports:start#running-process-release-automations|Running Process Release Automations]]).+==== 1. Check the prerequisites ====
  
-//Note: An existing SAML connection needs to be re-established by registering the new URLs at the IdP server.//+**Only** Stages databases of Stages **7.12.5.0 or newer** can be upgraded to Stages 26.2. Therefore upgrade to this version first if not yet done.
  
-===== Recommended upgrade procedure =====+==== 2. Update customized Stages extensions ====
  
-An upgrade from Stages 7.12 to 26.2 is a major version step. To ensure a smooth transition without disrupting your productive process work, we strongly recommend the following procedure:+If you use any of the following, contact your responsible Stages product consultant **before** the upgrade, so that these products can be updated to Stages 26.2: 
 +  * customized metamodel 
 +  * customized reports 
 +  * Admin Jobs 
 +  * other customer-specific add-ons (e.g. importers, exporters)
  
-  - **Update customized stages extensions first** \\ If you use any of the following, contact your responsible Stages product consultant **before** the upgrade, so that these products can be updated to Stages 26.2: +==== 3. Review functional changes ====
-    * customized metamodel +
-    * customized reports +
-    * Admin Jobs +
-    * other customer-specific add-ons (e.g. importers, exporters) +
-  - **Set up a dedicated test system** \\ Always perform the installation on a separate test system first – never directly on your productive system. The test system must be connected to a **mirror (copy) of the productive database**, so that all tests are performed with your real customer data. +
-  - **Connect all third-party systems** \\ Connect all third-party systems to the test system that are also connected to your productive system (e.g. identity provider/SAML, CMS/file storage, ALM tools, mail server), so that these integrations can be tested as well. +
-  - **Perform a thorough test** \\ After the test system has been set up, perform a thorough test based on the [[#test_checklist|test checklist]] below. +
-  - **Upgrade the productive system** \\ Only when all tests have been completed successfully, the productive system may be upgraded. Follow the technical steps described in the sections below.+
  
-==== Test checklist ====+The following changes require preparation on your side:
  
-We recommend testing all common actions that are performed in Stages within your organization (e.g. modeling, releasing). The following checklist serves as a general guideline and should be extended by your organization-specific use cases.+  * **Workspace collections replace Group and Common Elements** \\ The workspace settings **Group** and **Common Elements** no longer exist in 26.2. Their functionality now has to be modeled via **workspace collections**. Plan which collections you need before the upgrade. For details and examples see [[262:collectionmigration|Migrate process interface handling to workspace collections]]. 
 +  * **SAML connection** \\ An existing SAML connection needs to be re-established by registering the new URLs at the IdP server. Coordinate this with the team responsible for your identity provider. 
 + 
 +==== 4. Set up a test system ==== 
 + 
 +Always perform the upgrade on a separate test system first – never directly on your productive system. 
 + 
 +  * The test system must be connected to a **mirror (copy) of the productive database**, so that all tests are performed with your real customer data. 
 +  * Connect all **third-party systems** to the test system that are also connected to your productive system (e.g. identity provider/SAML, CMS/file storage, ALM tools, mail server), so that these integrations can be tested as well. 
 + 
 +Then upgrade the test system as described in [[#part_2conduct_the_upgrade|Part 2 – Conduct the upgrade]]. 
 + 
 +==== 5. Test the upgrade ==== 
 + 
 +After the test system has been upgraded, perform a thorough test. We recommend testing all common actions that are performed in Stages within your organization (e.g. modeling, releasing). The following checklist serves as a general guideline and should be extended by your organization-specific use cases.
  
 **Viewing** **Viewing**
Line 59: Line 76:
   * Creating participants and assigning users   * Creating participants and assigning users
  
-===== Upgrade your system to at least Stages 7.12.5.0 =====+==== 6. Schedule the productive upgrade ====
  
-**Only** Stages databases of Stages **7.12.5.0 or newer** can be upgraded to Stages 26.2. Therefore upgrade to this version first if not yet done.+Only when all tests have been completed successfully, the productive system may be upgraded. 
 + 
 +  * **Stages Managed Service:** Please [[stages-support@ul.com|contact our customer care team]] to request the upgrade of your instance. 
 +  * **On-premise:** Upgrade the productive system as described in [[#part_2conduct_the_upgrade|Part 2 – Conduct the upgrade]]. 
 + 
 +===== Part 2: Conduct the upgrade ===== 
 + 
 +Perform the following steps **first on the test system** and – after all tests have been completed successfully – **on the productive system**. 
 + 
 +==== 1. Finish running process release automations ==== 
 + 
 +All process release automations have to be finished before an upgrade can be performed (see report [[reports:start#running-process-release-automations|Running Process Release Automations]]).
  
-===== Ensure consistent data =====+==== 2. Ensure consistent data ====
  
 To minimize the chance of issues during the upgrade, it is recommended to execute ''ensureDatabaseIntegrity.bat|sh'' before upgrading to Stages 26.2. To minimize the chance of issues during the upgrade, it is recommended to execute ''ensureDatabaseIntegrity.bat|sh'' before upgrading to Stages 26.2.
Line 76: Line 104:
 //Note: Stages should be stopped while ''ensureDatabaseIntegrity'' is running.// //Note: Stages should be stopped while ''ensureDatabaseIntegrity'' is running.//
  
-===== Create backups before upgrading =====+==== 3. Create backups ====
  
 To be safe in case of any problems during the update, **back up your database and the stages folder before the upgrade**. \\ To be safe in case of any problems during the update, **back up your database and the stages folder before the upgrade**. \\
 If the backup is running automated, please check whether the backup was created successfully. If the backup is running automated, please check whether the backup was created successfully.
  
-===== Install Java 25 =====+==== 4. Install Java 25 ====
  
-===== Install Stages 26.2 =====+==== 5. Install Stages 26.2 ====
  
-===== Execute manual actions =====+==== 6. Execute manual actions ====
  
 === server.xml migration === === server.xml migration ===
Line 157: Line 185:
  
 > Add ''rewriteBatchedStatements=true'' as parameter to ''database.jdbc.url'' if you are using MySQL. > Add ''rewriteBatchedStatements=true'' as parameter to ''database.jdbc.url'' if you are using MySQL.
 +
 +==== 7. After the upgrade ====
 +
 +  * **Set up workspace collections** via ''Administration > Workspaces > Collections'' as planned in [[#review_functional_changes|Part 1, step 3]]. Then check via the [[262:remoteassociations|Process Interfaces]] menu that process interfaces are created as expected (see [[262:collectionmigration|Migrate process interface handling to workspace collections]]).
 +  * **Update the IdP:** If SAML SSO is used, make sure the new Stages URLs are registered at the IdP (see [[#authentication_method_configuration_migration|Authentication method configuration migration]]).
 +  * **Test:** On the test system, continue with [[#test_the_upgrade|Part 1, step 5 – Test the upgrade]].