In addition to the official documentation on Sitecore Experience Edge for XM, it is important to understand the way Sitecore Experience Edge can be managed. Sitecore offers managed services for Experience Edge as part of the Sitecore Managed Cloud portfolio, but customers can also choose to self-manage their solution and integration with Sitecore Experience Edge. This document presents details on both approaches.
When customers finalize their contract for Sitecore Experience Edge, it can be in the form of either Sitecore Experience Edge stand-alone or Sitecore Experience Edge as part of a Sitecore Managed Cloud solution. For both options, provisioning will be completed by the Sitecore Manage Cloud team. When the contract is received, the Experience Edge deployment will be created. As part of the workflow for both options, a ticket in the Sitecore Support Portal will be created in the customer’s account to securely communicate the details for the new Experience Edge deployment. The details include:
Refer to the Experience Edge documentation for how these details can be put to use.
Customers that are self-managing their implementation are responsible for taking the details in the new Experience Edge deployment ticket and integrating their Sitecore solution according to their requirements. For example, a customer might want to install the Experience Edge Connector module to start making use of Experience Edge from their Sitecore CM.
If customers need a new Experience Edge tenant or are having challenges with their implementation, the regular Sitecore support channels are available to assist.
When customers run their implementation in the Sitecore Managed Cloud, in addition to the normal workflow used when Provisioning Sitecore Experience Edge (described previously), additional services from Sitecore are available including:
One Experience Edge deployment can be created and used for each Sitecore XM deployment. This 1:1 mapping is the best practice. To determine how many Experience Edge deployments a customer could request, refer to the Sitecore License. Under the "Sitecore.Environment" XML node, one can find the licensed production environment count; this example shows 1:
<Object Id="Sitecore.Environment" xmlns="http://www.w3.org/2000/09/xmldsig#"><module xmlns=""><idref>...</idref><name>Sitecore.Environment</name><count>1</count>
Under the "Sitecore.Env.NonProd" XML node, one can find the licensed non-production environment count; this example shows 3:
<Object Id="Sitecore.Env.NonProd" xmlns="http://www.w3.org/2000/09/xmldsig#"><module xmlns=""><idref>...</idref><name>Sitecore.Env.NonProd</name><count>3</count>
Note that some older Sitecore licenses might show a very high count, like 10,000 – this was effective for an unlimited environment license. The expectation is that each customer deployment would connect to one Experience Edge deployment, so if a customer has 4 environments total there would be 4 Experience Edge environments to match.
There may be additional support options available via paid engagement with the Sitecore Professional Services team. If you have any questions related to this topic, contact your Sitecore CSM or your regional Sitecore representative.