Full-Text Search Speed Seems Slow - Full-Text Search - English - Foundation 22.1 - OnBase - external

Full-Text Search
Platform
OnBase
Product
Full-Text Search
Release
Foundation 22.1
License

In systems with large amounts of documents indexed and available to search, performance can appear to be slow when searching. There can be a variety of environmental reasons for this and you should first try adjusting settings to optimize the search engine. See Optimizing Full-Text Search.

If the optimizations don't produce the desired results, there are two other settings for the OnBase Application Server than can be set: fullTextAutoStopLimit and fullTextOmitSummary. These settings are available in the appSettings element of the web.config file on the Application Server.

Note:

Both settings reduce the amount and quality of information returned to users in the search results list and should only be used in special cases.

To edit the web.config file of the Application Server:

  1. Open the web.config file in a plain-text editor, such as Notepad.
    Note:

    The *.config file should only be edited in a plain-text editor, such as Notepad, or a utility specifically designed to edit XML files. It should not be edited in a binary editor, such as Microsoft Word. Using a binary editor can introduce invalid characters to the file and make it unreadable by the software.

  2. Locate the key to update under the appSettings element. If the key is not available, add it as a child of the appSettings element. For example:
    <add key="fullTextAutoStopLimit" value=""/>
  3. Change the value of its value attribute to a valid setting:

    Key

    Settings

    fullTextAutoStopLimit

    Enter a whole number that represents the maximum number of results to return before ending the search process. Once this value is reached, the search process ends. The default value is 0, which does not stop the search process.

    Note:

    If this value is set too low, searches may not return relevant results.

    The fullTextAutoStopLimit value is respected even if the MaxResults limit is set to a higher value.

    For example: <add key="fullTextAutoStopLimit" value="200"/>

    fullTextOmitSummary

    Set the value to true to omit summaries with search results, or set the value to false to include summaries. Summaries are included by default and are displayed in the Summary column of the search results list.

    Note:

    Search results without summaries can be difficult for users to navigate and can make it difficult for users to determine which results to view.

    For example: <add key="fullTextOmitSummary" value="false"/>
  4. Save and close the web.config file.
  5. Reset the application pool for the Application Server for the changes to take effect.