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 the maximum size of uploads to Content Manager
By default, content uploaded to Content Manager through an SDL Tridion Sites GUI (Content Manager Explorer, Experience Manager or another SDL Tridion Sites-based GUI) fails to upload if it is larger than 30,000,000 bytes (about 28.6 MB). Also by default, content uploaded directly to Content Manager's Core Service can have the highest allowed size: 2 GB. You can change these values to fit your preferences. - 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 Content Manager for notification broadcasting with a SQL Azure database
When you use a SQL Azure database with Content Manager, you need to apply some additional backplane hub configuration if you want to use broadcast notification. Specifically, you need to specify your Azure service bus and service bus endpoint in the server-side Content Manager configuration file. - 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 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. - 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 8
If you use OpenJDK 8 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.