Stages Documentation

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
261:upgrade_from_712 [2026/04/15 16:51] – [Execute Manual Actions] Weinlein, Thomas261:upgrade_from_712 [2026/04/22 12:35] (current) – [How to upgrade to version 26.1] Weinlein, Thomas
Line 4: Line 4:
  
 Please [[stages-support@ul.com|contact our customer care team]] to request an upgrade of your Stages Managed Service instance. Please [[stages-support@ul.com|contact our customer care team]] to request an upgrade of your Stages Managed Service instance.
 +
 +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.
  
 //Note: all process release automations have to be finished before an upgrade can be performed.// //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]])
 +
 +//Note: An existing SAML connection needs to be reestablished, by registering new URLs at the IDP server.//
  
 ===== Upgrade your system to at least Stages 7.12.5.0 ===== ===== Upgrade your system to at least Stages 7.12.5.0 =====
Line 36: Line 41:
 === server.xml migration === === server.xml migration ===
  
-Remove the following lines from conf/server.xml+Remove the following lines from ''$STAGES_CONF/server.xml''
  
 <code xml> <code xml>
Line 74: Line 79:
  
 >//In case SAML SSO is enabled please ensure the idp-metadata.xml file is available in ''$CONF_STAGES''.// >//In case SAML SSO is enabled please ensure the idp-metadata.xml file is available in ''$CONF_STAGES''.//
 +
 +The ACS URLs changed and because of that the information about Stages in the IDP must be updated. Best case is to take the sp-metadata.xml file and import it on the IDP. Certificates should stay the same.
  
 The authentication section in the ''config.xml ''file needs to be migrated to a new format. The basic conversion can be done by the following script call. Please review the results in detail and add missing information as the ''idp-metadata.xml'' file from the SAML IDP. The authentication section in the ''config.xml ''file needs to be migrated to a new format. The basic conversion can be done by the following script call. Please review the results in detail and add missing information as the ''idp-metadata.xml'' file from the SAML IDP.
Line 85: Line 92:
 === Database access configuration migration === === Database access configuration migration ===
  
-The ''conf/database.properties'' file used in Stages 7.12 and earlier is no longer in use. Database connection settings are now configured in conf/config.properties and conf/secret.properties with the following property keys:+The ''conf/database.properties'' file used in Stages 7.12 and earlier is no longer in use. Database connection settings are now configured in ''conf/config.properties'' and ''conf/secret.properties'' with the following property keys:
  
 <code properties config.properties> <code properties config.properties>
Line 91: Line 98:
 database.jdbc.url= database.jdbc.url=
 </code> </code>
 +They are similar to these properties from conf/database.properties: torque.database.default.driver, torque.database.default.url
  
 <code properties secret.properties> <code properties secret.properties>
Line 96: Line 104:
 database.password= database.password=
 </code> </code>
- +and those are the like torque.database.default.username, and torque.database.default.password.
-They are similar to these properties from conf/database.properties: torque.database.default.driver, torque.database.default.url, torque.database.default.username, and torque.database.default.password.+
  
 >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.