Scaling and configuring Content Management
Content Management (CM) roles enable content editors to create and publish content. You can configure multiple CM instances to meet your scaling requirements.
Installation
Use the Sitecore Installation Framework (SIF) or the Sitecore Azure Toolkit (SAT) to install the Content Management role. Refer to the installation guide for your version of the platform for more information.
Scaling the Content Management role
The following table describes the way you can scale the Content Management role:
|
Scaling option |
Supported |
Notes |
|---|---|---|
|
Combined instance |
Yes |
The following combinations are supported:
Note In a developer environment, all Core roles can be combined into a single instance. This includes Content Management, Content Delivery, xDB Processing, xDB Reporting, and EXM Dispatch. This setup is not recommended in production. |
|
Standalone instance |
Yes |
You can deploy Content Management as a standalone role. |
|
High availability and failover |
Yes |
You can fail over to a passive instance or set up multiple active instances behind a load balancer. |
|
Horizontal scaling for load distribution |
Yes |
You can set up multiple instances behind a load balancer. All instances must connect to a centrally located Master database. Note Out-proc session state management is not officially supported. We recommend that you use in-process session state and sticky sessions. |
The following general recommendations apply to all scaling scenarios:
-
Deploy the Content Management role as close as possible to the Master database.
Performance tuning tasks
Consider the following performance tuning options:
-
Set up a dedicated device to handle encryption/decryption of incoming requests.
-
To improve publishing performance of classic publishing, consider reviewing the DeepScan setting.
Security configuration tasks
Refer to the Content Management section of the Security guide.
General configuration tasks
The following general configuration tasks apply to the Content Management role:
-
Update Core role license files. You must perform this task on all instances of the Content Management role if your Sitecore license changes or expires.
-
Enable/disable the indexing sub-role. The indexing sub-role is enabled on the Content Management role by default. If you have more than one instance of the Content Management role, you must disable indexing on all except one instance.
-
Disable the robot detection component. The robot detection component is disabled by default on the Content Management role, and may cause errors if enabled.
Default topologies and packages
The following tables list the topologies that include the Content Management role and how the role is packaged by default.
Sitecore Installation Framework
The Content Management role is available in the following default topologies for the Sitecore Installation Framework:
|
Topology |
Web Deploy Packages |
Description |
|---|---|---|
|
XP Single |
|
Content Management is bundled with all other Core roles. Not recommended in a production environment. |
|
XP Scaled |
|
Standalone instance of Content Management. |
|
XM Scaled |
|
Standalone instance of Content Management. |
Sitecore Azure Toolkit
The Content Management role is available in the following default topologies for the Sitecore Azure Toolkit:
|
Topology |
Web Deploy Packages |
Description |
|---|---|---|
|
XP Single |
|
Content Management is bundled with all other Core roles. Not recommended in a production environment. |
|
XP Scaled |
|
Standalone instance of Content Management. |
|
XM Scaled |
|
Standalone instance of Content Management. |
|
XM Single |
Sitecore 9.2.0 rev. 002893 (XM) (Cloud)_single.scwdp.zip |
Content Management is bundled with Content Delivery. Not recommended in a production environment. |