Switch from on-premises to cloud indexes
Switch from on-premises to cloud indexes
Moving to Coveo cloud indexes opens customers to a world of powerful relevance features, future readiness, and convenience.
There are many differences between a cloud and an on-premises index which require changes to your Sitecore configuration.
|
Because you’re changing the location of your indexes, you will also need to reconfigure all of your sources on the Coveo Platform, including those external to Sitecore. |
Step 1: Change your organization from on-premises to Cloud
Coveo for Sitecore needs to have access to a Coveo organization, whether you’re using a cloud or an on-premises installation. However, those organizations are different for cloud and on-premises installations, which means that your Sitecore instance will need to connect to a different organization.
-
In the Sitecore Control Panel, under Coveo Search, select Configure.
-
Under Configure Coveo Cloud Organization, click Configure.
-
In the Coveo Cloud Organization panel:
-
If you already have access to a cloud organization, select it, and click Next.
-
If you don’t have access to a cloud organization, select Create new organization.
-
Under Organization configuration, choose a name for your organization.
-
Under Select your license plan, select Cloud Edition Trial.
-
Click Next.
-
-
-
Your Sitecore instance is now connected to a cloud organization.
|
Note
A Standard Cloud, Pro Cloud, or Enterprise Cloud license is required for a production Coveo cloud index. |
Step 2: Remove deletion of AddAnonymousEmailUserIdentity
In an on-premises installation, the AddAnonymousEmailUserIdentity
processor is deleted, as CES handles permissions on its own.
However, in a cloud installation, it needs to be reactivated.
-
Open your
<SITECORE_INSTANCE_ROOT>\App_Config\Include\Coveo\Coveo.SearchProvider.Custom.config
file using a text editor. -
Delete or comment the
<patch:delete />
element in the section below.<getSearchUserIdentities> <processor name="AddAnonymousEmailUserIdentity"> <patch:delete /> </processor> </getSearchUserIdentities>