This diagram / mind map was created using MindJet application and covers the steps/guidelines on exactly what it takes to promote the Content & Search configuration from Staging to Production environment.

1. Promoting Content -
Endeca
Lifecycle
Authoring
Previewing
Live
What is promoted
Content
Pages
Templates
Phrases
Rules
Thesaurus
Keyword redirects
Promotion methods
Direct Usually within staging
File-based From staging to production
Where to configure?
Assembler.properties
Edit the store.factory settings
ecrStoreFactory
fileStoreFactory
Repository.configuration.path -
location where the content is
extracted to when you promote
content
Assembler-context.xml
Check Administrative section
Check bean
id="filestorefactory"
Need to restart Endeca Tools
Services
Promote content script -
from stg to prod
Promotes content
Promotes search configuration
Ifcr.exportConfigSnapshot -
exports search config from
workbench in your stg env
Ifcr.exportApplication - exports
content and content config
Livedgraphcluster.updateconfig
fromsnapshot - import search
config to mdex in prod
Assemblerupdate.updateasse
mblers - tells all assemblers in
your prod env to update
content and content config
Uses config in
Workbenchconfig.xml
How to promote from stg to
prod in isolated network using
file-based method
Workbenchconfig.xml is
different in both stg and prod
Manually move content and
config to shared location
Promote content in staging env
is used to export
Comment or delete
Livedgraphcluster.updateconfi
gfromsnapshot
Comment or delete
Assemblerupdate.updateAsse
mblers
Need ifcr.exportconfigsnapshot
Need ifcr.exportApplication
Promote content in prod is
used to import
Comment or delete
ifcr.exportconfigsnapshot
Comment or delete
ifcr.exportapplication
Need
livedgraphcluster.updateconfig
fromsnapshot
Need
Assemblerupdate.updateAsse
mblers
How to promote using direct
method?
Edit assembler-context.xml
Find the ecrStoreFactory entry
and change isAuthoring value
to false
Edit
workbenchConfiguration.xml
Uncomment
ifcr.promoteFromAuthoringToLi
ve
Delete or comment the lines
calling out
exportConfigSnapshot,
exportApplication,
updateConfigFromSnapshot,
and updateAssemblers
Content export file format
Workbench content
ECR content is extracted to zip
file - JSON
Content - rule-based
Pages - static, URL-based
content
Templates - structure and
content configuration
Services - node is used
internally for merchandising
content configued within
experience manager
Search Configuration
Search configuration is
extracted from ECR to zip file -
XML
Appname.merch.xml
Appname.merch-rule-
group.content.xml
Appname.merchzones.xml
Appname.phrases.xml
Appname.redirects.xml
Appname.thesaurus.xml