In order to allow CRXDe via dispatcher, a configuration shoudl include a fidler similar to:/0012 { /type "allow" /url "/crx/*" }Note: you must restart your HTTPD server so dispatcher configuration takes an effect. Also, Dispatcher rules are counted from top to the bottom, so make sure that nothin...
Do you mean that offloading (the worker instance) does not send rendition and metadata back to the master? Despite the Publishing process, does offloading topology work?
AEM offloading workflow creates "jcr:content/metadata" node. The node is empty up until a worker extracts and sends metadata to the master. Can you test with "Modified event" and set Run Modes to Author only.
You have a large repository and hence it's expected that a migration/upgrade will take significant time. You can try to clean your CQ 5.6.x repository manually to reduce the total number of nodes to migrate over to AEM 6.x.1. Stop all replication agents, workflows and launchers.2. Make sure that you...
Might be you can consider AEM launches feature: Creating Launches By default, Live Copy automatically updates the launch pages as the source pages change. You can specify that a static copy is created to prevent automatic changes. Your authors can finish editing and promote it manually or even sched...
Have you had a chance to review the OOTB feature: Content Insight (pages) Content Insight and Asset Insight - Asset Insights It allows syncing with AEM author Analytics var and it those can be presented in a dashboard. In a case, you are using re-wring rules on a front-end, you would also need to c...
You can consider configuring an AEM DAM Offloading Offloading Jobs. Such a configuration helps to relax main AEM server and run DAM Update Asset workflow on a worker AEM