Abstract
The term “distribution” means the ability of picking one or more resources on a certain Sling instance in order to copy and persist them onto another Sling instance. The Sling Content Distribution module is able to distribute content by:
1. “pushing” from Sling instance A to Sling instance B
2. “pulling” from Sling instance B to Sling instance A
3. “synchronising” Sling instances A and B via(third) coordinating instance C
In this blog, I am going to list down all the steps required for synchronising two sling instances.
How to Test:
Make a change in any of the content in one of the publisher under /content/we-retail and validate the changes in the other publisher.
How to Debug:
Above changes done in the configMgr can be validated in below path:
http://localhost:4502/libs/granite/distribution/content/distribution-agent.html?agentName=socialpubsync
Click on Edit and change log level to Debug
Read Full Blog
Q&A
Please use this thread to ask the related questions.
Kautuk Sahni