Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Developing
The topics in the Developing section describe tasks performed by an application developer.
WebSphere Commerce search
WebSphere Commerce search provides enhanced search functionality in starter stores by enabling enriched search engine capabilities such as automatic search term suggestions and spelling correction, while influencing store search results by using search term associations, and search-based merchandising rules.
Programming model, extension points, and customization tasks
This guide outlines the WebSphere Commerce search programming model, extension points, and how it can be customized. There are mandatory and optional areas to work with, depending on the customization that is being performed to your WebSphere Commerce search implementation.
.... in Feature Pack 7 or later
The following guide outlines the WebSphere Commerce search programming model, extension points, and how it can be customized. There are mandatory and optional areas to work with, depending on the customization that is being performed to your WebSphere Commerce search implementation.
Customizing the search run time
You can customize several areas of the search run time.
Adding native Solr query parameters to search expressions
You can add native Solr query parameters to each search profile's query parameter section to enhance and customize the final Solr query.

Adding native Solr query parameters to search expressions

You can add native Solr query parameters to each search profile's query parameter section to enhance and customize the final Solr query.

This param configuration can be used to declare properties that influence how the query expression gets run against the Solr server at runtime. The given name value-pair parameters will be directly added into the final SolrQuery object using the setParam(name, value) method.

Note: This feature requires the REST search API. It will not work with searches that use the BOD API. For more information about the differences between REST and BOD APIs in Feature Pack 7, see Websphere Commerce search interface.

For example:


<_config:query>
   <_config:param name="debug" value="results" />
   <_config:param name="spellcheck.collate" value="false" />