Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 262:upgrade_from_712 [2026/11/18 18:10] – Goetz, Sebastian | 262: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: | ||
| + | |||
| + | * **[[# | ||
| + | * **[[# | ||
| + | |||
| + | ===== 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 | ||
| - | Please [[stages-support@ul.com|contact our customer care team]] | + | ===== Part 1: Plan the upgrade ===== |
| + | |||
| + | To ensure a smooth transition without disrupting your productive process work, we strongly recommend the following procedure. | ||
| + | |||
| + | ==== 1. Check the prerequisites ==== | ||
| + | |||
| + | **Only** Stages databases of Stages **7.12.5.0 or newer** can be upgraded | ||
| + | |||
| + | ==== 2. Update customized Stages extensions ==== | ||
| + | |||
| + | If you use any of the following, contact | ||
| + | * customized metamodel | ||
| + | * customized reports | ||
| + | * Admin Jobs | ||
| + | * other customer-specific add-ons (e.g. importers, exporters) | ||
| + | |||
| + | ==== 3. Review functional changes ==== | ||
| + | |||
| + | The following changes require preparation on your side: | ||
| - | //Note: All process release automations have to be finished | + | * **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 |
| + | * **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. | ||
| - | //Note: An existing SAML connection needs to be re-established by registering the new URLs at the IdP server.// | + | ==== 4. Set up a test system ==== |
| - | ===== Recommended | + | Always perform the upgrade |
| - | An upgrade from Stages 7.12 to 26.2 is a major version step. To ensure a smooth transition without disrupting | + | * The test system must be connected |
| + | * Connect all **third-party systems** to the test system that are also connected to your productive | ||
| - | - **Update customer-specific products 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: | + | Then upgrade the test system as described in [[#part_2conduct_the_upgrade|Part 2 – Conduct the upgrade]]. |
| - | * customized metamodel | + | |
| - | * customized reports | + | |
| - | * Admin Jobs | + | |
| - | * other customer-specific add-ons (e.g. importers, exporters) | + | |
| - | - **Set up a dedicated test system** \\ Always perform | + | |
| - | - **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/ | + | |
| - | - **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, | + | |
| - | ==== Test checklist | + | ==== 5. Test the upgrade |
| - | 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. | + | 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 57: | 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 | + | Only when all tests have been completed successfully, |
| + | |||
| + | * **Stages | ||
| + | | ||
| + | |||
| + | ===== 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: | ||
| - | ===== Ensure consistent data ===== | + | ==== 2. Ensure consistent data ==== |
| To minimize the chance of issues during the upgrade, it is recommended to execute '' | To minimize the chance of issues during the upgrade, it is recommended to execute '' | ||
| Line 74: | Line 104: | ||
| //Note: Stages should be stopped while '' | //Note: Stages should be stopped while '' | ||
| - | ===== Create backups | + | ==== 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 155: | Line 185: | ||
| > Add '' | > Add '' | ||
| + | |||
| + | ==== 7. After the upgrade ==== | ||
| + | |||
| + | * **Set up workspace collections** via '' | ||
| + | * **Update the IdP:** If SAML SSO is used, make sure the new Stages URLs are registered at the IdP (see [[# | ||
| + | * **Test:** On the test system, continue with [[# | ||