Post-install/upgrade tasks
After you complete a new installation of Content Manager server or an upgrade, you should complete a number of post-installation tasks. The post-installation tasks help you verify the installation and configure the components that you have just installed. A list of additional tasks apply if your installation is made in a context of application upgrade.
- 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
DBUpgradeTool, 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 installation 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 Knowledge Center 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. - 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. - Creating a ServiceUser user
Creating a user ServiceUser user is a mandatory action for translation services, and for the interaction between Content Manager and Content Delivery. - 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. - Configuring Content Manager to support team editing
To enable team editing in Content Delivery, you need specify values including the URI of yourContent Delivery web application in two different configuration settings. - Specific post-upgrade tasks
If Content Manager installation has been performed in the context of an upgrade, you need to make sure that important characteristics of the environment are restored. - Installing Content Editor
The Content Editor is installed as part of Content Manager. You just need to install the license file and enable the capability. - Enable the Quality Assistant plugin for Content Editor
Follow this procedure to enable the Quality Assistant in the Content Editor. - Verifying the installation
Conduct some testing to verify critical parts of your installation.