Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| 262:upgrade_from_712 [2026/09/28 19:26] – created - external edit 127.0.0.1 | 262:upgrade_from_712 [2026/11/19 15:55] (current) – Goetz, Sebastian | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== How to upgrade to version 26.1 ===== | + | ====== How to upgrade |
| - | **Version | + | An upgrade from Stages 7.12 to 26.2 is a major version step. This page is divided into two parts: |
| - | Please | + | * **[[# |
| + | * **[[# | ||
| - | If you use a customized metamodel on your Stages Managed Service instance, it needs to be adapted to v26 by your Stages product consultant first. | + | ===== Before |
| - | //Note: all process release automations have to be finished before an upgrade can be performed.// | + | **Version 26.2 is currently only available on Stages Managed Service instances. On-premise usage will be made available later this year.** |
| - | (see Report [[reports: | + | |
| - | //Note: An existing SAML connection needs to be reestablished, | + | **Integrations with PTC products are not yet available for 26.2.** |
| - | ===== Upgrade your system | + | **The following scripts are currently not yet available for 26.2:** |
| + | * **Transfer Mapping script** – transfers compliance mapping associations | ||
| + | * **Migrate Metamodel script** – adapts the process content so that it matches a new metamodel | ||
| - | **Only** Stages databases of Stages **7.12.5.0 or newer** can be upgraded to Stages 26.1. Therefore | + | ===== Part 1: Plan the upgrade |
| - | ===== Ensure consistent data ===== | + | To ensure a smooth transition without disrupting your productive process work, we strongly recommend the following procedure. |
| - | To minimize the chance for issues during the upgrade it is recommended to execute '' | + | ==== 1. Check the prerequisites ==== |
| - | To minimize the runtime of '' | + | **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. |
| + | |||
| + | ==== 2. Update customized Stages extensions ==== | ||
| + | |||
| + | 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) | ||
| + | |||
| + | ==== 3. Review functional changes ==== | ||
| + | |||
| + | The following changes require preparation on your side: | ||
| + | |||
| + | * **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: | ||
| + | * **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/ | ||
| + | |||
| + | Then upgrade the test system as described in [[# | ||
| + | |||
| + | ==== 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** | ||
| + | * All visualizations render correctly (including their different parameter settings) | ||
| + | * All processes are displayed correctly | ||
| + | |||
| + | **Modeling** | ||
| + | * Creating elements and associations | ||
| + | * File upload to a connected CMS system | ||
| + | * Assigning users to a role | ||
| + | * Creating compliance mapping associations | ||
| + | * Creating tailoring associations | ||
| + | |||
| + | **Management** | ||
| + | * Performing module updates in an integrated workspace | ||
| + | * Creating a process version | ||
| + | * Release as valid version | ||
| + | * Performing tailoring (manually and via the tailoring assistant) | ||
| + | * Running a process release automation | ||
| + | |||
| + | **Administration** | ||
| + | * Creating workspaces and collections | ||
| + | * Creating test users | ||
| + | * Assigning permissions | ||
| + | * Creating participants and assigning users | ||
| + | |||
| + | ==== 6. Schedule the productive upgrade ==== | ||
| + | |||
| + | Only when all tests have been completed successfully, | ||
| + | |||
| + | * **Stages Managed Service:** Please [[[email protected]|contact our customer care team]] to request the upgrade of your instance. | ||
| + | * **On-premise: | ||
| + | |||
| + | ===== 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: | ||
| + | |||
| + | ==== 2. Ensure consistent data ==== | ||
| + | |||
| + | To minimize the chance of issues during the upgrade, it is recommended to execute '' | ||
| + | |||
| + | To minimize the runtime of '' | ||
| <code xml config.xml> | <code xml config.xml> | ||
| Line 27: | Line 102: | ||
| </ | </ | ||
| - | Note: Stages should be stopped while ensureDatabaseIntegrity is running. | + | //Note: Stages should be stopped while '' |
| - | ===== Create | + | ==== 3. Create |
| - | To be safe in case of any problems during the update, **back up your database and the stages folder | + | 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. | ||
| - | ===== Install Java 25 ===== | + | ==== 4. Install Java 25 ==== |
| - | ===== Install Stages 26.1 ===== | + | ==== 5. Install Stages 26.2 ==== |
| - | ===== Execute | + | ==== 6. Execute |
| === server.xml migration === | === server.xml migration === | ||
| - | Remove the following lines from '' | + | Remove the following lines from '' |
| <code xml> | <code xml> | ||
| - | <Realm className=" | + | <Realm className=" |
| - | <Realm className=" | + | <Realm className=" |
| - | <Realm className=" | + | <Realm className=" |
| - | </ | + | </ |
| </ | </ | ||
| Line 56: | Line 132: | ||
| </ | </ | ||
| - | remove | + | Remove |
| <code xml> | <code xml> | ||
| Line 67: | Line 143: | ||
| </ | </ | ||
| - | In case one of the Connectors are configured to use protocol | + | In case one of the connectors is configured to use protocol |
| <code xml> | <code xml> | ||
| < | < | ||
| - | protocol=" | + | |
| - | [...] | + | [...] |
| /> | /> | ||
| </ | </ | ||
| Line 78: | Line 154: | ||
| === Authentication method configuration migration === | === Authentication method configuration migration === | ||
| - | >//In case SAML SSO is enabled please ensure the idp-metadata.xml file is available in '' | + | > //In case SAML SSO is enabled, please ensure the '' |
| - | The ACS URLs changed | + | The ACS URLs have changed, therefore |
| - | The authentication section in the '' | + | The authentication section in the '' |
| - | The original '' | + | The original '' |
| - | < | + | < |
| $STAGES_ROOT/ | $STAGES_ROOT/ | ||
| </ | </ | ||
| Line 98: | Line 174: | ||
| database.jdbc.url= | database.jdbc.url= | ||
| </ | </ | ||
| - | They are similar | + | |
| + | These correspond | ||
| <code properties secret.properties> | <code properties secret.properties> | ||
| Line 104: | Line 181: | ||
| database.password= | database.password= | ||
| </ | </ | ||
| - | and those are the like torque.database.default.username, | ||
| - | >Add rewriteBatchedStatements=true as parameter to database.jdbc.url if you are using MySQL. | + | These correspond to '' |
| + | |||
| + | > 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 [[# | ||