The Coveo Configuration files

The Coveo Configuration files

Similar to Sitecore, the Coveo Search Provider is highly configurable and has many different configuration files. This page explains the roles of the different Coveo configuration files.

Locating and Identifying the Configuration Files

Configuration Folders

Sitecore 7.2

The Coveo for Sitecore configuration files are located with the other Sitecore configuration files under <SITECORE_INSTANCE_ROOT>\Website\App_Config\Include. Depending on your Sitecore version, the Coveo configuration is located in one to three folders:

1. \Coveo
2. \ExperienceAnalyticsCoveo
3. \ExperienceProfileCoveo

Sitecore 9.0

The Coveo for Sitecore configuration files are located in Coveo folders with the other Sitecore configuration files. The Coveo folders are located under:

• <SITECORE_INSTANCE_ROOT>\App_Config\Include\
• <SITECORE_INSTANCE_ROOT>\App_Config\Modules\

Coveo Folder(s)

The Coveo folder(s) can be found on all Sitecore versions. The files therein store the configurations of the Coveo Search Provider and of the different search components and the Coveo for Sitecore UI.

In the Coveo folder(s), you can find:

1. Coveo.CloudPlatformClient.config: contains configuration of the module responsible for interacting with the Coveo Platform.
2. Coveo.CloudPlatformClient.Custom.config: contains custom configuration of the module responsible for interacting with the Coveo Platform.
3. Coveo.SearchProvider.config: contains the Coveo indexes definitions and the default configuration of the Coveo Search Provider. No modification should be done to this file (see Understanding the Coveo Search Provider Configuration File).
4. Coveo.SearchProvider.Custom.config: contains the custom configuration of the Coveo Search Provider and pipeline examples. This file is meant to be modified.
5. Coveo for Sitecore 4.1 (September 2018) Coveo.SearchProvider.Fields.Custom.config: contains the list of include fields. This file is automatically generated when using the PATCH or PUT fields services for the first time. No modification should be done to this file directly.
6. Coveo.SearchProvider.Licensing.config: contains the different commands used to open Coveo wizards.
7. Coveo.SearchProvider.Rest.config: contains the configuration of the REST endpoint used to query the Coveo index. It also includes configurations related to search results handling. No modification should be done to this file (see Understanding the REST Endpoint Configuration Files).
8. Coveo.SearchProvider.Rest.Custom.config: contains the custom configuration of the REST endpoint and pipeline examples. This file is meant to be modified.
9. Coveo.UI.Controls.config: this file is responsible for the configuration related to the integration of Coveo JS Framework in the Sitecore page editor.
10. Sitecore 9.0 SwitchMasterToWeb.Coveo.config.example: useful when configuring Sitecore in a CM/CD configuration. Activate only on CD instances.

ExperienceAnalyticsCoveo Folder

This folder contains a single configuration file: Coveo.Analytics.xDB.config, which defines the Coveo components related to Sitecore xDB. It can be found on instances of Sitecore 7.5+.

ExperienceProfileCoveo Folder

This folder also contains a single configuration file:Coveo.ExperienceProfile.config, which defines the Coveo for Sitecore processors to report Coveo-powered search page events to Sitecore xDB. It can be found on instances of Sitecore 7.5+.

Configuration File Types

Most Coveo configuration files are split into two categories:

1. .config files

2. .Custom.config files

The .config files contain the default configurations of Coveo for Sitecore, while the .Custom.config files contain configuration examples and the configurations generated by Coveo UIs (for example, the post installation wizard). Because the Sitecore wizard treats .config files in alphabetical order, the configurations in the .Custom.config files take priority over the .config files. If you need to modify your configurations, you’re therefore encouraged to do so in the .Custom.config files; otherwise, you may encounter unexpected bugs during updates.