As described on the parent Repository Restructuring in AEM 6.5 page, customers upgrading to Adobe Experience Manager (AEM) 6.5 should use this page to assess the work effort associated with repository changes impacting the AEM Assets Solution. Some changes require work effort during the AEM 6.5 upgrade process, while others can be deferred until a future upgrade.
With 6.5 Upgrade
Before Future Upgrade
Previous location | /etc/dam/jobs |
New location(s) | /var/dam/jobs |
Restructuring guidance | If any custom code depends on this location–that is, the code explicitly relies on this path–then the code must be updated to use the new location before upgrading. Ideally, Java™ APIs are used when available to reduce dependencies on any specific path in the JCR. Temp location to hold a zip file for the client to download. There is no need to update since when the client requests to download the asset. It generates a file in the new location. |
Notes | N/A |
Previous location | /etc/notification/email/default |
New location(s) |
|
Restructuring guidance | If the e-mail templates were modified by the customer, then perform the following actions to align with the new repository structure:
|
Notes | N/A |
Previous location | /etc/designs/assetshare |
New location(s) |
|
Restructuring guidance | For any Designs that are managed in SCM, and not written to at run-time by way of Design Dialogs, perform the following actions to align to the latest model:
For any Designs that are not managed in SCM, and modified run-time by way of Design Dialogs, do not move authorable designs out of |
Notes | N/A |
Previous location | /etc/dam/workflow/notification/email/downloadasset |
New location(s) |
|
Restructuring guidance | If the e-mail templates (downloadasset or transientworkflowcompleted) have been modified, then follow the below procedure to align to the new structure:
|
Notes | While /conf/global/settings/dam/workflownotification/email/downloadasset is technically supported for look-up (takes precedence before /apps by way of usual Sling CAConfig lookup, but after /etc ) the template could be placed in /conf/global/settings/dam/workflownotification/email/downloadasset . However, this is not recommended as there is no runtime UI to facilitate the editing of the e-mail template. |
Previous location | /etc/dam/drm/licenses/ |
---|---|
New location(s) | /libs/settings/dam/drm |
Restructuring guidance | N/A |
Notes | N/A |
Previous location | /etc/dam/adhocassetshare |
New location(s) |
|
Restructuring guidance | If the e-mail template was modified by the customer, then to align with the new repository structure:
|
Notes | While /conf/global/settings/dam/adhocassetshare is technically supported for look-up (it takes precedence before /apps by way of the usual Sling CAConfig lookup, but after /etc ), the template can be placed in /conf/global/settings/dam/adhocassetshare . However, this is not recommended as there is no runtime UI to facilitate the editing of the e-mail template |
Previous location | /etc/dam/indesign/scripts |
New location(s) |
|
Restructuring guidance | To Align with the new repository structure:
|
Notes | It is recommended customized scripts be stored under /apps , since that is the location where code should be stored. |
Previous location | /etc/dam/video |
New location(s) |
|
Restructuring guidance | Project level customizations must be cut and pasted under equivalent To align with the AEM 6.4 repository structure:
|
Notes | N/A |
Previous location | /etc/dam/presets/viewer |
New location(s) |
|
Restructuring guidance | For the out of the box Viewer Preset, it is only available in the new location. For the Custom Viewer preset:
You do not have to adjust their copyURL/embed code to point to |
Notes | N/A |
Previous location |
|
New location(s) | /libs/dam/clientlibs |
Restructuring guidance | Adjust any references to point to the new resources under Finally, clean up by removing the folders for the migrated clientlibs from |
Notes | N/A |