Repository restructuring in AEM 6.4

Repository restructuring in AEM 6.4
  • AEM product code will always be placed in /libs, which must not be overwritten by custom code
  • Custom code should be placed in /apps, /content, and /conf

Related image

Starting from AEM 6.4 (see https://helpx.adobe.com/experience-manager/6-4/sites/deploying/using/repository-restructuring.html) content repository is to be reorganised prior to 6.5, and finally in 6.5 most probably will follow the rule as below:
  1. /etc should not be used (probably to be removed)
  2. any application code, clientlibs should be located under /apps
  3. any runtime data to be under /var or /content folder, 
  4. while the configurations should be rather under /conf
The groovy console should have its own content structure to be reorganised as follows:
  1. /etc/clientlibs/groovyconsole should rather go to /apps/groovyconsole/clientlibs
  2. /etc/groovyconsole to /apps/groovyconsole
  3. /etc/groovyconsole/scripts should go to /conf/groovyconsole/scripts or /var/groovyconsole/scripts
  4. /etc/groovyconsole/jcr:content/audit should to to /var/groovyconsole/audit

No comments:

Post a Comment