This is an old revision of the document!


How to upgrade to version 26.1

Version 26.1 is currently only available on Stages Managed Service instances. On-premise usage will be made available later this year.

Please contact our customer care team to request an upgrade of your Stages Managed Service instance.

Note: all process release automations have to be finished before an upgrade can be performed.

Upgrade your system to at least Stages 7.12.5.0

Only Stages databases of Stages 7.12.5.0 or newer can be upgraded to Stages 26.1. Therefore upgrade to this version first if not yet done.

Ensure consistent data

To minimize the chance for issues during the upgrade it is recommended to execute ensureDatabaseIntegrity.bat|sh before upgrading to Stages 26.1.

To minimize the runtime of ensureDatabaseIntegrity add the following config properties to config.xml to skip those steps:

config.xml
<property name="database.cleanup.targets" value="false"/>
<property name="database.cleanup.associationAttributes" value="false"/>

Note: Stages should be stopped while ensureDatabaseIntegrity is running.

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.

Install Java 25

Install Stages 26.1

Execute Manual Actions

server.xml migration

Remove the following lines from conf/server.xml

<Realm className="org.apache.catalina.realm.CombinedRealm" > 
    <Realm className="de.methodpark.stages.containerauth.SSLAuthenticatorRealm" roles="pki_user"/> 
    <Realm className="de.methodpark.stages.containerauth.SimpleAuthenticationRealm" roles="StagesUser" /> 
</Realm> 

and

<Valve className="org.apache.catalina.authenticator.SingleSignOn" />

remove the Context elements with path=“/stages” and path=“/reporting”:

<Context path="/stages" docBase="stages" cookies="true">
[...]
</Context>
<Context path="/reporting" docBase="reporting" cookies="true" >
[...]
</Context>

In case one of the Connectors are configured to use protocol “org.apache.coyote.http11.Http11Nio2Protocol” replace that by “org.apache.coyote.http11.Http11NioProtocol”

<Connector port="[...]"
protocol="org.apache.coyote.http11.Http11NioProtocol"
[...]
/>

Authentication method configuration migration

In case SAML SSO is enabled please ensure the idp-metadata.xml file is available in $CONF_STAGES.

Execute the upgradeConfig.sh

Database access configuration migration