Is this really the version you are looking for? Kentico Xperience 8.2 Documentation is no longer updated. Use the switcher in the header to choose your product version.
All web farm synchronization mechanisms, except for automatic configuration, require that all web farm servers are configured in the system. After you choose and enable a synchronization mechanism, start using web farm synchronization by performing the following steps:
OR
Configure web farm servers automatically.If you are running a web farm with a static number of web farm servers (regardless of the chosen synchronization mechanism), configure the web farm servers manually in your system.
Open the Web farm application.
Click New server.
Fill in the following fields:
Click Save to register the server.
Open the web.config file on the particular server and add the CMSWebFarmServerName key into the appSettings section:
<add key="CMSWebFarmServerName" value="ServerCodeName"/>Replace ServerCodeName with the server code name that the system created for the server (or the code name that you manually entered). Every server must contain only one such key with its own name.
Repeat the process for every server in your web farm.
Enter an appropriate license key for the internal URLs of all your web farm servers.
For example, if you use the web farm for domain name example.com and access the servers internally through URLs like:
Enter separate license keys for example.com, 192.168.1.2 and 192.168.1.3 in the Licenses application. You only need to add the licenses on one server and restart the other instances using the System application (click Restart application).
If you are running a web farm with a dynamic number of web farm servers in a combination with the database updater synchronization mechanism, set your system to configure the web farm servers automatically.
This configuration is used on Azure projects by default.
All servers with enabled web farm support add themselves into the list of servers when the application starts.
After you define the web farm servers, enable web farm synchronization in the settings:
You can perform additional low-level settings for web farm synchronization by adding the keys listed in Web.config file settings into the /configuration/appSettings section of your web.config file.
When you have defined the web farm servers and enabled the web farm, go through the following configurations to ensure that your web farm is working properly.
The default session state mode for ASP.NET applications is the InProc mode, which stores session state in the memory of the server. InProc session state mode is not supported on most types of webfarms, because requests for the same session can be served by different servers. This can cause unexpected behavior and data loss. For example, items stored in a shopping cart can disappear after making another request on the website.
If you are using a load balancer in sticky-session mode, you can use the default InProc mode. However, visitors may still experience session loss when a server in the web farm becomes unavailable.
To configure your web farm to store session state data correctly, use one of the following modes:
To use one of these modes, adjust the <sessionState> element and its attributes in the web.config file. For more information, see the Session-State Modes (opens in a new tab) article.
To learn how to configure Azure projects to store session data, see Configuring an Azure project.
By default, the Internet Information Services (IIS) server uses an automatically generated machineKey to encrypt and validate view state and forms authentication information. If a user tries to access the same session from two servers with different machine keys, the validation fails, and a Message Authentication Code (MAC) view state validation error occurs. To prevent this, the machineKey element needs to be the same across all Kentico instances in the web farm configuration.
To learn how to generate a machine key, see Generating a machineKey element.
Never use any websites that will generate a machineKey for you with the click of a button. It is impossible to know whether these keys were created securely or if they are being recorded to a secret database. You should only ever use machineKey configuration elements that you created yourself.
For IIS 7 and below:
Machine keys can be generated in the Machine Key section under ASP.NET in the IIS Manager:
Select your preferred encryption and decryption methods.
Clear the Automatically generate at runtime and Generate a unique key for each application check boxes.
Click Generate keys*.*
Insert the machineKey element into the <system.web> section in the web.config file of all Kentico instances in your web farm configuration.
<system.web>
...
<machineKey decryption="..." decryptionKey="..." validation="..." validationKey="..." />
...
</system.web>Copy the generated decryption and validation keys into the decryptionKey and validationKey attributes.
The decryption and validation attributes need to contain the names of your specified encryption and decryption algorithms. If you left the Decryption method set to Auto when generating the machine keys in the IIS Manager, enter AES as the decryption.
For IIS 8 and above:
The ability to generate machine keys is not available in the IIS Manager 8 or newer. You can use a PowerShell script to generate the machineKey element according to the instructions in this article from Microsoft (opens in a new tab). Insert the generated machineKey element into the <system.web> section in the web.config file of all Kentico instances in your web farm configuration.
The system uses signatures to ensure the security of macro expressions. Macro signatures contain the user name of the macro's author and a hash of the given expression.
The hash function used to create the signatures appends a salt (opens in a new tab) to the input. To ensure that macro expressions work correctly in a web farm environment, you need to configure all servers to use the same hash salt:
Set the CMSHashStringSalt key in the appSettings section of the web.config file to the same value on all web farm servers. For example:
<add key="CMSHashStringSalt" value="e68b9ad6-a461-4707-8e3e-ece73f03dd02" />The best option is to set the hash salt value before you start creating content for your website. Changing the salt causes all current hash values to become invalid. To fix existing macro expressions in the system after changing the hash salt, you need to re-sign the macros. See Working with macro signatures for more information.
If you are using a web farm, scheduled tasks will be executed randomly by one of the servers. However, certain scheduled tasks, which work with the application file system, should be executed by each server in the web farm.
The following scheduled tasks must be executed by each server in a web farm, if you are NOT using a shared file storage (Azure Blob Storage or Amazon S3 storage):
The following scheduled task must be executed by each server in a web farm regardless of the used file storage:
To configure these tasks to be executed by each server in a web farm, clone the original tasks and configure them to be executed on specific servers:
Perform this procedure for all scheduled tasks listed above.
When creating new scheduled tasks, you can ensure that the task is created for all web farm servers by selecting the Create tasks for all web farm servers check-box.
If you use an SSL offload device or accelerator as part of your web farm and your website is configured to require SSL for the administration interface or on specific pages, you may encounter problems with redirection loops.
For this type of scenario, you need to add some custom code to your website according to the instructions in SSL accelerator support.
If your environment uses unique port numbers to identify web farm servers (for example with a load balancer that internally maps URLs to ports), the system generates certain types of URLs with the internal port number. Such URLs may not be processed correctly, leading to problems with related features (for example GetResource requests for files).
To resolve these problems, add the following key into the appSettings section of the web.config file on all servers:
<add key="CMSURLPort" value="80" />The key ensures that the system generates all URLs without the port number (the default HTTP port is used).