Progress Sitefinity
Contents
1 Introduction
Progress Sitefinity(R) is an award-winning Web Content Management System empowering teams to independently create and manage content that delivers engaging digital experiences.
The LoadMaster delivers an exceptional, cost effective, and easy to use solution which by employing intelligent server health checking, load balancing, high availability, and security can support an always-on application experience for Sitefinity.
1.1 Document Purpose
This document provides the recommended LoadMaster settings used when providing load balancing for Sitefinity. The Kemp Support team is available to provide solutions for scenarios not explicitly defined. The Kemp Support site can be found at: https://support.kemptechnologies.com.
1.2 Intended Audience
This document is intended to be read by anyone who is interested in configuring the LoadMaster to optimize Sitefinity.
2 Template
Kemp has developed a template containing our recommended settings for this workload. You can install this template to help create Virtual Services (VSs) because it automatically populates the settings. You can use the template to easily create the required VSs with the recommended settings. For some workloads, additional manual steps may be required such as assigning a certificate or applying port following. These steps are covered in the document, if needed.
You can remove templates after use and this will not affect deployed services. If needed, you can make changes to any of the VS settings after using the template.
Download released templates from the following page: LoadMaster Templates.
For more information and steps on how to import and use templates, refer to the Virtual Services and Templates, Feature Description on the Kemp Documentation page.
3 Architecture
Progress Sitefinity deployments consist of multiple front-end servers running the Sitefinity CMS and a back-end SQL Server (SQL clustering recommended).
4 Configure the LoadMaster
Refer to the sections below for details on some recommended global settings.
4.1 Enable Subnet Originating Requests Globally
It is best practice to enable the Subnet Originating Requests option globally.
In a one-armed setup (where the Virtual Service and Real Servers are on the same network/subnet) Subnet Originating Requests is usually not needed. However, enabling Subnet Originating Requests should not affect the routing in a one-armed setup.
In a two-armed setup where the Virtual Service is on network/subnet A, for example, and the Real Servers are on network B, Subnet Originating Requests should be enabled on LoadMasters with firmware version 7.1-16 and above.
When Subnet Originating Requests is enabled, the Real Server sees traffic originating from 10.20.20.21 (LoadMaster eth1 address) and responds correctly in most scenarios.
With Subnet Originating Requests disabled, the Real Server sees traffic originating from 10.0.0.15 (LoadMaster Virtual Service address on eth0) and responds to eth0 which could cause asymmetric routing.
When Subnet Originating Requests is enabled globally, it is automatically enabled on all Virtual Services. If the Subnet Originating Requests option is disabled globally, you can choose whether to enable Subnet Originating Requests on a per-Virtual Service basis.
To enable Subnet Originating Requests globally, follow the steps below:
1. In the main menu of the LoadMaster User Interface (UI), go to System Configuration > Miscellaneous Options > Network Options.
2. Select the Subnet Originating Requests check box.
5 Virtual Services
This step-by-step setup of Virtual Services (VSs) leverages the Kemp application template for Sitefinity. This template configures the Virtual Services to publish Sitefinity with HTTP, HTTPS with TLS/SSL Offloading, or HTTPS with TLS/SSL Reencryption.
The table in each section outlines the settings configured by the application template. You can use this information to manually configure Virtual Services or use the Kemp LoadMaster Application Programming Interface (API) and automation tools.
5.1 Create the Sitefinity - HTTP Virtual Service
The following are the steps involved and the recommended settings to configure the Sitefinity HTTP Virtual Service.
-
In the main menu of the LoadMaster User Interface (UI), go to Virtual Services > Add New.
-
Type a valid Virtual Address.
-
Select the Sitefinity - HTTP template in the Use Template drop-down list.
-
Click Add this Virtual Service.
-
Expand the Real Servers section.
-
Click Add New.
-
Type the Real Server Address.
-
Click Add This Real Server.
-
Repeat these steps to add more Real Servers as needed.
5.1.1 Sitefinity - HTTP Virtual Service Recommended API Settings (optional)
This table outlines the API parameters and values set using the Kemp application template. You can use these settings with scripts and automation tools.
|
API Parameter |
API Value |
|
port |
80 |
|
prot |
tcp |
| VStype | http |
| Schedule | lc |
| Persist | none |
| CheckType | http |
| CheckPort | 80 |
5.2 Create the Sitefinity - HTTPS Offloaded Virtual Services
The following are the steps involved and the recommended settings to configure the Sitefinity HTTPS Offloaded Virtual Service.
-
In the main menu of the LoadMaster User Interface (UI), go to Virtual Services > Add New.
-
Type a valid Virtual Address.
-
Select the Sitefinity - HTTPS Offloaded template in the Use Template drop-down list.
-
Click Add this Virtual Service.
-
Click Virtual Services and View/Modify Services.
-
Click Modify on the Sitefinity - HTTPS Offloaded Virtual Services on port 443.
-
Expand the SSL Properties section.
-
Select the certificate to use from Available Certificates and click the arrow (>) to move it to Assigned Certificates.
-
Expand the Real Servers section.
-
Click Add New.
-
Type the Real Server Address.
-
Click Add This Real Server.
-
Repeat these steps to add more Real Servers as needed.
5.2.1 Sitefinity - HTTPS Offloaded Virtual Service Recommended API Settings (optional)
This table outlines the API parameters and values set using the Kemp application template. You can use these settings with scripts and automation tools.
|
API Parameter |
API Value |
|
port |
443 |
|
prot |
tcp |
| VStype | http |
| SubnetOriginating | 1 |
| Forcel7 | 1 |
| Schedule | lc |
| SSLAcceleration | 1 |
| TLSType | 7 |
| CipherSet | BestPractices |
| CheckType | http |
| CheckUseGet | 1 |
| CheckPort | 80 |
5.3 Create the Sitefinity - HTTPS Reencrypt Virtual Services
The following are the steps involved and the recommended settings to configure the Sitefinity HTTPS Reencrypt Virtual Service.
-
In the main menu of the LoadMaster User Interface (UI), go to Virtual Services > Add New.
-
Type a valid Virtual Address.
-
Select the Sitefinity - HTTPS Reencrypt template in the Use Template drop-down list.
-
Click Add this Virtual Service.
-
Click Virtual Services and View/Modify Services.
-
Click Modify on the Sitefinity - HTTPS Reencrypt Virtual Services on port 443.
-
Expand the SSL Properties section.
-
Select the certificate to use from Available Certificates and click the arrow (>) to move it to Assigned Certificates.
-
Expand the Real Servers section.
-
Click Add New.
-
Type the Real Server Address.
-
Click Add This Real Server.
-
Repeat these steps to add more Real Servers as needed.
5.3.1 Sitefinity - HTTPS Reencrypt Virtual Service Recommended API Settings (optional)
This table outlines the API parameters and values set using the Kemp application template. You can use these settings with scripts and automation tools.
|
API Parameter |
API Value |
|
port |
443 |
|
prot |
tcp |
| VStype | http |
| SubnetOriginating | 1 |
| Forcel7 | 1 |
| Schedule | lc |
| SSLAcceleration | 1 |
| Reencrypt | 1 |
| TLSType | 7 |
| CipherSet | BestPractices |
| CheckType | https |
| CheckUseGet | 1 |
| CheckPort | 443 |
Last Updated Date
This document was last updated on 26 May 2022.