Repository Restructuring for AEM Communities in 6.5

Manual migration ia needed if you want to move to new path under "/apps/settings". You can use the Granite Configuration Manager to perform the migration.

You can perform the migration by setting the property mergeList to true on the "/libs/settings/community/subscriptions" node and add an nt:unstructured child node.

A Lazy Migration task is available to clean up the Communities Configurations.

The Task moves watchwords from /etc/watchwords to /conf/global/settings/community/watchwords.

If customized watchwords are stored in SCM, then they should be deployed to /apps/settings/... and you must ensure that there is not an overlaying /conf/global/settings/... configuration that would take precedence.

Migration task removes /etc locations.

Badge Rules:

/libs/settings/community/badging

Badge Images:

For default images: /etc/community/badging/images are moved to /libs/community/badging/images

For custom images: /content/community/badging/images

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:

1. Create a site context bucket using the Configuration Browser under Tools
2. Go to the Site root
3. Set cq:confproperty to the bucket path where you want to store all your settings. The same can be set via the site Edit Wizard - Set cloud config input.
4. Move relevant badging rules and scoring rules from /etc/community/* to the site context bucket created in the previous step.
5. Adjust badging Rules and scoring Rules properties on site root to have relative references to new rule locations.
   1. For example, if the poperty for cq:conf = /conf/we-retail, then badgingRules [] = community/badging/rules if rules are now moved to this new bucket.
6. Similarly, adjust the references to scoring rules in a badging rule node to have a relativepath.

Finally, clean up by removing the resource /etc/community/badging

/libs/settings/wcm/designs/social/console

/apps/settings/wcm/designs/social/console

/conf/global/settings/cloudconfigs/facebookconnect

/conf/<tenant>/settings/cloudconfigs/facebookconnect

Any new Facebook Cloud Configurations must be migrated to the New Location.

1. Migrate existing configurations in the Previous Location to the New Location.

   1. Manually recreate new Facebook Social Login Configurations via the AEM authoring UI at Tools > Cloud Services > Facebook Social Login Configuration.
      or
   2. Copy any new Facebook Cloud Configurations from Previous Location to the appropriate New Location, under /conf/global or /conf/<tenant>.

2. Update any AEM Communities Site root to reference the new Facebook Social Login Configuration by setting the [cq:Page]/jcr:content@cq:conf property to the absolute path in the New Location.

3. Disassociate the legacy Facebook Connect Cloud Service from any AEM Communities site roots updated to reference the New Location.

/conf/global/settings/cloudconfigs/pinterestconnect

/conf/<tenant>/settings/cloudconfigs/pinterestconnect

Any new Pinterest Cloud Configurations must be migrated to the New Location.

1. Migrate existing configurations in the Previous Location to the New Location.

   1. Manually recreate new Pinterest Social Login Configurations via the AEM authoring UI at Tools > Cloud Services > Pinterest Social Login Configuration.
      or
   2. Copy any new Pinterest Cloud Configurations from Previous Location to the appropriate New Location under /conf/global or /conf/<tenant>.

2. Update any AEM Communities Site root to reference the new Pinterest Social Login Configuration by settings the [cq:Page]/jcr:content@cq:conf property to the absolute path in the New Location.

3. Disassociate the legacy Pinterest Connect Cloud Service from any AEM Communities site roots updated to reference the New Location.

To align with new repository structure, scoring rules can be stored in /apps/settings/ or /conf/.../settings

1. For /apps/settings, this would act as global or default rules managed in SCM.

Create context-aware configs in /conf/ by using CRXDELite:

1. Create the configs in the desired /conf/.../settings location
2. Communities site must have the cq:conf property property set.
   1. If no cq:conf is set, scoring rules would be directly read from the given path for property 'scoringRules' at the site's root node, for example: /content/we-retail/us/en/community/jcr:content

Cleanup: Remove the resource /etc/community/scoring

/conf/global/settings/cloudconfigs/twitterconnect

/conf/<tenant>/settings/cloudconfigs/twitterconnect

Any new Twitter Cloud Configurations must be migrated to the New Location.

1. Migrate existing configurations in the Previous Location to the New Location.

   1. Manually recreate new Twitter Social Login Configurations via the AEM authoring UI at Tools > Cloud Services > Twitter Social Login Configuration.
      or
   2. Copy any new Twitter Cloud Configurations from Previous Location to the appropriate New Location, under /conf/global or /conf/<tenant>.

2. Update any AEM Communities Site root to reference the new Twitter Social Login Configuration by setting the [cq:Page]/jcr:content@cq:conf property to the absolute path in the New Location.

3. Disassociate the legacy Twitter Connect Cloud Service from any AEM Communities site roots updated to reference the New Location.