Search Server Settings

Search Settings

The search settings control the behavior of searching and browsing in Commerce Manager. The following list describes these settings.

• COMMERCE/SEARCH/indexOptimizationInterval

  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).

• COMMERCE/SEARCH/maxReturnNumber

  The maximum number of matching items to include in search results. The default is 0, which specifies no limit.

• COMMERCE/SEARCH/minimumSimilarity

  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 0 and 1, not inclusive. (1 would mean it must be an exact match and 0 would mean the terms do not match need to match at all.) Default is 0.75.

• COMMERCE/SEARCH/prefixLength

  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 0.

• COMMERCE/SEARCH/minimumResultsThreshold

  Used for the spell checker. Results that are below or equal to this number will trigger a spelling suggestion lookup. Default is 10.

• COMMERCE/SEARCH/maximumResultsThreshold

  Used for the spell checker. Results that are above or equal to this number will trigger a spelling suggestion lookup. Default is 10000.

• COMMERCE/SEARCH/minimumSuggestionsPerWord

  Used for the spell checker. The maximum number of spelling suggestions to return. Default is 3.

• COMMERCE/SEARCH/accuracy

  Sets the accuracy of spelling suggestions. This value works the same as minimumSimilarity. Default is 0.75.

• COMMERCE/SEARCH/boosts

  Optional. Specifies a comma-separated list of field name/value pairs that specify greater importance to values matched in specific fields. For example:

  categoryCode=0.5,productCode=0.5,
  categoryName_en=2.0,description_en=0.2
  

  By default, all search fields are assigned a boost value of 1.0.

• COMMERCE/SEARCH/excludeAttributes

  Optional. Specifies a comma-separated list of attribute keys that should be not be included when searching all fields. For example:

  A00981,A01012
  

  By default, all attributes are included

Configuring Search Settings

The following indexes are used to optimize sorting, searching, and browsing:

• category
• product
• promotion
• cmuser
• sku

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 APPSPECIFIC/RCP/product

note

The context is case-sensitive.

Logging

The web applications use the Log4j logging framework to write logging information. By default, the searchserver web application logs errors and other system messages to standard out. The default logging level is INFO.

You can configure the application’s logging settings in the extensions/search/ext-search-webapp/src/main/filtered-resources/log4j2.xml file.

Solr Logging

Solr, which provides the search server’s search functionality, uses SLF4J (Simple Logging Façade for Java) with Apache Log4j to write its logging information. For more information on Solr, see Search and Indexing with Solr.

To enable Solr message logging, edit the extensions/search/ext-search-webapp/src/main/filtered-resources/log4j2.xml file and set the following property:

<Logger name="org.apache.solr" level="FINEST" additivity="false">
    ${ep.log.to}
</Logger>