The search settings control the behavior of searching and browsing in Commerce Manager. The following list describes these settings.
Specifies how often the index is optimized.
Optimization is generally only needed when the index has had a large number of updates (adds/deletes), so if the index is updated frequently, you may want to specify a higher frequency. For more information, see Scheduled Jobs (Search Server).
The maximum number of matching items to include in search results. The default is
0, which specifies no limit.
Used for fuzzy searching. This specifies how similar the matching terms must be to the query term.
It must be set to a value between
1, not inclusive. (
1would mean it must be an exact match and
0would mean the terms do not match need to match at all.) Default is
Used for fuzzy searching. Specifies the number of characters at the start of the search term that must be the same in potential matches. Default is
Used for the spell checker. Results that are below or equal to this number will trigger a spelling suggestion lookup. Default is
Used for the spell checker. Results that are above or equal to this number will trigger a spelling suggestion lookup. Default is
Used for the spell checker. The maximum number of spelling suggestions to return. Default is
Sets the accuracy of spelling suggestions. This value works the same as
minimumSimilarity. Default is
Optional. Specifies a comma-separated list of field name/value pairs that specify greater importance to values matched in specific fields. For example:
By default, all search fields are assigned a boost value of
Optional. Specifies a comma-separated list of attribute keys that should be not be included when searching all fields. For example:
By default, all attributes are included
Configuring Search Settings
The following indexes are used to optimize sorting, searching, and browsing:
Search settings can have different values for each of these indexes, depending on the application (Commerce Manager or web services). Search settings also affect search behavior at the store level, so they can have a different value for each combination of index and store. As such, the context of a search setting value must specify the index to which it applies, and either the application or the store.
For example, the
COMMERCE/SEARCH/maxReturnNumber setting lets you configure the maximum number of search results to return. To set the maximum number of results when searching for products (the Product index) in the Commerce Manager, identified by RCP (Rich Client Platform), the context must be set to
The context is case-sensitive.
The web applications use the Log4J logging framework to write logging information. By default, the
searchserver web application logs errors and other system messages in
<Your Server>\webapp\WEB-INF\log\elasticpath.log. The default logging level is
You can configure the application’s logging settings in the
Solr, which provides the search server’s search functionality, uses Log4J to write its logging information. For more information on Solr, see Search and Indexing with Solr.
To enable Solr message logging, edit the
log4j.properties file and set the following property: