Deploy on Additional Content Managers
Deploy on Additional Content Managers
If your setup has more than one content management instance, you also need to copy the Coveo for Sitecore package and the Coveo data to the other CMs.
Make sure that you have already configured a Content Manager for a scaled environment (see Prepare the Main Sitecore Content Manager for a Scaled Environment).
Step 1: Copying the Package to an Additional CM
The Coveo for Sitecore installation package contains several files that are added to the Sitecore website directory.
-
Locate the installation package you used for the content manager (see Releases and Downloads).
-
Unzip the
Coveo for Sitecore X.Y <BUILD_NUMBER>.zip
. -
Open the
package.zip
file. -
In the
package.zip
compressed folder, copy the content of thefiles
folder to<SITECORE_INSTANCE_ROOT>\Website\
on the additional CM.
The files
folder mimics the folder structure found in the Sitecore website.
Step 2: Ensuring Access to the Encryption Keys
Coveo for Sitecore stores its encryption keys in the Properties
table of a database.
These encryption keys must be the same on all the Sitecore instances to be able to decrypt the encrypted configuration elements.
The <Database>
setting in the Coveo.SearchProvider.config
file determines the encryption keys storage database.
|
Note
For versions of Sitecore up to Sitecore 9.0 inclusively, the default storage location for the encryption keys is the See the How to validate the encryption key has switched to the core database mode after an upgrade of Coveo for Sitecore Coveo community article for more details on encryption key storage option configurations.
This article also contains handy SQL queries to validate whether a database contains the encryption key and to copy the encryption key between For Sitecore 9.1+ instances which store the encryption key in the |
|
|
Step 3: Copying the Configuration Files
Since the index is shared between all the Sitecore instances, you need to configure all the additional Sitecore instances (CMs and CDs) to use the same base configuration as the CM1
Sitecore instance:
-
Delete the
Coveo
configuration files folder(s) in each additional Sitecore instance.Sitecore 8
In each additional Sitecore instance, delete the
Coveo
folder located in the<SITECORE_INSTANCE_ROOT>\Website\App_Config\Include\
folder.Sitecore 9 and 10
In each additional Sitecore instance, delete the
Coveo
folders located in the<SITECORE_INSTANCE_ROOT>\App_Config\Include\
and<SITECORE_INSTANCE_ROOT>\App_Config\Modules\
folders. -
Copy the configuration files folder(s) of the
CM1
instance to each additional Sitecore instance.Sitecore 8
Copy the
Coveo
folder located in the<SITECORE_INSTANCE_ROOT>\Website\App_Config\Include\
folder of yourCM1
instance. Paste it into your<SITECORE_INSTANCE_ROOT>\Website\App_Config\Include\
folder of your other instances.Sitecore 9 and 10
Copy the
Coveo
base configuration files folder located in the<SITECORE_INSTANCE_ROOT>\App_Config\Modules\
folder of yourCM1
instance. Paste it into the<SITECORE_INSTANCE_ROOT>\App_Config\Modules\
folder of your other instances.Sitecore 9 and 10
Copy the
Coveo
custom configuration files folder located in the<SITECORE_INSTANCE_ROOT>\App_Config\Include\
folder of yourCM1
instance. Paste it into the<SITECORE_INSTANCE_ROOT>\App_Config\Include\
folder of your other instances.
What’s Next?
Deploy Coveo for Sitecore on your content delivery servers (see Deploy Coveo for Sitecore on the Content Delivery Servers).