As described on the parent Repository Restructuring in AEM 6.4 page, customers upgrading to AEM 6.5 should use this page to assess the work effort associated with repository changes impacting the AEM Communities 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
Prior to Future Upgrade
Previous location | /etc/community/notifications |
New location(s) | /libs/settings/community/notifications |
Restructuring guidance | Manual migration ia needed if you want to move to new path under " You can perform the migration by setting the property |
Notes | N/A |
Previous location | /etc/community/subscriptions |
New location(s) | /libs/settings/community/subscriptions |
Restructuring guidance | Manual migration ia needed if you want to move to new path under " You can perform the migration by setting the property |
Notes | N/A |
Previous location | /etc/watchwords |
New location(s) | /libs/community/watchwords |
Restructuring guidance | A Lazy Migration task is available to clean up the Communities Configurations. The Task moves watchwords from If customized watchwords are stored in SCM, then they should be deployed to Migration task removes |
Notes | N/A |
Previous location | /etc/community/badging |
New location(s) | Badge Rules:
Badge Images: For default images: For custom images:
|
Restructuring guidance | Manual Migration is required. If your instance has customized the badging/scoring rules, there is no automated way to place all the rules under a bucket. Need customer inputs on which conf bucket (global or sitespecific) you want to use for your site. No UI available to configure the badging and scoring for a site. To align with new repository structure:
Finally, clean up by removing the resource |
Notes | N/A |
Previous location | /etc/designs/social/console |
New location(s) |
|
Restructuring guidance | N/A |
Notes | N/A |
Previous location | /etc/cloudservices/facebookconnect |
New location(s) |
|
Restructuring guidance | Any new Facebook Cloud Configurations must be migrated to the New Location.
|
Notes | N/A |
Previous location | /etc/social/config/languageOpts |
New location(s) | /libs/social/translation/languageOpts |
Restructuring guidance | N/A |
Notes | N/A |
Previous location | /etc/cloudservices/pinterestconnect |
New location(s) |
|
Restructuring guidance | Any new Pinterest Cloud Configurations must be migrated to the New Location.
|
Notes | N/A |
Previous location | /etc/community/scoring |
New location(s) | /libs/settings/community/scoring |
Restructuring guidance | To align with new repository structure, scoring rules can be stored in
Create context-aware configs in
Cleanup: Remove the resource |
Notes | N/A |
Previous location | /etc/cloudservices/twitterconnect |
New location(s) |
|
Restructuring guidance | Any new Twitter Cloud Configurations must be migrated to the New Location.
|
Notes | N/A |
Previous location | /etc/community/templates |
New location(s) | /libs/settings/community/templates |
Restructuring guidance | Adobe has provided a migration utility at: |
Notes | The existing custom templates would move to /conf/global/settings/community/template/<groups/sites/functions> |