To configure the delivery of static personalized content in multiple regions, you need to make several adjustments to some of the configuration files.
Open the web.config file of all Sitefinity CMS instances that are part of the Primary and the Secondary region and make the following configurations:
restrictionLevel
<telerik>
machineKey
Open the DataConfig.config file and make the following configurations:
DataConfig.config
replication=”Master”
replication=”Slave”
Primary region: The DataConfig.config file of all Sitefinity CMS instances that participate in the Primary region should look in the following way:
Secondary region(s): The DataConfig.config file of all Sitefinity CMS instances that participate in the Primary region should look in the following way:
replication="Master"
replication="Slave"
replication="None"
Open the LibrariesConfig file of the Secondary region and for every Sitefinity CMS instance that is part of the region, disable dynamic resizing of images, because it requires database writes operations.
LibrariesConfig
LibrariesConfig.config
NOTE: If you do not have a LibrariesConfig.config file, create one and place it in folder ~\App_Data\Sitefinity\Configuration.
~\App_Data\Sitefinity\Configuration
Open the SchedulingConfig file of the Primary and the Secondary region and for every Sitefinity CMS instance that is part of the respective region, reconfigure the config file to use the respective Session database, which is dedicated per region.
SchedulingConfig
SchedulingConfig.config
NOTE: If you do not have a SchedulingConfig.config file, create one and place it in folder ~\App_Data\Sitefinity\Configuration.
Statistics must be stored in the respective Session database. Open the StatisticsConfig.config file of the Primary and the Secondary region and for every Sitefinity CMS instance that is part of the respective region, reconfigure the config file to use the respective Session database, which is dedicated per region.
StatisticsConfig.config
NOTE: If you do not have a StatisticsConfig.config file, create one and place it in folder ~\App_Data\Sitefinity\Configuration.
User activities must be stored in the respective Session database. Open the UserActivityConfig.config file of the Primary and the Secondary region and for every Sitefinity CMS instance that is part of the respective region, reconfigure the config file to use the respective Session database, which is dedicated per region.
UserActivityConfig.config
NOTE: If you do not have a UserActivityConfig.config file, create one and place it in folder ~\App_Data\Sitefinity\Configuration.
Open the SystemConfig.config file and make the following configurations:
SystemConfig.config
Primary region: The SystemConfig.config file of all Sitefinity CMS instances that participate in the Primary region should look in the following way:
Secondary region(s): The SystemConfig.config file of all Sitefinity CMS instances that participate in the Secondary region should look in the following way:
NOTE: If you do not have a SystemConfig.config file, create one and place it in folder ~\App_Data\Sitefinity\Configuration.
You should add a metadata provider that uses the respective Session database. Open the MetadataConfig.config file of the Primary and the Secondary region and for every Sitefinity CMS instance that is part of the respective region, reconfigure the config file to use the respective Session database, which is dedicated per region.
MetadataConfig.config
NOTE: If you do not have a MetadataConfig.config file, create one and place it in folder ~\App_Data\Sitefinity\Configuration.
Output cache feature must use the respective Session database. Open the OutputCacheConfig.config file of the Primary and the Secondary region and for every Sitefinity CMS instance that is part of the respective region, reconfigure the config file to use the respective Session database, which is dedicated per region.
OutputCacheConfig.config
NOTE: If you do not have a OutputCacheConfig.config file, create one and place it in folder ~\App_Data\Sitefinity\Configuration.
Open the SecurityConfig.config of each Sitefinity CMS instance in the Primary region and the Secondary region(s) and make sure that all Sitefinity CMS instances in each region have exactly the same values for authCookieName, rolesCookieName, loggingCookieName, validationKey, and decryptionKey properties.
SecurityConfig.config
authCookieName
rolesCookieName
loggingCookieName
validationKey
decryptionKey
Restart Sitefinity CMS by restarting the IIS application pool.
Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.
This free lesson teaches administrators, marketers, and other business professionals how to use the Integration hub service to create automated workflows between Sitefinity and other business systems.
This free lesson teaches administrators the basics about protecting yor Sitefinity instance and its sites from external threats. Configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.
The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important