Wednesday, April 27, 2016

As part of the development/debugging phase, Endeca Application needs to be migrated from QA to UAT or Production to Staging. Following it...11:59:00 PM

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.

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.

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 steps1. Record Store -Click here to get more details. This Step can be optional if baseline triggers using /atg/commerce/endeca/index/ProductCatalogSimpleIndexingAdmin Component2. State files - Copy <<Endeca_App>>/data/state folder.

6. Workbench Content - Navigate 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

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]

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