Sitecore xDB Cloud comes with open tenancy improvements for increased privacy in the Cloud. You connect to xDB Cloud by following the standard Sitecore configuration guidelines.
Before configuring Sitecore for xDB Cloud 2.0, you must ensure that you are running Sitecore 8.0 or later and you must upgrade to the latest supported update for the Sitecore version that you are running. See the xDB Cloud service compatibility tables for the list of versions that are supported by the xDB Cloud service for new xDB Cloud customer sets.
This topic describes how to:
- Request the xDB Cloud 2.0 customer set
- Prepare a scaled on-premise Sitecore environment
- Prepare a standalone Sitecore instance
- Upgrade the xDB Cloud components
- Configure the xDB Cloud client and connection to the xDB Cloud service
Request the xDB Cloud 2.0 customer set
To request an xDB Cloud 2.0 customer set, register a support ticket through the Sitecore Support portal. If you do not have a valid Sitecore certification you must contact your Sitecore Implementation Partner to register the support ticket for you. If this is not possible, contact your Sitecore representative to access the Sitecore Support portal. Ensure that you include:
- Your License ID.
- Your deployment ID.
- The version of Sitecore that you are running.
- The preferred location for your xDB Cloud environment. See the xDB Cloud Service compatibility tables for compatible data center locations. You will receive the following from Sitecore Support:
- MongoDB connection strings:
- A Search index connection string (applicable to Sitecore 8.2.1 and later):
- Reporting service settings, including the address of the service and the thumbprint of the SSL certificate.
Prepare a scaled on-premise Sitecore environment
This procedure describes how to prepare a local Sitecore environment. To prepare a standalone Sitecore instance, skip to the next section.
The Sitecore xDB Cloud service for 2.0 supports scaled Content Management (CM) and Content Delivery (CD) servers. You do not need to set the database connection strings at this stage because you do it later when you configure the xDB Cloud client and connection to the xDB Cloud service.
To prepare a local scaled on-premise Sitecore environment:
- Download the spreadsheet that lists of all the configuration files that you must enable or disable for each server type.
- For Sitecore 8.0, refer to the table of files to enable or disable to configure a Content Delivery server.
- For Sitecore 8.1, Update 1, and Update 2, download the Config Enable Disable Excel spreadsheet for Sitecore 8.1.
- For Sitecore 8.1 Update 3, download the Config Enable Disable Excel spreadsheet for Sitecore 8.1 Update 3.
- For Sitecore 8.2, download the Config Enable Disable Excel spreadsheet for Sitecore 8.2 initial release.
- For Sitecore 8.2 Update 1, download the Config Enable Disable Excel spreadsheet for Sitecore 8.2 Update 1.
- For Sitecore 8.2 Update 2, Update 3, Update 4, and Update 5, download the Config Enable Disable Excel spreadsheet for Sitecore 8.2 Update 2-5.
- For Sitecore 8.2 Update 6, download the Config Enable Disable Excel spreadsheet for Sitecore 8.2 Update 6.
- Configure the CD servers, by following the instructions in the Configure a content delivery server topic. However, you must also:
- Go to the Configure a content delivery server section and follow the instructions. Skip the steps that require you to set the database connection strings for MongoDB.
- In the Config enable disable spreadsheet, consult the Content Delivery (CD) column and ensure that the relevant configuration files are enabled and disabled.
- Refer to the Changes to configuration file settings table and update the parameter values of your configuration files accordingly.
- Configure the CM servers, by following the instructions in the Configure a content management server topic. However, you must also:
- Go to the Configure a content management server section and follow the instructions. Skip the steps that require you to set the database connection strings for MongoDB.
- In the Config enable disable spreadsheet, consult the Content Management (CM) column and ensure that the relevant configuration files are enabled and disabled.
Prepare a standalone Sitecore instance
This procedure describes how to prepare a standalone Sitecore environment. To prepare a scaled on premise Sitecore environment see the previous section.
For development and demonstrations purposes, you can configure a standalone instance of Sitecore to use with xDB Cloud 2.0. Ensure that you use dedicated CD and CM instances in your production environment.
To use a Sitecore standalone instance with xDB Cloud 2.0:
- Ensure that the following configuration files are disabled or removed from your local installation by adding
.disabledto the end of the file name.
File path (relative to the website root)
Configuration file name
- Follow all of the instructions in Configure a content management server to use a remote Reporting Service server. Ensure you enable and disable your configuration files according to the table in the Configure Path Analyzer section: Configure Path Analyzer.
Upgrade the xDB Cloud components
To connect to xDB Cloud 2.0 you must first upgrade the cloud components on your Sitecore installation
To install the Cloud components package:
- In the XdbCloud folder (
Website/App_Config/Include), delete the following files. If they already have the
.disabledextension, it is a good idea to delete them at this point.
- Use the Sitecore Installation Wizard to install the package.
Configure the xDB Cloud client and connection to the xDB Cloud service
When the CD and CM instances are installed and configured, the next stage is to configure them to communicate with dedicated Azure services of Sitecore xDB Cloud.
- In the
App_Config), configure the MongoDB database connection strings by using the connection strings from the response that you received from Sitecore Support.
The MongoDB connection strings:
- In the
App_Config), add the search index connection string from the response that you received from Sitecore Support. For versions 8.2-Update1 and later, the connection string will look like this for example:
<add name=" cloud.search" connectionString="[cloud.search connection string
- In the
App_Config), ensure the following connection string is removed:
<add name="reporting" connectionString="Data Source=…"/>
- For versions 8.2 Update-1 and later, go to the Xdb Cloud folder (
Include/), enable the following configuration files:
For versions prior to 8.2 Update-1:
- In the Xdb Cloud folder (
Include/), disable the following configuration files:
- In the
Xdb Cloud), configure the reporting service by using the actual Service URL and SSL certificate thumbprint from the response that you received from Sitecore Support, for example:
<httpTransportFactory patch:instead="httpTransportFactory" type="Sitecore.Cloud.Xdb.CloudBasedTransportFactory, Sitecore.Cloud.Xdb" singleInstance="true">
<param desc="serviceUrl">[reporting service URL]</param>
<param desc="certificateThumbprint">[SSL certificate thumbprint]</param>
Deploy marketing definitions
To complete the xDB Cloud client configuration and connection to the xDB Cloud service, you must deploy marketing definitions.
If you are using the Sitecore Experience Database (xDB) functionality, you must first set the
Xdb.Tracking.Enabled parameters to true. If you do not do this, you cannot deploy marketing definitions.
To deploy marketing definitions:
- On the Sitecore Launchpad, click Control Panel, Analytics, Deploy marketing definitions.
- In the Deploy marketing definitions dialog box, select all of the definitions and taxonomies and click Deploy.
If you do not do this, the binary data stored in the Data column in the definition tables (CampaignActivityDefinitions, GoalDefinitions), might not be compatible with Sitecore XP 8.2 rev. 170407 (Update-3).