Load Balancing
Created by Orckestra
Load Balancing Setup Guide
- Introduction
- Getting started
- Pre-installation setup
- Installation
- Post-installation setup and use
- Configuration
Post-installation setup and use
Once you’ve installed the Load Balancing add-on, go on to deploy copies of the website on other servers.
These copies (nodes) are not required to be part of a NLB setup. You can also may have a mixed setup where some nodes are part of the NLB and some are not.
You may want to consider having a dedicated instance of the website for the CMS Console administration.
Preparing another node in your cluster
- Set up a new server and join it to your load balanced cluster.
- Copy your C1 CMS website to the new machine.
- Set up a new IIS site in accordance to the C1 CMS version you are running
Please see also “Configuration”.
Deploying the Website on Multiple Servers
Once you've finished the setup, make a copy of the website to deploy it on other servers. You can use the XML-Based Site Backup add-on to make a zipped copy of the website. (Please note that the website files will be zipped only – the SQL database in use will not be backed up.)
Then go on and deploy it on as many servers as you need.
Making a dedicated instance for the CMS Console administration
The Load Balancing add-on does not synchronize all the website files (please see “Limitations”.
We thus recommend that you have set up one dedicated instance for the CMS Console administration.
To disable usage of the CMS Console in production sites:
- Completely remove the "/Composite" folder from the website.
- For Composite C1 (now “C1 CMS”) version 4.2 (Update 1) or earlier only, also remove references to AdministrativeAuthorizationHttpModule from web.config.
Users maintaining content should not take any further steps to ensure content change synchronization after the add-on has been installed and the cluster set up.
The Load Balancing add-on will synchronize all changes to content and media files automatically.
Developers that make changes to website files such as CSS documents or Razor functions are responsible for synchronizing these changes across servers on their own.