Most Recent

Sunday, April 3, 2016

Endeca Basics : How to Debug Endeca Pipeline Components transformation is working as expected?

A pipeline is composed of a collection of components. Each component performs a specific function during the transformation of  source data ... thumbnail 1 summary
    • A pipeline is composed of a collection of components. Each component performs a specific function during the transformation of  source data into Endeca records. Components are linked together by means of cross-references, giving the pipeline a sequential flow.

    Find out the way below to debug Endeca Pipeline Components transformation working as expected or not.

    1. Set the global log level. Log level can be set in Forge component using -v[f|e|w|i|d] option. Use -vd flag to increase Forge logging visibility as debug mode.

    2. -printRecords flag option to print records as they are produced by each pipeline component.

    3. Use Record Adapter - Insert a Record adapter between the pipeline components that needs to be review and set direction as Output. Make sure the Record source the component whose output needs to be examined. Pipeline stores the data in XML format and can be seen output XML under <<Endeca_App>>/data/processing folder.

    Find out screen shot below 
    Endeca Pipeline Output Record Adpater Debugging

    Sunday, March 20, 2016

    Oracle Endeca - How to create a dimension based on more than one attributes?

    In Endeca, A Dimension can be created using multiple properties. Example: More Ways to Shop dimension should contain 3 different proper... thumbnail 1 summary
    • In Endeca, A Dimension can be created using multiple properties.

    Example: More Ways to Shop dimension should contain 3 different properties sale, online, new so that user should be able to select multiple refinements under one dimension.

    Following are the ways to achieve it :-

    1.  Using Product-sku-output-config.xml : 

    Add outpur-name and use same name for all properties those needs to be combined for one Dimension
         <property name="online" is-dimension="true" type="string" multiselect-type="multi-or" output-name="product.moreWaysToshop"/>
        <property name="sale" is-dimension="true" type="float" multiselect-type="multi-or" output-name="product.moreWaysToshop"/>
        <property name="new " is-dimension="true" type="float" multiselect-type="multi-or" output-name="product.moreWaysToshop"/>



    2. Developer Studio:  

    Map dimension to multiple source properties as per screen shot below: - 

    Oracle Endeca Developer Studio



    3. Index-config.json - 

    This can be used for CAS based indexing where we have multiple source and joined using Endeca CAS system. use following examples to add mapping to index-config.xml and can be found under <<Endeca_App>>/config/mdex folder

     "product.moreWaystoShop" : {
     "sourcePropertyNames" : [ "new" ],
     "isAutogen" : true,
     "jcr:primaryType" : "endeca:dimension"
     },
     "product.moreWaystoShop" : {
     "sourcePropertyNames" : [ "online" ],
     "isAutogen" : true,
     "jcr:primaryType" : "endeca:dimension"
     },
     "product.moreWaystoShop" : {
     "sourcePropertyNames" : [ "sale" ],
     "isAutogen" : true,
     "jcr:primaryType" : "endeca:dimension"
     }


    Output would be looks like below in Endeca jspref   :-

    Multiple properties mapping to Dimension in Enddeca Jsp ref Implementation

    Text Widget