Creating and Using an EPiServer CMS Configuration File

You can optionally create and use a configuration file with an EPiServer CMS source. The purpose of the configuration file is to specify fields that are links to downloadable documents that you want to index. Without a configuration file, the connector crawls the content of the pages but not the content of downloadable documents linked from the pages.

Note: An alternative to using a configuration file to crawl downloadable documents is to crawl the EPiServer CMS File Manager content (see Configuring the EPiServer CMS Source to Crawl the File Manager).

To create and use an EPiServer CMS configuration file

1. Using an administrator account, connect to the Coveo Master server.

2. Using a text editor:

   1. Create an XML file respecting the format illustrated in the following commented example.

      <episerverdocumentconfig>
        <!-- This is the type of item. For now, this config only applies for type "page" -->
        <page>
          <!-- This is the type of pages, as defined within EPiServer -->
          <pagetype>
            <!-- The value of pagetype -->
            <string>[AlloyTech] Document</string>
          </pagetype>
          <fieldstodownload>
            <!-- this is the list of fields that the connector attempts to download as documents. -->
            <fieldnames>
              <!-- This is the value of the metadata contained in the page that allows to retrieve the document. -->
              <!-- Generally this takes the form of a virtual path in the file manager. -->
              <string>DocumentInternalPath</string>
            </fieldnames>
          </fieldstodownload>
        </page>
      </episerverdocumentconfig>  

   2. Save the file using a name of your choice in the [Index_Path]\Config folder.

      Example: C:\CES7\Config\MyEPiServerCMSConfig.xml

3. To instruct the source to use this configuration file, add the ConfigFile hidden parameter to the EPiServer CMS source and use the filename and path where you saved the file as the value for the parameter (see Modifying Hidden EPiServer CMS Source Parameters).