Updating Coveo for Sitecore Settings

The Coveo Cloud Manager allows you to modify your Coveo Cloud organization settings. Typically, you’ll use this feature either to change the Coveo Cloud organization your Sitecore instance is linked to or to modify indexing settings.

Accessing the Coveo Cloud Manager

To access the Coveo Cloud Manager as a Sitecore administrator

  1. Open the Coveo Search section of the Sitecore Control Panel (see Opening the Coveo Search Control Panel Section).

  2. Choose Coveo Cloud Manager.

    You can also access the Coveo Cloud Manager section of the Command Center using URL http://[INSTANCE NAME]/coveo/command-center/index.html#configuration, where [INSTANCE NAME] is the name of your Sitecore instance. Non Sitecore administrators can only access the Command Center by URL (see Giving Access to the Command Center).

Changing Your Coveo Cloud Organization

To change your Coveo Cloud organization

  1. Click Log In.

    Command Center Activation

  2. Follow the instructions shown on screen to log in to the Coveo Cloud Platform using your preferred identity provider.

  3. Select or create your Coveo Cloud organization.
    • To select an existing organization, in the Change your organization section, under the Existing tab, select the appropriate organization name from the drop-down menu.
    • To create a new organization
      1. In the Change your organization section, select the Create New tab.
      2. Type the name you want in the Organization name field.

        While you can always change your organization display name later in the Coveo Cloud Administration Console under Settings > Organization > Profile, be aware that the original name value you specify when creating an organization will forever be part of the unique and permanent ID of that organization.

  4. Select the Trial type that matches your needs (see Entitlement Comparison (Coveo for Sitecore)).

  5. By default, your Configure options section settings are carried over from your previous Coveo Cloud organization to the current one.

    • If you need to change these settings as well, proceed to Modifying Your Indexing Settings.
    • If you want to keep the settings in the Configure options section such as they are, click Apply and Restart.
  • Allow 15 to 30 minutes for a new Coveo Cloud organization to be provisioned.
  • When a Coveo Cloud trial organization has been idle for some time, it’s paused automatically. If you have selected an existing organization that has been idle for a while, one of the following dialogs is displayed when you reload the page:

    If you click Resume, the organization status then changes to Resuming.

    The dialog automatically closes once the organization has finished resuming and is, once again, fully functional.

    You can also resume your cloud organization through the Coveo Cloud Administration Console, in the main menu, in the Status section.

Modifying Your Indexing Settings

To modify your indexing settings

  1. In the Configure options section, specify your new settings.

    Further details for each option are provided below.

    • Body indexing: Allows you to select whether the rendered HTML should be indexed.
    • Farm configuration: Allows you to specify a Farm name in order to refer to resources such as sources and security identity providers with coherent names.

      Changing the Farm name in the Command Center updates the <farmName> element text content in Coveo.SearchProvider.Custom.config. Similarly, when you change the text content of the <farmName> element in Coveo.SearchProvider.Custom.config, the Command Center reflects this change as soon as you refresh the page.

      However, if you overwrite the Farm name value using a patch file of your own, the Command Center will detect a difference between the Coveo.SearchProvider.Custom.config Farm name and the one in the Sitecore compiled configuration. When both values are different, the Command Center disables Farm name editing.

  2. Click Apply and Restart.

Since Coveo for Sitecore configuration files are updated, the Sitecore instance must be restarted.

Recommended Articles