Post upgrade tasks
After you complete the upgrade of your Content Manager server, you should perform a number of post-upgrade tasks. These tasks help you to verify the installation and configure the components that you have just upgraded.
- Verifying Microsoft SQL System Administration role permissions
To ensure that the database upgrade tool (DBUpgradeTool or DBUT) works properly, theisourceuser must have system administrator permissions. - Running DBUpgradeTool for maintenance
DBUpgradeTool (DBUT), for all supported database engines, performs an overall verification of the database and updates database objects such as views, indexes, packages and stored procedures and modifies metadata structures. - Completing the installation or upgrade with ISHDeploy
Most post-install/upgrade tasks can be carried out with ISHDeploy. - Adding the relying party entries for webUI and WCF Services for commercial STS
After the Content Manager installation you have to create the Relying Party Trust for the website and the WCF services on the STS Server if you are not using ISHSTS. This is required to allow logins to Content Manager. - Configure Security Token Service
Client installations can be used only if you properly configure a Security Token Service (STS). The default system that manages user identity for Tridion Docs is ISHSTS. - The Administrator setup
Needs to be done only if you did not receive a fully prepared database dump-backup file, otherwise this is done and configured. - Upgrading Content Manager from 13.0.0 or 13.0.1
New features and feature changes that appeared between the 13.0.0 release and the service packs require specific actions for the upgrade. - Checking the TRANSLATORSERVICE role
An active TRANSLATORSERVICE role is necessary for translation services (TranslationOrganizer, TranslationBuilder) to operate. This role is part of the out-of-the-box settings for Content Manager 10.0.0 and later. Older versions require that you create it manually along with a list of status transitions. - Translation management integration configuration
The configuration of the Translation management integration with WorldServer, TMS and File System is described. - Enabling services
After the install is complete, services will not start automatically, since the database is not guaranteed to be in the right state until you run DBUT tool. Also, you might decide not to start some services on the specific installation depending on the server role. To enable typical services you can locate and run the Enable-DefaultServices.ps1 script. - Enabling Draft Space
We recommend you enable Draft Space with ISHDeploy. - Rebuilding the full text index
You can rebuild the full text index if it is no longer synchronized with the current database, or after a Content Manager upgrade on a new server for example. - Configuring Content Manager for Collaborative Review
To enable accessing Collaborative Review features from Content Manager, you need to specify values including the URI of your Collaborative Review web application in two different configuration settings. - Verifying the installation
Follow these procedures to test and verify the critical parts of the new Content Manager installation. - Collaborative Review upgrade
Collaborative Review has added features. - System management reference for Content Manager upgrade
A few system management concepts are good to know in the context of a complex Content Manager upgrade.