Differences

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

--- 712:upgrade_from_710 [2025/09/15 14:55] – created - external edit 127.0.0.1
+++ 712:upgrade_from_710 [2025/09/18 06:51] (current) – removed Weinlein, Thomas
@@ Line 1: / Line 1: @@
-====== Steps to upgrade from V7.10 to V7.11 ======
-===== Create Backups Before Upgrading =====
-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.
-Please also backup your cacerts file from your JDK installation. (<JavaHome>/jre/lib/security/cacerts)
-===== Stop Stages =====
-Linux: execute ''sudo stages stop''
-Windows: stop the ''Stages'' and ''Stages Search'' Windows services
-===== Execute Manual Actions Before Upgrading to Stages 7.11 =====
-In case you are upgrading from the latest service releases 7.9.19.0 and 7.10.10.0 or newer, there is only one mandatory manual action in case Kerberos Authentication is in use.
-| **Kerberos autologin is no longer supported since Stages version 7.11. See the documentation on how to switch to [[712:integration:saml|SAML]].** |
-In case you use our Standard Reports 'License Usage' or 'Process Version Usage', please update to the latest version published here: [[:reports:start]]
-In case you use **custom reports** or **admin jobs** please test them as configuration changes might be necessary for them to work, due to enhanced security restrictions. See [[712:scripting_advanced|]] for more details.
-===== Upgrade to Stages 7.11 =====
-Linux: execute ''sudo rpm -Uvh stages-…rpm''  or ''sudo yum localinstall stages-…rpm'', depending on your Linux flavor
-(if you have installed the rpm to different path then default - ///opt/stages// - previously: "--prefix=/path/to/stages" also have to be added to the update command)
-Windows: execute Stages V7.11 Windows installer in an administrative command prompt and follow the assistant steps
-===== Execute Manual Actions After Upgrading to Stages 7.11 =====
-**The following actions only apply when upgrading from a release minor to Stages 7.10.10.0 or 7.9.19.0**.
-Please have a look at this **Security Advisory**:
-[[https://doc.stagesasaservice.com/general/secadv-2024-01]]
-> Please remind that the mentioned mitigation actions also need to be executed after upgrading to Stages 7.11
-When upgrading to the **new default Unified Configuration metamodel versions** provided with this release, existing processes using previous versions of the unified configuration need to be migrated with the following commands. Please replace the [ROOT_WORKSPACE_NAME] with your root workspace name:
-''bin/migrateMetamodel.bat|sh -c migrateMemberOfRoleAssocDirection.xml -a -r -w [ROOT_WORKSPACE_NAME] -o unified_configuration''
-''bin/migrateMetamodel.bat|sh -c migrateMemberOfRoleAssocDirection.xml -a -r -w [ROOT_WORKSPACE_NAME] -o unified_configuration_3''
-''bin/migrateMetamodel.bat|sh -c migrateMemberOfRoleAssocDirection.xml -a -r -w [ROOT_WORKSPACE_NAME] -o unified_configuration_vs''
-''bin/migrateMetamodel.bat|sh -c migrateMemberOfRoleAssocDirection.xml -a -r -w [ROOT_WORKSPACE_NAME] -o unified_configuration_vs3''
-Please remind that the Linux installer automatically replaces the default Unified Configuration metamodels - **if you do not use any customer specific adoption**. The Windows installer does not replace any metamodels automatically. To activate the new default metamodels with Windows, please contact the Stages support team.
-> If you use a customer specific Unified Configuration metamodel, please contact your product consultant for further information.
-**The following actions only apply when upgrading from a release minor to Stages 7.10.5.0 or 7.9.14.0**.
-[[https://doc.stagesasaservice.com/79/upgrade_to_7_9_14]]
-[[https://doc.stagesasaservice.com/710/upgrade_to_7_10_5]]
-===== Restart Stages =====
-Linux: execute ''stages reload''
-Windows: verify that ''Stages''  and ''Stages Search''  Windows services are running