APAR status
Closed as program error.
Error description
Currently, in Feature Pack 4, SOLR queries are limited to one facet.
Local fix
Problem summary
USERS AFFECTED: All WC 7.0 Feature Pack 4 users who desire to use multiple facets in a SOLR query PROBLEM ABSTRACT: Add runtime support for search query pre and post expression processor in Feature Pack 4 BUSINESS IMPACT: Minimal, enhancement request for the solr framework RECOMMENDATION:
Problem conclusion
This iFix contains code logic to enable your multi-select facet search runtime customization: - GetData tag is now able to handle multi-value URL parameter. You can now use this feature to pass in several facet name-value pair using the same parameter name in the URL, while being able to re-use the existing expression builder template from your storefront JSP. - Adding expression pre-processor and post-processor support in through the search runtime. This allows you to modify the SolrQuery request object right before sending the SOLR, and performing additional customization around QueryResponse object from SOLR. This is where the multi-select facet customization logic should go. In order to enable this feature, the query section of a search profile in the wc-search.xml file should be updated with the following: <!-- List of search query pre-processors. A query pre-processor can be used to modify the SolrQuery object right before sending to Solr server for processing. All query pre-processor must extend from <code>AbstractSolrSearchQueryPreprocessor</code> class and implements <code>SearchQueryPreprocessor</code> interface in order to allow initialization of the <code>iSelectionCriteria</code> and <code>iSolrQuery</code> object reference. For example: <_config:preprocessor classname="com.ibm.commerce.catalog.facade.server.services.searc h.query.solr.SolrSearchSampleQueryPreprocessor" /> --> <!-- List of search query post-processors. A query post-processor can be used to modify the physical data object, SolrEntityContainerImpl, right after the QueryResponse is returned from the Solr server. All query post-processor must extend from <code>AbstractSolrSearchQueryPostprocessor</code> class and implements <code>SearchQueryPostprocessor</code> interface in order to allow initialization of the <code>iSelectionCriteria</code>, <code>iQueryResponse</code>, and <code>iResponseObject</code> object reference. For example: <_config:postprocessor classname="com.ibm.commerce.catalog.facade.server.services.searc h.query.solr.SolrSearchSampleQueryPostprocessor" /> --> </_config:query> ------------------------------------------------------------- The latest available maintenance information can be obtained from the Recommended Fixes for WebSphere Commerce technote: http://www.ibm.com/support/docview.wss?rs=3046&uid=swg21261296
Temporary fix
Comments
APAR Information
APAR number
IV16059
Reported component name
WC BUS EDITION
Reported component ID
5724I3801
Reported release
600
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function
Submitted date
2012-02-23
Closed date
2012-07-11
Last modified date
2012-11-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WC BUS EDITION
Fixed component ID
5724I3801
Applicable component levels
R600 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYSYL","label":"WebSphere Commerce Enterprise"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
08 November 2012