Installing Coveo for Sitecore 4.0
We recommend that you upgrade at least to the March 2016 (3.0.1266) release of Coveo for Sitecore 3.0 before migrating to the April 2016 (4.0.171) release of Coveo for Sitecore 4.0.
The Leading Practices When Upgrading Coveo for Sitecore also apply to a migration to Coveo for Sitecore 4.0.
Upgrade Coveo Services
If you upgrade to Coveo for Sitecore On-Premises, you will need to upgrade Coveo Enterprise Search (CES) and the Coveo Search API.
First upgrade your Coveo for Sitecore 3.0 to the version that uses the same CES and Search API version as the Coveo for Sitecore 4.0 release that you plan to install.
Upgrade Coveo Enterprise Search (CES). For more details, see Upgrading CES.
Upgrade Coveo Search API. Follow the normal steps of the installation wizard.
Prepare Your Sitecore Instance
Disable all the Coveo for Sitecore configuration files.
.disabledat the end of the following
Sitecore 7.5 In the
.disabledat the end of the
Sitecore 7.5 In the
.disabledat the end of the
If you use Coveo for Sitecore 7.2, or if your Coveo indexes replace Lucene indexes, re-enable Lucene. Go to the
App_Config/Includefolder, and remove
Don’t remove the
Upgrade Coveo for Sitecore
If you’re using the Coveo Admin Service in secure mode, please read this notice before installing the package.
Coveo.SearchProvider.config file, make sure that the
adminServiceUri value uses the same host name as the one specified in the certificate. If you’re using a different host name, such as
localhost, you might get the error below when installing the package.
The remote certificate is invalid according to the validation procedure. ... [WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.] ... [SecurityNegotiationException: Could not establish trust relationship for the SSL/TLS secure channel with authority 'localhost'.]
Log into the Sitecore Desktop.
Access the Installation Wizard (Sitecore Start Menu > Development Tools > Installation Wizard).
Upload and install the
Coveo for Sitecore XX 4.0 (YYY).zippackage.
When prompted to overwrite files, click Yes to all.
When prompted to overwrite items, select Overwrite, then click Apply to all.
You might be prompted twice with this question. Select the Overwrite option and click Apply to all both times.
You may get the following message. Select Continue Always.
Role 'sitecore\Coveo Admin' won't be installed since it already exists.
Follow the instructions of the Post Installation Wizard. This will configure certain mandatory settings in the configuration files. For more information, see Installing Coveo for Sitecore.
Once the installation is completed, make sure that you restart both the Sitecore client and server.
Rebuild Your Indexes
Once your client and server are up and running, you should rebuild your indexes (see Coveo for Sitecore Indexing Guide).
Failure to do so will result in the duplication of your index items.
Change the Encryption Key Name
In Coveo for Sitecore 3.0, the name of the encryption key was
RijndaelEncryptionKey. However, in Coveo for Sitecore 4.0, it’s
To ensure that your encryption key remains valid, rename your encryption key to
IndexingEncryptionKey. It’s usually located under
Configure Your Sources
The Coveo for Sitecore Cloud edition doesn’t use CES anymore, instead relying on the Coveo Platform.
If you had indexed non-Sitecore sources in your previous installation, you need to reconfigure them in the Cloud Platform.
For more information on how to do this, see Adding Content to Your Coveo Organization.
Connecting to Cloud
Coveo for Sitecore 4.0 needs to connect to an organization in the Coveo Platform, whether you’re using the Cloud or On-Premises version of Coveo for Sitecore.
In an On-Premises installation, this organization is used to store your CES license. The organization is also used to store your Coveo for Sitecore license. Therefore, it’s important that you allow your instances to communicate with the Cloud Platform. To know which IPs the Coveo Platform uses, see Adding and Managing API Keys.
Because a Coveo for Sitecore Cloud installation doesn’t use CES anymore, many services have been moved to the Coveo Platform, including securities and permissions.
For Cloud editions of Coveo for Sitecore, Top Results has moved to the Cloud Platform as part of the Query Pipeline feature, and has been renamed Featured Results. For more information, see Adding and Managing Query Pipeline Featured Results.
Merging Your Modifications Into the Configuration Files
Since upgrading Coveo for Sitecore updates the Coveo configuration files with the latest fixes and enhancements, you need to manually merge these modifications into your current configuration files. This method allows you to keep your own customization intact, while still benefiting from the latest enhancements brought in the product. You can use a merge tool such as WinMerge to do that.
To see the list of modifications that you should perform, see Upgrading Configuration Files from Coveo for Sitecore 3.0 to Coveo for Sitecore 4.0.