IBM Support

JR54722: Rule-Based Sales Category maxRows setting not respected in Solr query results

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When 'applying a rule' to a Rule-Based Sales Category, it will
    associate a maximum of 500 products to the category.
    
    Some data is missing.   <Argument name="specifyMaximum"
    value="MARKETING_specifyMaximum"/>
    
    1) Update the DMELETEMPLATE table:
    
    update dmeletemplate set implxml='<FlowElementImplementation
    type="DisplayProductStandardSearchCombined"><Implementation
    invocationType="TaskCommand"><Class
    name="com.ibm.commerce.marketing.commands.elements.DisplayProduc
    tBySearchActionAdvancedTaskCmd"><Argument
    name="useUserSearchTerm"
    value="MARKETING_useUserSearchTerm"/><Argument
    name="searchTermList"
    value="MARKETING_searchTermList"/><Argument
    name="searchParameter" value="searchTerm"/><Argument
    name="displayMax" value="MARKETING_displayMax"/><Argument
    name="filterName" value="MARKETING_filterName"/><Argument
    name="filterOperator"
    value="MARKETING_filterOperator"/><Argument name="filterValue"
    value="MARKETING_filterValue"/><Argument name="filterValue2"
    value="MARKETING_filterValue2"/><Argument name="filterWeight"
    value="MARKETING_filterWeight"/><Argument name="orderByField"
    value="MARKETING_orderByField"/><Argument name="orderBySequence"
     value="MARKETING_orderBySequence"/><Argument name="filterType"
    value="MARKETING_filterType"/><Argument
    name="recommendationMethod"
    value="MARKETING_recommendationMethod"/><Argument
    name="includeCategories"
    value="MARKETING_includeCategories"/><Argument
    name="specifyMaximum"
    value="MARKETING_specifyMaximum"/><Argument name="includeFacets"
     value="MARKETING_includeFacets"/><Argument name="filterCode"
    value="MARKETING_filterCode"/><Argument name="filterDataType"
    value="MARKETING_filterDataType"/><Argument
    name="orderByFieldCode"
    value="MARKETING_orderByFieldCode"/><Argument
    name="orderByFieldType"
    value="MARKETING_orderByFieldType"/><Argument
    name="facetExclusionField"
    value="MARKETING_facetExclusionField"/><Argument
    name="facetExclusionFieldCode"
    value="MARKETING_facetExclusionFieldCode"/><Argument
    name="facetExclusionFieldType"
    value="MARKETING_facetExclusionFieldType"/></Class></Implementat
    ion></FlowElementImplementation>' where dmeletemplate_id=343;
    
    2)  Restart the WC server.
    
    3)  Behaviour explanation:
    
         Finding sample catalog entries:  The sample results,
    displayed in the utility pane of Management Center, are
    unbounded and are paged.
    
         Saving / Re-applying the rule:
         If no maximum is specified, we do not allow a potentially
    unbounded set of search query results.  A maximum of 500 catalog
     entries (not including product-level SKUs) will be allowed for
    the category.
         If the business user wants to override this value, they can
     use the management center to override this value:
    
    
    
    
    To prevent the business user from assigning an overly large
    number, an IT configured limit can be set.  This is the setting
    in the wc-search.xml.
    
    
    http://www-01.ibm.com/support/knowledgecenter/SSZLC2_7.0.0/com.i
    bm.commerce.admin.doc/tasks/tpnrulebasedsalescatadconfig.htm?lan
    g=en
    <_config:profile indexName="CatalogEntry"
    name="IBM_salesCatalogDynamicCatalogEntryRecommendation">
            <_config:query>
    		<_config:param name="maxRows" value="500"/>
                <_config:param name="maxTimeAllowed" value="15000"/>
                <_config:provider
    classname="com.ibm.commerce.catalog.facade.server.services.searc
    h.expression.solr.SolrSearchBasedMerchandisingExpressionProvider
    "/>
                <_config:provider
    classname="com.ibm.commerce.catalog.facade.server.services.searc
    h.expression.solr.SolrSearchTermAssociationExpressionProvider"/>
                <_config:provider
    classname="com.ibm.commerce.catalog.facade.server.services.searc
    h.expression.solr.SolrSearchByKeywordRelevancyExpressionProvider
    "/>
                <_config:provider
    classname="com.ibm.commerce.catalog.facade.server.services.searc
    h.expression.solr.SolrSearchByMasterCatalogExpressionProvider"/>
                <_config:provider
    classname="com.ibm.commerce.catalog.facade.server.services.searc
    h.expression.solr.SolrSearchByManufacturerExpressionProvider"/>
                <_config:provider
    classname="com.ibm.commerce.catalog.facade.server.services.searc
    h.expression.solr.SolrSearchByPriceExpressionProvider"/>
                <_config:provider
    classname="com.ibm.commerce.catalog.facade.server.services.searc
    h.expression.solr.SolrSearchByStorePathExpressionProvider"/>
                <_config:provider
    classname="com.ibm.commerce.catalog.facade.server.services.searc
    h.expression.solr.SolrSearchByPublishedEntryOnlyExpressionProvid
    er"/>
                <_config:provider
    classname="com.ibm.commerce.catalog.facade.server.services.searc
    h.expression.solr.SolrSearchTypeExpressionProvider"/>
                <_config:provider
    classname="com.ibm.commerce.catalog.facade.server.services.searc
    h.expression.solr.SolrSearchInventoryExpressionProvider"/>
                <_config:field name="name"/>
    		<_config:field name="defaultSearch"/>
    		<_config:field name="categoryname"/>
               <_config:field name="shortDescription"/>
            </_config:query>
            <_config:result>
                <_config:field name="catentry_id"/>
            </_config:result>
        </_config:profile>
    

Local fix

Problem summary

  • USERS AFFECTED:
    Websphere Commerce V7 FEP8 and V8 users.
    
    PROBLEM ABSTRACT:
    Rule-Based Sales Category maxRows setting not respected in Solr
    query results
    
    BUSINESS IMPACT:
    The business user will not be able to specify a maximum of more
    than 500 catalog entries belonging to a rule-based sales
    category.
    
    RECOMMENDATION:
    

Problem conclusion

  • See the problem description for the data required to fix the
    issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR54722

  • Reported component name

    WC BUS EDITION

  • Reported component ID

    5724I3800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-11-12

  • Closed date

    2016-01-18

  • Last modified date

    2016-01-25

  • 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

    5724I3800

Applicable component levels

  • R700 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":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
25 January 2016