Hi Madhur,    Yes it is through replication via sling distribution.     Offloading is for splitting long running jobs to another instance & not for syncing.Thanks,

Hi Sandeep,    Deploying through ci looks good to me. OOB initial install creates programatically & should not be an issue.Thanks,

Hi Nanda,Verify the company proxy Or firewall settings. in case there is ELB make sure it is not timing out.Thanks,

Hi Nanda,     Make use of HttpClient api. Sample for api refer https://helpx.adobe.com/experience-manager/using/HttpClient_AEM.htmlThanks,

Hi Jay,AFAIK metadata schema editor use conf folder to see the changes.   Can you make your changes in /libs only rather than /apps & see it works.  If that works then I can guide for next steps of actual fix rather than updating the /libs directly.Thanks,

Hi Kumar,       Integrating asset picker with cf or asset finder is one of the option.https://docs.adobe.com/docs/en/aem/6-1/author/assets/managing-assets-touch-ui/asset-picker.htmlhttp://blogs.adobe.com/contentcorner/2016/03/03/integrating-aem-asset-selector-with-your-web-page/ Thanks,

Hi Madhur,It is common set up I have seen in all implementations with single author, multiple publishers/dispatcher on unix favours.  Coming to cluster no such option in tarmk & have to use cold stand by.Thanks,

Hi Michael,   Ready for review means aem send all the content to TMS & nothing pending in AEM.   Login at TEM & approve then the status will change.    If you have done that already then sounds like problem can be anywhere & needs a screen sharing session. I would recommend to reach to official conn...

Hi,AFAIK it is part of 6.2 & you can request for backport by filling a official support request.Thanks,

Hi Theo,  OOM sounds different issue all together. Attach the heap dump [A] to see what is happening.  Sounds like you might be using the default jvm settings.   2 gig should be fine but in you envirnoments we use 4 gigs.  Higher the better, we have few developers using 1 gigs also. [A]   https://he...