Building a Processing Server role

The job of a processing server is to convert all of the xDB content from MongoDB into a compressed form, which is stored in the reporting database inside of SQL Server.

If you have any custom types that are registered with MongoDB in the Initialize pipeline, then you will need to make sure that the registration also happens on the Processing Server. If the custom types are not registered on the Processing Server, some of the engagement data will not be reduced correctly. If you are unsure if you need to register types with MongoDB, check the Sitecore logs after the processor has run. If there are unregistered types, there will be deserialization errors in the Sitecore logs.

The following steps are for setting up the Processing Server:

  1. Create accounts to be used as app pools. For more information, go to What are the required accounts and groups to create?

  2. Install Sitecore. For more information, go to Sitecore installation.

  3. Install, but do not configure, Commerce Server.

  4. Install Commerce Connect:

    1. From the Sitecore Launchpad, click on Desktop -> Start -> Development Tools -> Installation wizard.

    2. Upload the Sitecore Commerce Connect package and follow the steps in the wizard.

  5. Install Commerce Server Connect,

    1. Navigate to http://<your site>/sitecore/admin/UpdateInstallationWizard.aspx, and follow the steps in the wizard.

    2. Upload the Sitecore Sitecore Commerce Server Connect update file.

  6. If you are using Solr, set it up now (see the Setting up Solr topic for instructions).

  7. Disable all of the config files under \App_Config\Include\CommerceServer\, except for CommerceServer.config and CommerceServer.Processing.config, by adding .disabled to the end of their file name.

  8. Convert the Sitecore instance to a Processing Server role. See the Configure a processing server topic for detailed steps.