Product DocsMenu

Sitecore Legacy Connector Deployment Overview

Deprecated

The following procedure outlines the steps required to bring content into the Coveo unified index using the Sitecore connector. The steps indicate the order in which you must perform configuration tasks.

Note: It is strongly recommended to rather use the Sitecore 2nd generation connector or Coveo for Sitecore based on your Sitecore version (see Coveo for Sitecore and Sitecore Connector).

To deploy the Sitecore connector

  1. Validate that your environment meets the requirements (see Sitecore Legacy Connector Requirements).

  2. On the Sitecore server, install the Coveo Web Service for Sitecore that allows the connector to retrieve information from Sitecore (see Installing the Coveo Legacy Web Service Plugin for Sitecore).

  3. On the Coveo server:

    1. Configure the user identity

      The connector needs to know the account to use to crawl the Sitecore content. By default, the connector uses the extranet\Anonymous account to retrieve content from Sitecore. Depending on the security configuration, this account might not have access to all Sitecore items.

      It is recommended to configure a CES user identity to use a dedicated Sitecore account that has the Read permission to all the Sitecore content. This account does not need to be a Sitecore administrator. It is also recommended, but not mandatory, to specify a user part of the same domain as the crawled source (see Adding a User Identity).

    2. Optionally configure a security provider

      When you want to index security permissions and use the search interface integration within a Sitecore website you need to create a Sitecore security provider (see Configuring a Sitecore Security Provider for the Legacy Connector).

    3. Configure and index the Sitecore source

      A Sitecore source only targets one Sitecore website, therefore it is recommended to create one source for each Sitecore website to index (see Configuring and Indexing a Sitecore Source for the Legacy Connector).

    4. Optionally modify hidden source parameters

      Once your Sitecore connector source is up and running, when you encounter specific issues or you want to achieve specific crawling behavior, consider modifying some hidden source parameters to resolve the issues (see Modifying Hidden Sitecore Source Parameters for the Legacy Connector).

    5. Optionally create a mapping file

      When you want to modify how referenced Sitecore field values are resolved, create a mapping file to specify how to map Sitecore metadata to CES fields (see Defining a Sitecore Mapping File for the Legacy Connector and About Sitecore Metadata with the Legacy Connector).

  4. Optionally enable incremental refresh

    When you want to maintain the indexed Sitecore content up-to-date between index refreshes, while the Sitecore connector supports incremental refreshes, you must configure the Sitecore database to allow incremental refresh (see Enabling Incremental Refresh on a Sitecore Database for the Legacy Connector).

  5. Optionally integrate the Coveo search interfaces in a Sitecore website:

    When Coveo search interfaces are integrated in a Sitecore website, end-users can use all Coveo search functionalities directly in the website (see Integrating the Coveo .NET Search Interface in a Sitecore Website).

People who viewed this topic also viewed