Deploying on Additional Content Managers
If your setup has more than one content manager, 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 at least one content manager for a scaled environment. See Prepare the 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 Downloads).
Coveo for Sitecore XX 4.X (xxxx).zip.
package.zipcompressed folder, copy the content of the
Local Disk\inetpub\wwwroot\<SITECORE_INSTANCE>\Website\on the additional CM.
files folder mimics the folder structure found in the Sitecore website.
Step 2: Ensuring Access to the Encryption Keys
Coveo for Sitecore creates a
Coveo directory in the Sitecore instance
Data directory to store configuration encryption keys
(ConfigurationEncryptionKeys\IndexingEncryptionKeys). These keys must be the same on all the Sitecore instances to be able to decrypt the encrypted configuration elements.
Copy the folder
Coveoto each content delivery server in their
As of December 2016, 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.
For versions of Sitecore up to Sitecore 9.0 inclusively, the default storage location for the encryption keys is the
core database. For Sitecore 9.1 onwards, the default value for this setting is the
If your CMs and CDs are all set up to access the
pubdatabase, ensure that you patch the following settings accordingly:
<Database>element in the
<setting name="Coveo.Framework.DatabasePropertyName"element in the
If your CMs and CDs don’t all share a given database, make sure you have a database replication strategy in place.
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 additional Sitecore instances
CM1instance, copy the
App_Config\Include\Coveofolder from the
CM1Sitecore instance to all the additional Sitecore instances.
Now that you deployed Coveo for Sitecore on your additional Content Managers, you may proceed to deploying the package to your Content Delivery servers (see Deploying Coveo for Sitecore on the Content Delivery Servers).