Difference between revisions of "How to configure the Content Manager synchronization services to handle multiple Ad Manager databases"
From Dot2DotCommunications
(Created page with "== Overview == == Steps ==") |
(→Overview) |
||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
| + | |||
| + | Each instance of the '''Dot2Dot Ad Manager CM Publishing Service''' and the '''Dot2Dot Ad Manager CM Playback Count Service''' can be configured to synchronize a single Ad Manager database with one or more Content Manager instances. | ||
| + | |||
| + | If you need to handle more than one Ad Manager databases and you have a powerful server with lots of CPU and memory capacity, you can configure multiple '''''named''''' instances of the synchronization services, each one dedicated to synchronizing a particular Ad Manager database. | ||
== Steps == | == Steps == | ||
Revision as of 09:29, 14 May 2015
Overview
Each instance of the Dot2Dot Ad Manager CM Publishing Service and the Dot2Dot Ad Manager CM Playback Count Service can be configured to synchronize a single Ad Manager database with one or more Content Manager instances.
If you need to handle more than one Ad Manager databases and you have a powerful server with lots of CPU and memory capacity, you can configure multiple named instances of the synchronization services, each one dedicated to synchronizing a particular Ad Manager database.
