Building a Processing Server role
The role 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, you must register them 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.
To set up a Processing Server, use the following steps:
-
Create the accounts to be used as app pools. For more information, go to What are the required accounts and groups to create?.
-
Install Sitecore. For more information, go to Sitecore installation.
-
Install, but do not configure, Commerce Server.
-
Install Commerce Connect:
-
From the Sitecore Launchpad, click on → → → , and follow the steps in the wizard.
-
Upload the Sitecore Commerce Connect package.
-
-
Install Commerce Server Connect:
-
Navigate to http://<your site>/sitecore/admin/UpdateInstallationWizard.aspx, and follow the steps in the wizard.
-
Upload the Sitecore Commerce Server Connect update file.
-
-
If you are using Solr, set it up now. For more information, go to Setting up Solr and Configure Solr.
-
In the \App_Config\Include\CommerceServer\ folder, append all files with .disabled except for CommerceServer.config.
-
In the \App_Config\Include\CommerceServer\ folder, append all files with .disabled except for CommerceServer.Processing.config.
-
Convert the Sitecore instance to a Processing Server role. For more information about setting up a processing server, go to Configure a processing server.