Wednesday, April 27, 2016

How to Migrate Endeca Application between environment for forge-based Indexing?

As part of the development/debugging phase, Endeca Application needs to be migrated from QA to UAT or Production to Staging. Following it... thumbnail 1 summary
As part of the development/debugging phase, Endeca Application needs to be migrated from QA to UAT or Production to Staging.

Following items need to be migrated between environments. Find out the description below for each item.

  • Workbench content - Business creates content using Endeca Experience manager and gets stored in IFCR(InFront Configuration Repository)
  • State File - State file contains Endeca auto generated dimension values and FCM generated dimension value. Endeca N-value can be different if state files do not get copied to the environment.
  • Endeca Pipeline -  This Folder contains Endeca Application indexing configuration XML including properties, dimensions, search etc.
  • Cartridge Templates -  This folder contains all cartridge templates that is used to create content in Experience Manager.
  • Editors Config - This Folder contains configuration file to make a call to MDEX to show appropriate data in Experience manager cartridges.
  • Record Store Record store contains all indexable records(Product catalog, content, record store etc.) and dimension information.

Endeca Dimension Cartridge Editors
Cartridge Editors


As part of the migration process, the application needs to be exported first and the same set of files can be used to import into another environment.

Export Endeca Application steps 

1. Record Store - Click here to get more details. This Step can be optional if baseline triggers using /atg/commerce/endeca/index/ProductCatalogSimpleIndexingAdmin Component

2. State files - Copy <<Endeca_App>>/data/state folder.


3. Endeca Pipeline - Copy <<Endeca_App>>/config/pipeline folder

4. Cartridge Templates - Copy <<Endeca_App>>/config/cartridge_templates folder.

5. Editors Config - Copy <<Endeca_App>>/config/editors_config folder

6. Workbench ContentNavigate To Endeca Application control folder and run following commands to get export 
       <<Endeca_App>>/control->export_site.[bat|sh]
      This would generate the XML file and take the backup
Endeca Export Site



Import Endeca Application steps - Steps should be in the following order.

1. Record Store Click here to get more details. This Step can be optional if baseline triggers using /atg/commerce/endeca/index/ProductCatalogSimpleIndexingAdmin Component.

2. State files - Take the backup of <<Endeca_App>>/data/state folder and move state files copied from step-2  during export.

3. Endeca Pipeline - Take the backup of <<Endeca_App>>/config/pipeline folder and move pipeline files copied from step-3  during export.

4. Cartridge Templates - Copy cartridge_templates  from step 4 and run the following command to apply to Workbench. 
        <<Endeca_App>>/control -> set_templates.[bat|sh]
Endeca Set Template command

5. Editors Config - Copy editors_config from step 5 and change host and post information based on environment under each json file and run the following command
         <<Endeca_App>>/control -> set_editors_config.[bat|sh]

6. Endeca Baseline Update-  Run below Command

      <<Endeca_App>>/control -> ./baseline_update.[bat|sh]

7. Workbench Content - Import generated XML from Step-6 (Import site) to the Workbench content u. Run the following command to  import XM content
        <<Endeca_App>>/control -> ./import_site.[bat|sh]<<File_Name>>

Endeca Import Site command


8. Promote Content - Run the following command to promote content from Authoring to Live. Promote content can be run the Workbench as well.
       <<Endeca_App>>/control -> ./promote_content.[bat|sh]

Endeca Promote Content


From Author

Was this post resolve the solution you are looking for? are you looking for some other issues?Provide your comments

No comments

Post a Comment

Text Widget