The Search.config file acts as a hub for all InSite Search
configurations, including Keymatch Search.
This file defines the location of main content index files, which outputs to a single
location on disk. Ingeniux Keymatch Search queries the main content index.
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:
Enter an arbitrary, unique name as the @name attribute value
for identification purposes.
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.
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:
If an <add> element doesn't already exist for Keymatch
search within the <IndexingSources> element, create one.
Complete the following steps in the <add>element:
Enter a unique name as the value of the @name
attribute.
Note
This name is for identification and can be arbitrary.
Enter Ingeniux.Search.KeyMatchSearchDocumentSource as
the value of the @type attribute.
Enter the filepath to KeymatchSource.config for the
value of the @settingsFile attribute.
Note
You can use a relative path to the default Keymatch
configuration file (i.e.,
App_Data\KeymatchSource.config), which is included
during installation.
For example, your Keymatch search <add> element and
attributes should look similar to the following code: