This video demonstrates the process of configuring SiteSync between two Sitefinity CMS website environments - source and destination:
Before you configure the SiteSync module, you need to make sure the source and destination environments are identical copies of the same project. When you are starting with one environment only, and must setup an extra environment to which you will promote content via SiteSync, we recommend following these steps:
NOTE: Backup is the most common option, but if your environment or use case scenario requires a different mechanism (such as scripting or packaging) for bringing up an identical database on destination, this is OK. The important element is to have an identical copy of the database configured for the destination environment.
NOTE: The environment-specific settings can be applied directly on the destination environment via changing the configuration files or be handled via config transformations in case of a CD setup. There are no limitations to the approach you prefer, the important part is to ensure your source and destination environments have matching configurations, and only the environment-specific settings differ.
The first step in setting up SiteSync is to install the SiteSync module. By default, this module is disabled, and you must enable it before working with SiteSync. To install the module, follow these steps:
NOTE: The SiteSync module needs to be installed on both source and target environments. Repeat the above steps for any environment that will be used as either source or destination.
To access SiteSync and promote content, you must grant all users that will be promoting content from the source environment the proper permissions to access the SiteSync module. Users in the Administrators role have access to the SiteSync module by default. For more information, see Administration: Security and authentication.
Once you have set up the source and destination environments, installed the SiteSync module, and configured the correct permissions for your users to access the module, you need to proceed with configuring the SiteSync module. This is an important step as it specifies which environment is going to be used as a source or destination for content promotion, as well as the addresses of the destination environments that each source is going to promote content to. The SiteSync module is configured differently depending on whether an environment will be used as source or destination.
To configure SiteSync on your destination and source environments follow these steps:
NOTE: You must configure a different Site key for any environment that will serve as destination for content promotion via SiteSync. If you are promoting content through more than one environment, for example Content Authoring » Staging » Production, the Staging and Production environments will serve as destinations, and need to have different Site keys. The Site key of the next destination environment must always be incremental to the one configured on the previous destination environment. For example, if you have Content authoring » Staging » production, and you have configured Staging to have a Site key value 1, the value on Production must be 2.
RECOMMENDATION: We recommend that the user you just created is reserved for SiteSync usage only, as opposed to logging in to the destination environment. If you log in with this user on the destination environment and try to promote content to this same environment, SiteSync module will fail with a “User already logged in” error.
Once you configured your destination environment, you must proceed by setting up the source environment as well. While on destination environment you take care of setting up Sitefinity CMS to receive data, on the source environment you need to specify where to promote content to. You do this in the following manner:
Click on the Synchronization Settings link on that screen to proceed with configuring SiteSync
NOTE: If you have created the dedicated SiteSync user in a membership provider, different than the default one, you must specify the provider name alongside the username in the Username textbox. You must stick to the following format: providerName\userName.
NOTE: In the most common scenario you are promoting content from one source to one destination environment. If your scenario requires promoting content from one source to multiple destinations, you can add more than one server following the above listed instructions. For more information see Using SiteSync to promote content to multiple destinations.
After a successful Test connection check, you have completed configuring SiteSync on your source environment.
NOTE: The test connection operation does not guarantee that a content promotion will pass successfully, as this requires actual push of data from source to destination. It guarantees only that the sync operation can be run.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2020 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity