Hi,the last time I looked into this, a custom predicate evaluator was requiredRegards,Opkar[0] http://labs.6dglobal.com/blog/2013-07-10/custom-predicateevaluators-or-how-i-learned-stop-worrying-and-love/[1] https://docs.adobe.com/docs/en/aem/6-2/develop/search/implementing-custom-predicate-evaluator...

Hi Ronny,unfortunately the terminology used in the documentation and product is confusing. The cluster that you see, which is used for job offloading, is actually based on Sling and is not clustering at the JCR level, as one saw in 5.x or MongoDB clustering as in 6(Although Sling Topologies/clusters...

Thanks for the clarification Joerg :)

Hi,as JK asked, what is the use case for using Reverse Replication? Previously it was used for synching of Users and User Generated Content. We now do not support reverse replication of UGC, instead you should use xSRP( requires AEM Communities licence). For users and groups you should use Sling Con...

This may be due the fact that crxde is not actually content in the repository, rather it is run from a content bundle, please see this answer from stack overflow:http://stackoverflow.com/questions/23718050/where-is-the-node-for-crx-explorer-stored-in-cq5-respositoryRegards,Opkar

Does it work if you use another path? For example under "/content"? For example working code look at the ACS Samples code: http://adobe-consulting-services.github.io/acs-aem-samples/Regards,Opkar

Hi John,it has been a long time since I looked at reverse replication, but the principles were to create a workflow launcher that would listen for changes in your tree, it would then replicate these changed which would go to the reverse replication queue. The changes would be sent to the author, whe...

Hi,how exactly did you change the sling.id of the work instance?I thought the only way to do this was to shutdown the instance, find the "sling.id.file" file somewhere under "crx-quickstart/felix", the path is not constant, but should be under a path like "quickstart/launchpad/felix/bundle*/data/sli...

Hi Ankur,yes you would have different ports for the two instances. The config file you have listed is not the same as the example file from the official documentation, you do not include the port number in the primary.host as the sync communication is done on port 8023, as specified in the file. The...

Hi viki,you could use the "replication-receiver" user for your replication agents. In order to use this user, you need to enable the user on the publish instance(set a password for the user), then configure your replication agent, to use the user replication user with the password previously set.Reg...