Endeca XM content promoted using the file-based method - Oracle Commerce v11.x

How to promote Endeca XM content using the file-based method?
 

Here are the steps:

     1) Update all store instances with correct shared location path

     Ex:

/dyn/admin/nucleus//atg/endeca/assembler/cartridge/manager/DefaultFileStoreFactory/

configurationPath=/opt/app/endeca/apps/CRS/data/workbench/application_export_archive/CRS

    2) Update LiveAppServerCluster.xml with all store instance details (refer DEV)

/opt/app/endeca/apps/CRS/config/script/LiveAppServerCluster.xml

    3) Update Workbench config file  as below:

/opt/app/endeca/apps/CRS/config/script/WorkbenchConfig.xml

  <![CDATA[

          IFCR.exportConfigSnapshot(LiveDgraphCluster);

         IFCR.exportApplication();

          LiveDgraphCluster.applyConfigSnapshot();

          AssemblerUpdate.updateAssemblers();

       //  IFCR.promoteFromAuthoringToLive();

          ]]>

applicationExportDir" value="/opt/app/endeca/apps/CRS/data/workbench/application_export_archive"

4) On the machine where the Oracle Commerce Platform is installed, mount the shared application_export_archive directory.

application_export_archive directory is used to store a ZIP file that contains content that is created by Experience Manager and then accessed by the Assembler. 
 

5)  Run Baseline update
/opt/app/endeca/apps/CRS/control:/>./baseline_update.sh

[04.01.16 17:44:41] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[04.01.16 17:44:43] INFO: Definition has not changed.
[04.01.16 17:44:43] INFO: Exporting MDEX tool contents to file CRS.mdex.2016-04-01_17-44-43.zip
[04.01.16 17:44:44] INFO: Exporting resource 'http://localhost:8006/ifcr/sites/CRS' to '/opt/app/endeca/apps/CRS/data/workbench/application_export_archive/CRS/CRS2016-04-01_17-44-44.zip'
[04.01.16 17:44:45] INFO: Finished exporting resource.
[04.01.16 17:44:45] INFO: Job #: update-dgraph-1459550685260 Sending update to server  - file: /tmp/soap-mdex2489908051012056922.xml
[04.01.16 17:44:45] INFO: The request to the Dgraph at localhost:15000 was successfully sent. The return code was : 200
[04.01.16 17:44:45] INFO: Job #: update-dgraph-1459550685260 Sending update to server  - file: /tmp/soap-mdex2489908051012056922.xml
[04.01.16 17:44:45] INFO: The request to the Dgraph at localhost:15000 was successfully sent. The return code was : 200
[04.01.16 17:44:45] INFO: Job #: update-dgraph-1459550685260 Sending update to server  - file: /tmp/soap-mdex2489908051012056922.xml
[04.01.16 17:44:46] INFO: The request to the Dgraph at localhost:15002 was successfully sent. The return code was : 200
[04.01.16 17:44:46] INFO: Begin updating Assemblers.
[04.01.16 17:44:46] INFO: Calling Assemblers to update contents.
[04.01.16 17:44:46] INFO: Updated Assembler at URL: localhost:8080/dyn/admin/assemblerAdmin/admin
[04.01.16 17:44:46] INFO: Finished updating Assemblers. Updating reference file.

ATG Pipeline - How to bypass AssemblerPipelineServlet request for specific web application (Ex: BCC, CSC etc..)? - ATG Endeca Integration

A web application must explicitly set the atg.assembler context parameter to true in its web.xml file, otherwise the AssemblerPipelineServlet will pass the request. 

atg.assembler context parameter indicates that we want to execute the AssemblerPiplineServlet which will use the assembler api to return content from Experience Manager or Guided Search.

To set the atg.assembler context parameter to true, add the following to the application’s web.xml file:

 
Applications that never have a need to invoke the Assembler, should set atg.assembler to false to bypass the servlet and avoid making requests to the Assembler.

ATG Endeca - How to find the Endeca Indexing History?

Oracle commerce v11.x has a new feature which will keep track of Endeca indexing history.

Use below component to check the Index History:

/dyn/admin/nucleus/atg/commerce/endeca/index/ProductCatalogSimpleIndexingAdmin/?histIdx=0