Configuring Search.config for Search Suggest


The Search.config file acts as a hub for all InSite Search configurations, including Search Suggest.

This file defines the location of main content index files, which outputs to a single location on disk. Ingeniux Search Suggest queries the main content index.

Note
If you upgraded your site to CMS 10.x and need to re-establish ISS, see Implementing InSite Search After Site Upgrade for details about upgrading Search.config.
To configure Search.config for the main content index:
  1. Open your DSS solution in Visual Studio.
  2. Right-click the solution file (i.e., the top node) in the Solution Explorer view, and select Rebuild
  3. Navigate to [Drive]:\[path-to-DSS-root-folder], and open Search.config in a text editor. The example below displays generic code contained within Search.config.
  4. On the <Search> element, complete the following steps.
    1. Ensure the @indexLocation attribute value points to the luceneIndex folder, which stores your main content index.
    2. Set the @indexingEnabled attribute value to true.
    Your code should look similar to the following example:
    Lucene index location example
    <Search indexLocation="App_Data\luceneindex" indexingEnabled="true">
  5. If an <add> element doesn't already exist for published CMS content within the <IndexingSources> element, create one. Complete the following steps in the <add> element:
    1. Enter an arbitrary, unique name as the value of the @name attribute for identification purposes.
    2. Enter Ingeniux.Runtime.Search.DssContentSearchSource as the @type attribute value.
      Note
      Queries that run against this library type require that the content published from an Ingeniux CMS be used by an Ingeniux DSS.
    3. Enter an absolute path to SearchSource.config as the @settingsFile attribute value.
      Important
      Verify the validity of the DSS directory filepath to SearchSource.config. A basic SearchSource.config file resides in [Drive]:\[path-to-DSS-root-folder]\[directory-containing-published-content]\settings. This file generates on publish of CMS content to the publishing content's settings folder (e.g., [Drive]:\[path-to-cms-site-instance]\site\App_Data\pub\[publishing-target-name]\settings\SearchSource.config).

    Your code should look similar to the following example:

    SearchSource.config location example
    <add name="CMSPublishedContent" type="Ingeniux.Runtime.Search.DssContentSearchSource"
       settingsFile="C:\igxdss\dss-published-content\settings\SearchSource.config"/>
  6. If an <add> element doesn't already exist for search suggest within the <IndexingSources> element, create one. Complete the following steps in the <add>element:
    1. Enter an arbitrary, unique name as the value of the @name attribute for identification purposes.
    2. Enter Ingeniux.Search.SpellCheckerSearchDocumentSource as the value of the @type attribute.
    3. Enter the filepath to SpellcheckerSource.config for the value of the @settingsFile attribute.
      Note
      You can use a relative path to the default Suggest Search configuration file (i.e., App_Data\SpellcheckerSource.config), which is included during installation.
    For example, your search suggest <add> element and attributes should look similar to the following code:
    spellcheckerSource.config location example
    <add name="SpellCheckDictionary" type="Ingeniux.Search.SpellCheckerSearchDocumentSource"
    settingsFile="App_Data\spellcheckerSource.config"/>
  7. Save and close Search.config.

Next Steps: Configure SpellcheckerSource.config for Search Suggest.