Disabling search expression providers and result filters in the search configuration file (wc-search.xml)

You can disable certain expression providers and result filters in the HCL Commerce search configuration file (wc-search.xml). Doing so optimizes the storefront flow and improves the overall response time for certain types of HCL Commerce Search scenarios.

Procedure

  • Disabling configurations:

    You can disable some configurations, for example, expression providers, preprocessors, postprocessors, and result filters from the HCL Commerce Search configuration file (wc-search.xml) on the Transaction server and Search server.

    This might be helpful when you use a customized version of the wc-search.xml file in the -ext customization directory.

    For example, the following snippet disables a query postprocessor called SolrSearchSampleQueryPostprocessor:
    
<_config:postprocessor
  classname="com.ibm.commerce.catalog.facade.server.services.search.query.solr.SolrSearchSampleQueryPostprocessor"
  enabled="false" />
  • Consider disabling the following expression providers from the HCL Commerce Search configuration file (wc-search.xml):
    SolrSearchProductEntitlementExpressionProvider
    This search expression provider performs product entitlement. It is performed by calling ProductEntitlementExpressionHelper to build search engine-specific query expressions for contracts that contain CatalogFilter Term Conditions and ProductSet Term Conditions.

    You can disable this expression provider from your search profile if your site does not contain customer-specific entitlement.

    SolrSearchInventoryExpressionProvider
    This search expression provider handles search requests to work with the Inventory index.

    You can disable this expression provider from your search profile if your site does not use the Inventory extension index.