Sitecore Experience Platform

Enable the interaction registry on a content management server

Abstract

Configuring a content management server to register interactions in a scaled environment.

Note

This topic only applies to content management servers in a scaled environment using Sitecore 8.1 update 3 and later updates. In Sitecore versions before 8.1 update 3, you can only use a content delivery server to register interactions. In Sitecore 8.2, the configuration files that enable the interaction registry are included by default when you configure a content management server.

By default, in a scaled environment, you can only register interactions on a content delivery server – not a content management server. This is because the interaction registry depends on analytics tracking functionality, which is only available on the content delivery web role.

When you don't want to route connections from your backend servers to your content delivery servers, you should use a content management server to register interactions from other backend office systems, for example, CRM systems.

To enable the interaction registry on a content management server in a scaled environment where the content delivery and content management environments are on separate, dedicated servers with direct access to the xDB collection database, you need to enable or disable some additional configuration files (Website\App_Config\Include folder).

Note

If your content delivery and content management instances are both on the same server, you do not need to change the default configuration.

Configuration file

Enable

Disable

Sitecore.Analytics.Tracking.Database.ScaledCM.config

62FC438E3D55408CA546D494B9DAD800.png

Sitecore.Analytics.Tracking.Database.config

DED29D56F54B4A88B2851AE044A0D02D.png

Sitecore.Analytics.Tracking.Aggregation.config

A20BCDDE547D42F4AF3A27CD6B4549CF.png

Important

If a contact is visiting your website, the contact is locked and interactions cannot be registered. This results in a ContactLockException. If this happens, retry the register operation later. The rejection of interactions on a content management server does not affect the collection of interactions on the content delivery server.