As of AEM Communities 6.1, a unique approach has been adopted for handling user generated content (UGC) submitted by site visitors (members) from the publish environment.
This approach is fundamentally different from the way the AEM platform handles site content that is generally managed from the author environment.
The AEM platform uses a node store that replicates site content from author to publish, while AEM Communities uses a single, common store for UGC that is never replicated.
For the common UGC store, it is necessary to choose a storage resource provider (SRP). The recommended choices are:
One other SRP option, JSRP - JCR Storage Resource Provider, does not support a common UGC store for the author and publish environments to both access.
Requiring a common store results in the following recommended topologies.
Establishing a common store for UGC is essential, and thus the underlying deployment is contingent on its ability to support a common store.
If the expected volume of UGC is high and a local MongoDB instance is possible, then the choice would be MSRP.
For both, the deployment may be based on any OAK microkernel.
To choose the appropriate common store, carefully consider the unique characteristics of each.
For more details on Oak microkernals, visit Recommended Deployments.
When the topology is a publish farm, relevant topics of importance are:
|MicroKernel||SITE CONTENTREPOSITORY||USER GENERATED CONTENTREPOSITORY||STORAGE RESOURCE PROVIDER||COMMON STORE|
|Deployment||SITE CONTENTREPOSITORY||USER GENERATED CONTENTREPOSITORY||STORAGE RESOURCE PROVIDER||COMMON STORE|
|TarMK Farm (default)||JCR||JCR||JSRP||No|
|Oak Cluster||JCR||JCR||JSRP||Yesfor publish environment only|
For non-production environments, JSRP provides simplicity in setting up a development environment with one author instance and one publish instance.
If choosing ASRP, DSRP or MSRP for production, it is also possible to setup a similar development environment using Adobe on-demand storage or MongoDB. For an example, see HowTo Setup MongoDB for Demo.
Discusses scynchronization of user data among publish farm instances.
Discusses the roles of users and user groups in the author and publish environments.
UGC common store
Describes the storage of community content separate from site content.
Basically, site content is stored in a node store. For Assets, a data store can be configured to store binary data. For Communities, a common store must be configured to select the SRP.
Describes the two node storage implementations: Tar and MongoDB.