Skip to main content

Enabling Inventory index for storefront in Websphere Commerce


By default, Inventory Index is only meant for business users to use in CMC for Product Ranking and merchandising purpose. This document describes how to enable this OOTB SOLR Index for Store Front usage so that it can be used to get SKUs Inventory from SOLR Index instead of DB hits.

The implementation involves two steps:
  1. Enable OOTB Inventory Index
  2. Make it usable by Store Front Pages

Enable Inventory Index


This step is well described at Infocenter at Setting up and building the inventory index



Enable Inventory Index for Store Front pages


This involves following steps

  1. Define a Search resource Handler to accept Inventory fetch requests.
  2. SOLR Index Customization, if required
  3. Define a search Profile to expose Inventory Schema fields to Response
  4. Map SOLR schema fields to External Response fields
  5. Custom Expression Provider to get default fulfillment center Id.
  6. Create a new SOLR Search Post Processor to format the solr fields in Response ready format.

Inventory Search Resource Handler

A new search resource handler needs to be mapped with a unique path using which a REST service can be invoked from Store Front Pages..

Handler: XInventorySearchResourceHandler
Extends: AbstractSearchResourceHandler

Class level path annotation: @Path ("store/{storeId}/inventoryview")
Method level path annotation: @Path ("byCatentryId/{catentryId}")

@GET
@Path("byCatentryId/{catentryId}")
@Produces({MediaType.APPLICATION_JSON, MediaType.APPLICATION_XML })
public Response fetchInventoryStatusByCatalogEntryId(
        @QueryParam("responseFormat") String responseFormat,
        @PathParam("storeId") String storeId,
        @PathParam("catentryId") String catentryId,
        @QueryParam("searchProfile") String searchProfile) {
     
    Response result = null;
    SearchCriteria searchCriteria = null;

    try {
        searchCriteria = prepareSearchCriteria(storeId, null, "inventoryview",
            "store/10501/inventoryview/byCatentryId/{catentryId}", searchProfile);
         
        throwRestExceptionIfErrorsAreDetected();
        searchCriteria.setControlParameterValue(
                "_wcf.search.internal.optional.query",
                "catentry_id:" + catentryId);

        result = performSearch(searchCriteria);
    } catch (Exception e) {
        result = generateResponseFromRespData(searchCriteria, null, e);
    } // EndTryCatch

    LOGGER.debug("Exit");
    return result;

} //EndMethod

Search Profile for Inventory Index


<!-- Search Profile to get Inventory SOLR response for a given catentryId -->
<_config:profile indexName="Inventory" name="X_findInventoryByCatentryId">
    <_config:query>
        <_config:param name="maxRows" value="50" />
        <_config:param name="maxTimeAllowed" value="15000" />
         
        <!--Add Providers -->
         
        <!--Add Post Processors -->
    </_config:query>
    <_config:result>
        <_config:field name="catentry_id"/>
        <_config:field name="inv_strlocqty_*"/>
        <_config:field name="inv_inventoryflag_*"/>
    </_config:result>
</_config:profile>

Comments

Popular posts from this blog

File Upload in Websphere Commerce

Websphere Commerce has a inbuilt mechanism to handle the file upload process but it has some limitations with it. Whenever a File type is present in request object, commerce ignores the rest of parameters coming after that. The inbuilt mechanism treats the file object as UploadedFile type object. This type of object provides a limited number of options to further process the File Objects. To  overcome these limitation, we need to use Apache Common Fileupload features to handle the File Upload process for Hanes. File Upload Basic Requirements In order to pass a File object in request, we need to make some changes in the Form. File Upload is not supported by REST or Ajax REST Requests. Icon Request Parsing The first step is to parse the request for Uploaded File Objects. And apart from this we need to get the other parameters back to request properties, which is not available because of the limitation of commerce. ...

Websphere Commerce Creating a custom SOLR core

This page describes how we can create custom SOLR cores in commerce. Let's think of a e commerce site where we retailers can log in and can register there shops. We want to index Shops so that user can search for different shops. SOLR Core Naming Convention A custom SOLR core has to be named according to OOTB convention  MC_10001_<coreName>_en_US . The core name should be a single word without any underscores in it. An entry in solr.xml will look like as below < core   instanceDir = "MC_10001\en_US\Shops\"   name = "MC_10001_Shops_en_US"   /> Registering custom core with Search server Create a new folder along with the other SOLR cores,  "Shops " at /search/solr/home/MC_10001/en_US/ Shops  should have a " conf " folder for configuration XMLs . Define SQL in /conf/wc-data-config.xml and map the database fields with SOLR fields. Define SOLR fields in schema.xml We need to register our custom SO...