Configure a content management server

Current version: 8.1

Content management servers enable content editors to create and publish content to a website. It is possible to mix server features such as content delivery and content management together on the same server, or you could configure a single content management server. You could also have multiple content management servers, depending on your content editing needs.


If you have multiple content management servers, you must set up a dedicated Reporting Service server.


Before you configure a content management server, consider the following recommendations:

  • xDB analytics tracking – tracking contacts, personalization, goals, campaigns, and more can be relevant when creating a dedicated content management server but is not a requirement. You can enable tracking in both xDB and xManagement mode.


    If you have a dedicated content management server used for tracking but do not want to save changes to the collection database, then disable the Sitecore.Analytics.Tracking.Database.config file. If you want to mix content management with other server features, or if there is a chance that other modules may depend on the tracking data access API, then you must enable this file again.

  • Session state – always configure the sessions connection string unless you use the InProc mode for session state. You can use the InProc session provider because a content management server does not perform the same tasks as a content delivery server. A content management server should never be a part of a content delivery cluster.

  • xDB Cloud configuration – if you are running xDB Cloud edition then configure your content management environment according to this topic and the instructions for configuring xDB Cloud.


Synchronize all servers to a single reliable time source, for example, by means of the Network Time Protocol (NTP). The aggregation of engagement automation states depends on the system time and changing this can lead to incorrect aggregation results or loss of data.


Do not make changes directly to the configuration files. Instead, you must create a patch file that performs the required changes during runtime.

Configure a content management server

To configure a content management server:

  1. Ensure that you have read the hardware guidelines for:

  2. Install a Sitecore instance using the Installing the Sitecore Experience Platform guide on the Sitecore Developer Portal website.

  3. Configure database connection strings. This topic contains a list of all database connection strings required for each server type.

  4. Download the spreadsheet that lists of all the configuration files that you must enable or disable for each server type.


    If you are using Windows File Explorer, you must ensure that file extensions are displayed. To display file extensions, in the File Explorer Options window, on the View tab, ensure that the Hide extensions for known file types check box is clear.

  5. Enable or disable the relevant files for a content management server.


    If you do not use the Sitecore Commerce product in your Sitecore XP installation, then you must disable the configuration files that belong to Commerce, regardless of whether the spreadsheet says to disable them or enable them.

  6. In the following configurations files, update each of the parameter values:

    Configuration file





    configuration/sitecore/settings/setting name="Social.LinkDomain"

    setting name



    configuration/sitecore/settings/setting name="InstanceName"

    patch:attribute name

    Default value is blank. If it is blank, Sitecore automatically assigns the unique value of machine id + IIS site name to InstanceName.

    If you assign the InstanceName yourself, give each server a unique name.


    configuration/sitecore/httpTransportFactory/param desc="serviceUrl"

    param desc="serviceUrl"



    Only enable the Sitecore.Xdb.Remote.Client.config and the Sitecore.PathAnalyzer.RemoteClient.config files on content management servers where the reporting role is on a remote server.

  7. Configure a search and indexing provider. This topic contains a list of links and other information you need to configure Lucene or Solr as your search and indexing provider.

  8. Disable the robot detection component on a content management server by following the steps in this topic. The robot detection component is not required on a content management server.


    Disabling the robot detection component will not disable all the robot detection functionality active in the xDB.


The configuration files required for the Content Testing, Experience Analytics, Experience Profile, Federated Experience Manager, List Management, and Social Connected applications are enabled by default.

Optional configuration

Do you have some feedback for us?

If you have suggestions for improving this article,