Hi kautuk,Thanks . Will wait for the updates

Could you add which of these (common docroot vs separate docroot) refers to option1 and option2 in your post And from a DAM cache invalidation POV1) in a common docroot if we maintain same depth as content tree then same statsfilelevel could handle DAM as well right?2) in a seperate docroot additional consideration needed as the dam get nested path within docroot? Any thoughts on how DAM cache invalidation can be made effective ? I can think of custom implementation that can send a dispatcher in...

Hi Jörg,Thanks for the details.Addtionally I have also followed these old post https://forums.adobe.com/thread/1082213 which refers to similar dispatcher does not understand sling mapped url by default (Could be for old dispatcher versions ) and recent dispatcher might work well with sling mapped url for multi domain - refering these lines "The /docroot property is set to the path of the root directory of the domain's site content in the Dispatcher cache. This path is used as the prefix for the ...

Hi Jörg,AEM is multi tenant for site content (SiteA and SiteB) and DAM (SiteA and SiteB) . we have node separation as here/content/SiteA/content/dam/SiteA /content/SiteB/content/dam/SiteBWe have a dispatcher flush farm as in the aem docsfor (2) and (3) as mentioned in my above post we have a common docroot as /usr/lib/apache/httpd-2.4.3/htdocs for both SiteA and SiteA instead of seperate /usr/lib/apache/httpd-2.4.3/htdocs/SiteA and /usr/lib/apache/httpd-2.4.3/htdocs/SiteB docroot and hope to con...