PT Sync Multi Server Configuration

From ADF Docs
Jump to: navigation, search


The following feature is implemented to sync custom element data across multiple CommonSpot servers and sites.

The steps below identify the configurations to setup and configure.


  1. On the source ColdFusion server, setup ColdFusion data sources to point to the destination servers CommonSpot server sites database table. This is not the CommonSpot site specific database, this is the server sites database.
  2. Within the PT Sync App directory, locate the following XML file (/ADF/apps/pt_sync/site_files/_cs_apps/config/ptSync.xml).
  3. Copy this file into the source site directory (/_cs_apps/config/). If the directory does not exist, then create it.
  4. Update the XML file that was copied into the source site. The XML file is formatted to build a relationship for CommonSpot servers that are connected into the sync process.
  5. The following example with setup the configuration for a server named "csServer1" and contains two sites named "mySite1" and "mySite2". Also, another server named "csServer2" and contains a single site named "myOtherSite1".
<?xml version="1.0" encoding="utf-8"?> 
  1. The XML data structure in this format will produce the following ColdFusion structure to work with in the PT Sync application config.

Pt sync multi server config1.jpg

Enable Multi Server

  1. Navigate to the App Configuration Manager page.
  2. Edit the record and open the "Features" tab. Update the "Enable Multi Server Configuration" field to "True".
  3. Submit the form and Reset the ADF for the server and site.
  4. Edit the record again and now the "ptSync Configuration" tab will have the servers and sites configured in the XML file populate the select fields for Source Site and Destination Site.
  5. Select the correct and site under the correct server.
  6. Submit the form and Reset the ADF for the server and site.
  7. Navigate to the Mapping Manager page.
  8. Edit all the mapping records. Only editing and submitting the form will solve this. This is needed to update the mapping record with the destination custom element for the new destination site.