Difference between revisions of "How to configure the Content Manager synchronization services to handle multiple Ad Manager databases"
(→Run the synchronization services installer) |
(→Remove the default (anonymous) instances of the synchronization services) |
||
Line 17: | Line 17: | ||
Open a Command Prompt window. | Open a Command Prompt window. | ||
− | Navigate to the Ad Manager CM Sync Services program folder | + | Navigate to the Ad Manager CM Sync Services program folder; for example: |
cd "\Program Files (x86)\Dot2Dot\Ad Manager CM Sync Services" | cd "\Program Files (x86)\Dot2Dot\Ad Manager CM Sync Services" |
Revision as of 16:44, 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.
Remove the default (anonymous) instances of the synchronization services
The synchronization service installer creates the default instances of the publishing service and the playback count retrieval service which would be used if you're handling a single Ad Manager database. If you're going to handle multiple Ad Manager databases, it's best to only use named instances of the services - this way it'll be easier to identify them.
Open a Command Prompt window.
Navigate to the Ad Manager CM Sync Services program folder; for example:
cd "\Program Files (x86)\Dot2Dot\Ad Manager CM Sync Services"
Run the following command:
unregsvc