Content Management (CM)
The Content Management (CM) role enables authors to create, manage, and publish content.
Supported infrastructure
You can host the CM role on:
Refer to the Sitecore compatibility table for compatible versions.
Reference structure
The CM role has its place in the Sitecore reference structure. It can be referenced by other roles, and it can also reference other roles.
Referenced by
The CM role is referenced by the following roles:
References
The CM role references the following roles:
Storage roles
|
Role name |
Connection string name |
Port |
Type |
Notes |
|---|---|---|---|---|
|
master |
1433 |
SQL | ||
|
core |
1433 |
SQL | ||
|
security |
1433 |
SQL | ||
|
web |
1433 |
SQL | ||
|
reporting |
1433 |
SQL |
Connection required for reporting database re-build even if you having a dedicated xDB Reporting role. | |
|
messaging |
1433 |
SQL |
If you install using SIF, SQL is the default provider. Not applicable to Experience Manager. | |
|
443 |
Azure Service Bus |
If you install Sitecore on Azure, Azure Service Bus is the default provider. Azure Service Bus is available in 9.2 and later. | ||
|
experienceforms |
1433 |
SQL |
The connection strings for the Forms database and for file storage are the same by default. You can create your own file storage provider with a custom connection string. See Manage file storage for forms and The security roles in Sitecore Form for details. | |
|
exm.master |
1433 |
SQL |
Not applicable to Experience Manager | |
|
session |
1433 |
SQL |
Optional, for SQL session state provider | |
|
6379 |
HTTP |
Optional, for Redis session state provider | ||
|
sharedsession |
1433 |
SQL |
Optional, for SQL session state provider | |
|
6379 |
HTTP |
Optional, for Redis session state provider |
On-premise application roles
|
Role name |
Connection string name |
Port |
Type |
|---|---|---|---|
|
xconnect.collection |
443 |
HTTPS | |
|
xconnect.search |
443 |
HTTPS |
The following client certificates and keys are required in a secure production environment:
|
Role |
Connection string name |
Type |
|---|---|---|
|
xconnect.collection.certificate |
Certificate | |
|
xconnect.search.certificate |
Certificate |
Azure application roles
On XP1 topologies deployed on Azure, the xConnect Collection Search service has a dedicated connection string. This is to separate the collection requests from the search and indexing requests. The xConnect Collection Search service is hosted under a basic hosting plan which might not have enough resources for collection, search, and indexing requests.
|
Role name |
Connection string name |
Port |
Type |
Notes |
|---|---|---|---|---|
|
xconnect.collection |
443 |
HTTPS |
Hosted on a resource intensive plan. | |
|
xconnect.search |
443 |
HTTPS |
Hosted on a basic plan. |
The following client certificates and keys are required in a secure production environment:
|
Role |
Connection string name |
Type |
Notes |
|---|---|---|---|
|
xconnect.collection.certificate |
Certificate | ||
|
xconnect.search.certificate |
Certificate |
Application roles for both on-premise and Azure
|
Role name |
Connection string name |
Port |
Type |
Notes |
|---|---|---|---|---|
|
xdb.referencedata.client |
443 |
HTTPS | ||
|
xdb.marketingautomation.operations.client |
443 |
HTTPS | ||
|
xdb.marketingautomation.reporting.client |
443 |
HTTPS | ||
|
N/A - see notes |
443 |
HTTPS |
The xDB Reporting service URL is configured in <content management root>\App_Config\Sitecore\Marketing.xDB\Sitecore.Xdb.Remote.Client.config | |
|
N/A - see notes |
443 |
HTTPS |
The xDB Processing service URL is configured in <content management root>\App_Config\Sitecore\Marketing.xDB\Sitecore.Xdb.Remote.Client.config | |
|
N/A - see notes |
443 |
HTTPS | ||
|
N/A - see notes |
80/443 |
HTTP/HTTPS |
Service url is configured in the <content management root>\App_Config\Modules\PublishingService\Sitecore.Publishing.Service.Config | |
|
N/A - see notes |
5000 |
HTTPS |
Service url is configured in the <content management root>\App_ConfigIncludeY.Commerce.Engine\Sitecore.Commerce.Engine.Connect.config | |
|
sitecore.reporting.client |
443 |
HTTPS |
If you have a dedicated xDB Reporting role or xDB Processing role, you must include the following API key in the CM connection strings configuration file:
|
Role |
Connection string name |
Type |
Notes |
|---|---|---|---|
|
reporting.apikey |
Unique string |
Required if you use a dedicated xDB Reporting role. Not required if CM connects directly to the reporting database. | |
The following client certificates and keys are required in a secure production environment:
|
Role |
Connection string name |
Type |
Notes |
|---|---|---|---|
|
xdb.referencedata.client.certificate |
Certificate | ||
|
xdb.marketingautomation.operations.client.certificate |
Certificate | ||
|
xdb.marketingautomation.reporting.client.certificate |
Certificate | ||
|
sitecore.reporting.client.certificate |
Certificate | ||
|
EXM Dispatch |
EXM.CryptographicKey |
Key | |
|
EXM Dispatch |
EXM.AuthenticationKey |
Key | |
|
Sitecore Identity |
sitecoreidentity.secret |
Key |
Search indexes
The Content Search provider determines how the CD role connects to the indexes. Sitecore supports Azure Search and Solr.
|
Index |
Port, Solr |
Port, Azure Search |
Type |
Notes |
|---|---|---|---|---|
|
8983 |
443 |
HTTPS | ||
|
8983 |
443 |
HTTPS | ||
|
8983 |
443 |
HTTPS | ||
|
8983 |
443 |
HTTPS |
Only for XP installations | |
|
8983 |
443 |
HTTPS |
Only for XP installations | |
|
8983 |
443 |
HTTPS |
Only for XP installations | |
|
8983 |
443 |
HTTPS |
Only for XP installations | |
|
8983 |
443 |
HTTPS |
Only for XP installations | |
|
8983 |
443 |
HTTPS |
Only for XP installations | |
|
8983 |
443 |
HTTPS |
Only for XP installations | |
|
8983 |
443 |
HTTPS |
Only for XP installations | |
|
8983 |
443 |
HTTPS |
Only for XP installations |
For more information, see:
Cloud Services
|
Role Name |
Port |
Type |
Endpoint URL |
|---|---|---|---|
|
443 |
HTTPS |
geoip-ces.cloud.sitecore.net | |
|
443 |
HTTPS |
devicedetection-ces.cloud.sitecore.net | |
|
443 |
HTTPS |
Multiple endpoints |
For more information, see:
Other
The CM role includes a reference to the Package Management Service via the PackageManagementServiceUrl connection string.
Privacy and security
The CM role handles personal data in the following ways:
-
Handles authentication and authorization of content editors and other business users.
-
Allows the management of website user accounts and authorization.
-
Hosts the business tools for accessing and managing Experience Database contacts and interactions.
-
Hosts the Experience Profile which shows Commerce customer and order information.
Refer to the Security Guide for steps to secure the CM role.