Upgrading to AEM 6.2 Communities

You are reading the AEM 6.2 version of Upgrading to AEM 6.2 Communities.
This documentation is also available for the following versions:  AEM 6.3  AEM 6.1 

Depending on each site's topology and features, the following actions may be necessary when upgrading to AEM Communities 6.2.

This section is specific to Communities and supplements the information provided in Upgrading to AEM 6.2 (platform).

Upgrading from AEM 6.1 Communities or to Latest Feature Pack

When installing a new Communities feature pack on a deployment configured with MSRP, it will be necessary to 

  1. install the latest feature pack
  2. install the latest Solr config files
  3. reindex MSRP
      see section MSRP Reindex Tool

Upgrading from AEM 5.6.1 or Earlier

When upgrading from AEM 5.6.1 or earlier, it is recommended to read Upgrading to AEM 6.0 Social Communities from CQ 5.5

Note

For AEM 6.2, only direct upgrades from CQ 5.4 or later are supported.

If upgrading from an older version, it is recommended to upgrade to 6.0 first.

 

Upgrading with UGC

When upgrading to AEM Communities 6.2, if pre-existing UGC needs to be retained, then steps should be taken depending on whether the deployment of AEM 5.6.1 or AEM 6.0 Communities included Adobe cloud storage or on-premise storage of UGC .

To improve the performance and synchronization of community content, AEM Communities 6.2 requires a common store specifically for user generated content (UGC) which eliminates the use of replication of UGC between author and publish instances.

To learn more about the common store, commonly referred to as SRP, visit Community Content Storage.

Adobe Cloud Storage

If there exists a site created with AEM 6.0 or earlier, configured to use Adobe cloud storage, and the site is upgraded to AEM Communities 6.2, then :

For all AEM 6.2 author and publish instances

  • sign in with administrator privileges
  • configure ASRP
  • follow these steps to make pre-existing UGC visible :

 

file

Note

If Cloud Storage were to remain checked, it would appear (incorrectly) as if all community content had been lost.  This is because the SRP methods would be unable to locate the pre-existing UGC.

When Cloud Storage is unchecked, ASRP will use AEM 6.0 compatability-mode to access UGC.

 

On-premise Storage

If there exists a site created with AEM 6.0 or earlier, which did not use cloud storage, any pre-existing UGC must be converted to conform to the new structure introduced in AEM Communities 6.1 due to the common store.

For this purpose, an open source migration tool is available on GitHub :
AEM Communities UGC Migration Tool

AEM Communities UGC Migration Tool

The AEM Communities UGC Migration Tool is an open source migration tool, available on GitHub, that can be customized to export UGC from earlier versions of AEM social communities and import into AEM Communities 6.1 or later.

In additin to moving UGC from earlier versions, it is also possible to use the tool to move UGC from one SRP to another, such as from MSRP to DSRP.

Java APIs

When upgrading from AEM 6.0 social communities to AEM 6.2 Communities, be aware that many APIs have been reorganized into different packages.  Most should be easily resolved when using an IDE for customization of Communities features.

For details on the deprecated SocialUtils package, visit SocialUtils Refactoring.

See also Using Maven for Communities.

No JSP Component Templates

The social component framework (SCF) uses the HandlebarsJS (HBS) templating language in place of Java Server Pages (JSP) used prior to AEM 6.0.

In AEM 6.0, the JSP components remained alongside the new HBS framework components in the same location, with the HBS components typically located in subfolders named "hbs".

As of AEM 6.1, the JSP components were completely removed.  For Communities, it is recommended to replace all use of JSP components with SCF components.

Any questions?

Have a question about this or any other AEM topic? Ask our Community.
Learn more about AEM topics on our help hub.
Was this helpful?

By submitting your feedback, you accept the Adobe Terms of Use.

Thank you for submitting your feedback.