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 Monitoring Server require no server-side configuration.
- Impersonation user identity
If you installed the (deprecated) Business Connector, 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 Web site
Check the redirection key, and execute a Microsoft Knowledge Base article, to configure the Web site. - Configuring the maximum size of uploads to Content Manager
By default, content uploaded to Content Manager through an SDL Web GUI (Content Manager Explorer, Experience Manager or another SDL Web-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. - 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. - Modifying your Safeguard configuration
Change the Safeguard configuration files to make Safeguard work in combination with the upgraded Content Manager server. Note that Safeguard will not work in combination with a legacy setup.