Preparing for the Content Manager server upgrade
Before upgrading Content Manager server, perform a number of preparatory tasks.
- Cancel or complete all current publish transactions
If you have any publish transactions that are currently in the queue and not yet completed, cancel those publish transactions from the Publishing Queue dialog in Content Manager Explorer, or wait for them to finish before proceeding. - Uninstalling add-ons
If you have any add-on products installed, even if they are compatible with SDL Tridion Sites 9.5, uninstall all of them before upgrading Content Manager server. Compatible add-ons minimally require an uninstall and reinstall, unless explicitly indicated otherwise. - Backing up TCM54.config
If you changed caching settings in theTCM54.configfile in the web\WebUI\Models\TCM54\Configuration\ subfolder of%TRIDION_HOME%, back it up to a safe location. - Backing up FormatAreaStyles.css
Because the file FormatAreaStyles.css has moved to a new location, back up your original (located in %TRIDION_HOME%\web\WebUI\Editors\CME\Configuration\ to a safe location. - Configuring the location of tnsnames.ora
As of SDL Tridion Sites 9.1, it is no longer required to have Oracle database client software installed, but the use of a tnsnames.ora file is still required if you use Oracle. Previously, the location of this file was configured in the client; now, you need to configure this location in an environment variable before upgrading. - Backing up your Safeguard configuration
If you use Safeguard (now a deprecated feature) and want to continue using it, from the web\WebUI\Editors\Safeguard\Configuration\ subfolder of %TRIDON_HOME%, back up SafegaurdEditor.config to a safe location. - Backing up logback.xml for the Transport Service
Because running the installer will change your logging directory for the Transport Service, back up the file logback.xml, located in the config\ subfolder of %TRIDION_HOME%, to a safe location of your choice.