Difference between revisions of "How to configure the Content Manager synchronization services to handle multiple Ad Manager databases"
From Dot2DotCommunications
(→Run the synchronization services installer) |
(→Run the synchronization services installer) |
||
| Line 9: | Line 9: | ||
=== Run the synchronization services installer === | === Run the synchronization services installer === | ||
| − | Run the installer | + | [[How To Set Up Publishing To Content Manager#Installing the Synchronization Services|Run the installer]] AmCmSync.msi. |
=== Remove the default (anonymous) instances of the synchronization services === | === Remove the default (anonymous) instances of the synchronization services === | ||
Revision as of 14:36, 14 May 2015
Contents |
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
Run the synchronization services installer
Run the installer AmCmSync.msi.
