Configure a content management server to use a remote Reporting Service server

Last updated Thursday, August 31, 2017 in Sitecore Experience Platform for Administrator

When you configure a content management server, if you want to use a remote, dedicated Reporting Service server, there are some additional steps you must follow.

To configure a content management server to connect to a dedicated Reporting Service server:

  1. On your content management server, in the Website/App_ Config/Include folder, enable the Sitecore.Xdb.Remote.Client.config configuration file.
  2. In the Sitecore/httpTransportFactory node, change the serviceUrl parameter to point to your reporting server.
  3. Disable the Sitecore.Xdb.Remote.Server.config file.

Note

All Remote.Client.config files are disabled by default. You should enable these files if you have a reporting server in another location. Disable these files on a content delivery server and enable them on a content management server. The <httpTransportFactory /> node in the Sitecore.Xdb.Remote.Client.config file must contain the base URL of the remote data server. If you are using the Sitecore xDB Cloud 1.0 do not enable the Sitecore.Xdb.Remote.Client.config file.

Configure Path Analyzer

If you connect to a dedicated remote reporting instance, then the content management server no longer has direct access to the Sitecore.Analytics SQL Server reporting database. Instead, the Path Analyzer client retrieves data from a remote reporting server with direct access to the SQL database using Web API services.

Note

This does not apply to Sitecore xDB Cloud 1.0 Edition.

To enable the Path Analyzer client to communicate with the remote reporting server, make the following configuration file changes:

Configuration file

Folder

Enable

Disable

Sitecore.PathAnalyzer.RemoteClient.config

App_Config/Include

Picture 154

Sitecore.PathAnalyzer.Processing.config

App_Config/Include

Picture 155

Sitecore.PathAnalyzer.Services.RemoteServer.config

App_Config/Include

Picture 156