Most Recent

Saturday, March 4, 2017

ATG-Endeca Integration : How to Enable/Disable automatic indexing after BCC Post Deployment?

Endeca Indexing jobs getting triggered automatically just after BCC post deployment. IndexingDeploymentListners helps trigger indexing and ... thumbnail 1 summary
    • Endeca Indexing jobs getting triggered automatically just after BCC post deployment. IndexingDeploymentListners helps trigger indexing and part of /atg/epub/DeploymentServer component.

     Enable Automatic Indexing 

     Add IndexingDeploymentListner component to the list of listeners on /atg/epub/DeploymentServer Component. Bydefault,  IndexingDeploymentListner is included.

    Disable Automatic Indexing


    Remove IndexingDeploymentListner component to the list of listeners on /atg/epub/DeploymentServer Component. 



    From Author

    Was this post resolve the solution you are looking for? what do you think about this solution?Provide your comments

    Sunday, April 3, 2016

    Endeca Basics : Partial update Process Limitation

    A partial update modifies only those portions of the MDEX Engine index that have changed since the last baseline update. Partial updates can... thumbnail 1 summary
    • A partial update modifies only those portions of the MDEX Engine index that have changed since the last baseline update. Partial updates can affect any number of records in the system, and the update may be run frequently. A partial update does not require restarting the MDEX Engine.

     Find out the Partial update process limitation below :-


    • Add new dimensions.
    • Add new properties.
    • Add new mid-hierarchy dimension values in hierarchical dimension e.g Product.category.
    • Add, delete, or change any aspect of an existing dimension value. For example, you cannot add,change, or remove dimension value properties.
    • Add dimension value properties to any existing dimension values.
    • Update the index configuration files (such as the thesaurus and stop words files).
    Click here to get more topics related to Endeca basic concepts.

    Endeca Basics : How to troubleshoot partial update is working as expected or not?

    Endeca Partial indexing process uses only Forge process to generate XML file and Dgidx process gets skipped.   The MDEX Engine processes p... thumbnail 1 summary
    • Endeca Partial indexing process uses only Forge process to generate XML file and Dgidx process gets skipped.  

     The MDEX Engine processes partial updates concurrently with processing incoming queries. This function is also known as the continuous query. The partial update does not require restarting of Dgraph servers.
    Find out steps below how partial gets applied to MDEX(Multi Dimensional Index)

     1. Once XML gets generated by Forge process, MDEX engine process updates on Record-by-record basis.

     2. Generated XML from step 1 copied to <<Endeca/App>>/data/dgraphs/DgraphA1/dgraph_input/updates folder.

     3. Update fails or succeeded at the record level.

     4. File gets deleted under <<Endeca/App>>/data/dgraphs/DgraphA1/dgraph_input/updates folder once partial update gets applied to MDEX.

    If there any error occurs during partial update :-

     1. Partial update process continues to apply to MDEX.

     2. A log entry added to Dgraph logs

     3. MDEX engine writes a  file containing the failed updated record and dimension value under <<Endeca/App>>/data/dgraphs/DgraphA1/dgraph_input/updates/failed_update folder

    Click here to get more topics related to Endeca basic concepts.

    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

    Text Widget