Difference between revisions of "How to configure the Content Manager synchronization services to handle multiple Ad Manager databases"
From Dot2DotCommunications
(→Overview) |
(→Steps) |
||
| Line 6: | Line 6: | ||
== Steps == | == Steps == | ||
| + | |||
| + | === Run the synchronization services installer === | ||
| + | |||
| + | === Remove the default (anonymous) instances of the synchronization services === | ||
| + | |||
| + | === Create one or more named instances of the synchronization services === | ||
| + | |||
| + | === Edit the synchronization service configurations === | ||
| + | |||
| + | == Starting and stopping the services == | ||
| + | |||
| + | == Monitoring the service logs == | ||
Revision as of 09:35, 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.
