Configure a processing server

You can configure one or multiple processing servers for aggregation or other kinds of processing. Multiple processing servers can provide better scalability and performance. As a general rule, the more aggregation server instances you create, the faster aggregation processing will be.

Recommendations

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

Note

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.

Configuration and connections

In order to install a Sitecore server, you must:

  1. Ensure that you have read the hardware guidelines for Sitecore Hosting Environment Requirements and Sitecore Client Requirements sections from Installation Guide 9.0. You can download the guide from the Sitecore Downloads page.
  2. Install a Sitecore instance using the Sitecore Installation Framework according to the instructions in the Installation Guide 9.0.

Note

When you use the Sitecore Installation Framework to install the server, you do not need to configure the server and the connections manually. The Sitecore Installation Framework performs the following steps automatically.

In order to configure a processing server manually, you must:

  1. Use rule-based configuration to configure the server to fulfill only the processing role by including this line in the web.config file:
<add key="role:define" value="Processing" />
  1. Ensure the following connection strings are set in the \App_Config\ConnectionStrings.config file:
Name Type Notes
core SQL  
master SQL  
reporting SQL Collection data is aggregated into the reporting database.
xconnect.collection HTTPS If collection and search are on dedicated servers, you will need to configure xconnect.collection and xconnect.search separately.
xconnect.collection.certificate Certificate  
xdb.referencedata SQL Used to access definition data during processing. Processing is an xDB component, and therefore accesses the database directly.
xdb.processing.pools SQL  
reporting.apikey Unique string Required if you use a dedicated Reporting Service or processing server.
xdb.processing.tasks SQL  

Note

If xConnect has been set up to use separate collection and search end points, they must be configured separately.

  1. Configure content search. Configuration depends on your provider:

In a scaled environment, you should use Solr or Azure Search - Lucene is not recommended. Azure Search provider is supported for Azure Cloud PAAS deployments only.

Note

The processing server does not have direct access to the xDB core. Contact and interaction search is done through the xConnect Search service.

Security

Refer to the Security Hardening Guide for comprehensive security hardening instructions.