Documentation Center

Scaling Online Marketing Explorer

You can scale up the Aggregation Framework by adding more cores to the machine to speed up data processing and scale out Synchronization Servers for Online Marketing Explorer.

The following diagram shows where you can scale Online Marketing Explorer:

Scaling on the Content Management system

Aggregation Framework (single Content Manager Database)
If you have the Online Marketing Explorer GUI installed on one or more Content Manager Servers which are configured to get data from a single Content Manager database, you need to install the Aggregation Framework on one of these machine—or on a separate machine—and then configure the connection to the same Tridion Aggregation Service.
You can configure the connection when you run the installer. The installer updates your web.config file:
<endpoint address="http://localhost:2600/AggregationDataService" 
          binding="basicHttpBinding" bindingConfiguration="basicHttpBinding_IDataProviderService" 
          contract="AggregationDataService.IDataProviderService" name="Reporting_IDataProviderService">				
        <identity>					
          <dns value="localhost"/>
        </identity>			
</endpoint>
Aggregation Framework (multiple Content Manager Databases)
If you have the Online Marketing Explorer GUI installed on several Content Manager Servers each using a separate Content Manager databases, you need to install the Aggregation Framework on each Content Manager Server. Each Aggregation Framework serves a separate Aggregation database.
Upscaling Aggregation Framework
You can scale up the Aggregation Framework by adding more cores to the machine to speed up data processing. The <aggregationFramework> section in the Tridion.Aggregation.config file—the Online Marketing Explorer configuration file on the Content Manager Server—has the following settings to control performance and outscaling:
  • maxAggregationThreads (mandatory)—the number of threads used to aggregate tracked data. Each batch is split into equal parts and each part is processed in its own thread. The minimum value is 1, and it is recommended to set the maximum value to no greater than the number of cores on the server. You can limit the number of cores that Tridion Aggregation Service uses by setting this value.
  • maxAggQueueLength (optional)—the maximum number of work items in the aggregation queue. If aggregation is slow, do not set maxAggQueueLength too high because batches will start to experience timeout failure on the synchronization server. The default value is 4, and the minimum value is 1.

Scaling the Content Delivery system

Tracking database
On the Content Delivery side, if you have one Web site served by one Content Data Store using multiple Web servers you need to install Tracking on each Web server.
You can store Tracking data in the same Content Broker Database that is used for published content, or in a separate database. If you have high database load, it is recommended to redirect tracked data to a separate database to make sure that tracking mechanism does not increase the load on the content database.
Outscaling Synchronization Servers
If different Web servers store tracked data in separate databases, you should install and configure one Synchronization Server for each database which contains tracked data. You can configure multiple synchronization servers for each database.