@Mohit-Servicenow , The issue is due to absence of "com.adobe.cq.wcm.core.components" in the AEM. To fix the issue you can try following Remove the <scope> tag and let maven download the dependency directly from the Adobe repo.Embed the package inside your all module's POM file.  <embedded> <group...

Ahh, I misunderstood your question.Try this:Step 1: Check if your custom dispatcher headers are working as expected.You can validate this from the Dispatcher logs. Refer to this blog to validate: https://techrevel.blog/2023/09/05/exploring-aem-request-and-response-headers-analysis-of-browser-cdn-and...

@Ayoub_Tabai ,It would be great if you can also attach the error logs. Without the logs, it's difficult to pinpoint what is happening after deployment.You can start debugging your current issue on following - Check if all project related the bundles are getting activated.Check if all the component s...

Hello @Anudeep_Garnepudi ,Did you also add the header in your vhost file. if not you need to set the headers in your vhost file. Here is a example. <IfModule mod_headers.c> Header set x-aem-client-country "<value>" Header set x-aem-client-continent "<value>" </IfModule>  

Repository migration is not possible, but you can synchronize repositories between CRX1 and OAK.In any JCR-compliant repository, there are two components: a node store and a segment store. Instead of performing a migration, it is essential to synchronize each type individually, with a preference for...