• AEM 6.2 Platform 
  • includes AEM Communities 6.2, package version 1.9

• AEM Communities license

•  Optional licenses for : 
  • Adobe Cloud for ASRP
  • MongoDB for MSRP
  • Communities enablement features
  • Adobe Analytics for Communities

AEM 6.2 Communities GA ships with Communities package version 1.9.
Feature packs for AEM 6.2 Communities are version 1.10.

All packages are made available through package share.

• install latest AEM 6.2 Updates
  it is important that platform updates be installed prior to Communities updates
• install latest available Communities feature pack
  • Communities Release Notes
  • Known Issues
• for Communities enablement features :
  • install the official JDBC driver for MySQL
  • install/update the AEM Communities SCORM-Engine
• for selected community content store :
  • configure ASRP  or  configure MSRP/Solr

Before installing Communities fix or feature packs, it is necessary to ensure the AEM platform is up-to-date. 

For the latest updates to AEM 6.2, be sure to check Adobe Experience Manager 6.2 hot fixes

AEM 6.2 Communities FP1 delivers fixes, new features and improvements for both for the engagement and enablement use cases.

• AEM-6.2-Communities-Feature-Pack-1
  • v1.10.60
  • 29 Aug 2016
• for Community Members
  • Richer and cleaner experience (buttons, pagination, sort orders, profiles, search results)
  • Predictive and suggestive search results
  • Email integration (notifications and subscriptions)
  • Sharing posts to social networks
  • Multilingual communities with inline translations
  • Badges and leaderboards
• for Community Administrators and Managers
  • Create community sites in multiple languages sharing the same content
  • Create and edit nested community groups within community sites
  • Configure advanced scoring and badging rules for expertise detection
  • Create, edit and manage community badges
  • Convert UGC contributions into AEM content fragments
  • View Analytics KPIs for individual community members (views, posts, likes, follows)
  • Pin forum posts and QnA questions to the top of the list
  • One-click export of community sites
• for Enablement Managers
  • More control over enablement resources (show to guest users, show in catalog, additional metadata)
• all fixes and improvements from previous versions

See also Communities Release Notes and Known Issues.

See Communities Version History for information on previous versions for AEM 6.2 Communities.

The Communities enablement feature uses a MySQL database for recording SCORM activities and learners.

The MySQL connector must be obtained and installed separately.

The necessary steps are :

1. download the ZIP archive from https://dev.mysql.com/downloads/connector/j/
   • version must be >= 5.1.38
2. extract mysql-connector-java-<version>-bin.jar (bundle) from the archive
3. use the web console to install and start the bundle :
   • for example, http://localhost:4502/system/console/bundles
   • select Install/Update
   • Browse... to select the bundle extracted from the downloaded ZIP archive
   • check that Oracle Corporation's JDBC Driver for MySQLcom.mysql.jdbc is active, and start it if not (or check the logs)
4. if installing on an existing deployment (after MySQL has been configured), then rebind JDBC to the new connector by resaving the JDBC configuration from the web console :
   • for example, http://localhost:4502/system/console/configMgr
   • locate Day Commons JDBC Connections Pool configuration
   • select to open
   • select Save
5. repeat steps 3 and 4 on all author and publish instances

Further information on installing bundles is found on the Web Console page.

Sharable Content Object Reference Model (SCORM) is a collection of standards and specifications for e-learning.  SCORM also defines how content may be packaged into a transferable ZIP file.

The AEM Communities scorm engine is required for the enablement feature.

• cq-social-scorm-package, v1.0.54, 2 Sep 2016

Each version of the SCORM package is compatible with all Communities releases.

The SCORM package should be installed on all AEM instances and is configured during setup of MySQL.

For the MSRP collection to support advanced multilingual search (MLS), new Solr plug-ins are required in addition to a custom schema and Solr configuration.  All required items are packaged into a downloadable zip file.

The advanced MLS download (also known as 'phasetwo') is available from the Adobe repository :

• AEM-SOLR-MLS-phasetwo
  • version 1.2.40, April 6, 2016
  • download AEM-SOLR-MLS-phasetwo-1.2.40.zip

For details and installation information, visit Solr Configuration for MSRP.

Packages Visible in Adobe AEM Cloud

The links to packages on this page require no running instance of AEM as they are to package share on adobeaemcloud.com.  While the packages are viewable, the Install button is for installing the packages into an Adobe hosted site.  If intending to install on a local AEM instance, selecting Install will result in an error.

How to Install on Local AEM Instance

To install the packages visible in adobeaemcloud.com on a local AEM instance, the package must first be downloaded to a local disk :

• select the Assets tab
• select download to disk

On the local AEM instance, use package manager (for example http://localhost:4502/crx/packmgr/), to upload to the local AEM's package repository.

Alternatively, accessing the package using package share from the local AEM instance (for example,http://localhost:4502/crx/packageshare/), the Download button will download to the local AEM instance's package repository.

Once in the local AEM instance's package repository, use package manager to install the package.

For more information, visit How to Work With Packages.

In AEM Communities, a common store is used to store user generated content (UGC) and is often referred to as the storage resource provider (SRP).  The recommended deployment centers on choosing an SRP option for the common store.  

The common store supports moderation of, and analytics on, UGC in the publish environment which eliminates the need for replication.

• Community Content Store : discusses the SRP storage options for AEM communities

• Recommended Topologies : discusses the topology to use depending on use case and SRP choice

When upgrading to the AEM 6.2 platform from previous versions of AEM, it is important to read Upgrading to AEM 6.2.

In addition to upgrading the platform, read Upgrading to AEM Communities 6.2 to learn about Communities changes.

When the deployment chosen is a publish farm, then one AEM publish instance must be identified as the primary publisher for activities which should not occur on all instances, such as features that rely on notifications or Adobe Analytics.

By default, the AEM Communities Publisher Configuration OSGi configuration is configured with the Primary Publisher checkbox checked, such that all publish instances in a publish farm would self-identify as the primary.  

Therefore, it is necessary to edit the configuration on all secondary publish instances to uncheck the Primary Publisher checkbox.

For all other (secondary) publish instances in a publish farm :

• sign in with administrator privileges
• access the web console
  • for example, http://localhost:4503/system/console/configMgr
• locate the AEM Communities Publisher Configuration
• select the edit icon
• uncheck the Primary Publisher box
• select Save

If not using port 4503 for the primary publish server, ensure the Replication Agent Config correctly identifies the publish server.

Replication is used for site content created in the publish environment, such as community groups.

There are two agents in the author environment that need the transport URI edited.  The following images show the results of changing the port from 4503 to 6103 by :

• access the Replication console on author
  • from global navigation : Tools, Deployment, Replication : Agents on author
• select the agent
• select edit
• select the Transport tab
• edit the URI to specify the correct port

When using the author environment to create sites, modify site properties or manage community members, it is necessary to access members registered in the publish environment instead of users registered on author.  

The tunnel service provides this access.  

To enable the tunnel service :

• on author
• sign in with administrative privileges
• access the Web Console
  • for example, http://localhost:4502/system/console/configMgr
• locate the AEM Communities Publish Tunnel Service
• select the edit icon
• check the enable box
• select Save

If using the Apache HTTP server, ensure that you use the correct server name for all relevant entries.

In particular, be careful to use the correct server name, not localhost, in the RedirectMatch. 

If using a Dispatcher, see :

• AEM's Dispatcher documentation
• latest Dispatcher release
• Configuring Dispatcher for Communities
• Known Issues

• Visit Administering Communities Sites to learn about creating a community site, configuring community site templates, moderating community content, managing members, and configuring messaging.

• Visit Developing Communities to learn about the social component framework (SCF) and customizing Communities components and features.

• Visit Authoring Communities Components to learn how to author with and configure Communities components.