Configuring the Content Manager server
After you have installed the Content Manager you need to configure various parts of the Content Manager to get it up and running.
Note: The Content Manager Explorer and the deprecated Monitoring Server (if using) require no server-side configuration.
- Impersonation user identity
If you installed the WebDAV Connector or the Visio Workflow Server, the installer created a Windows impersonation user. This impersonation user is trusted to take on the identify of (that is, to impersonate) an arbitrary Content Manager user. You can use the same impersonation user for all three interfaces. - Configuring the Content Manager Explorer website
Check the redirection key and execute a Microsoft Knowledge Base article to configure the website. - Configuring logging for Content Manager
To change the detail level of the log messages or any other aspect of logging, modify the NLog.config file. By default, the log level is set toWarn, which means that warnings, as well as critical and non-critical errors, are logged. - Changing the default log location of the Transport Service
By default, the Transport Service (which takes care of transporting content out of Content Manager for publishing) is configured to produce logs in the bin\logs\ subfolder of%TRIDION_HOME%. If you want to change this default, modify it in the Logback configuration file. - Configuring the maximum size of uploads to Content Manager
When you upload content to Content Manager, one or more preconfigured upload limits can restrict the size of the content you are allowed to upload. You can change these upload limits to change how big (or small) an upload can be. - Configuring Content Manager search
You can change the default Solr index location as well as the default search port. - Optimizing the search collection
Regularly optimize your search collection to keep your search collection up-to-date and fast. - Configuring the client for the Add-ons Service in Content Manager
Configure the URL and other settings for the Add-ons Service client by editing the AddonsSettings.json client configuration file. - Configuring navigation shortcuts for Add-ons and Access Management
When you enable the Add-ons and Access Management features while installing Content Manager, you are required to provide URLs for each service. One use of these URLs is to create shortcuts on the slide-out navigation. If either of the underlying URLs change, you can edit the manifest.xml file to set the appropriate shortcut URL. - Configuring funneling
You may want to funnel different Web sites with different ports and/or host headers to the same Content Manager Explorer location. - Configuring Content Manager for notification broadcasting with a SQL Azure database
After installing Content Manager, you need to apply some additional backplane hub configuration to enable broadcast notification. Specifically, you will specify your Azure Service Bus and service bus endpoint in the server-side Content Manager configuration file. - Scheduling cleanup of upload files and preview files
By default, the Content Manager does not clean up files that users upload to Content Manager, nor files that Content Manager generates when users preview content. Schedule regular cleanups of the folders that contain those files. - Setting registry values if you are using OpenJDK 11
If you use OpenJDK 11 as your Java virtual machine, you need to set several registry value in order for some Content Manager services (specifically the Transport Service and the Monitor Service) to work correctly.