For development and demonstration purposes, it will be necessary to run one author and one publish instance.
To do so, follow the basic AEM Getting Started instructions, which will result in:
For AEM Communities,
The author environment is for:
The publish environment is for:
If not familiar with AEM, view the documentation on basic handling and a quick guide to authoring pages.
This tutorial creates an engagement community site and is based on AEM Communities 6.2 feature pack version 1.10.
To ensure the latest feature pack is installed, visit:
For a tutorial that creates an enablement community site, visit Getting Started with AEM Communities for Enablement.
When Adobe Analytics is configured for the community site, information on community activity is available that enhances the community member’s experience as well as provides feedback to administrators of the site.
Integration with Adobe Analytics is optional.
The notifications feature, available by default for all sites created using the
Communities Sites console, provides an email channel for notifications.
What is necessary is for email to be properly configured for the site.
See Configuring Email.
When creating a community site in the author environment, the tunnel service makes possible the ability to assign roles to trusted community members registered in the publish environment. The tunnel service also allows access to community members from the Members and Groups consoles in the author environment.
The convention is for members and member groups created in the publish environment to not be recreated in the author environment. For more information see Managing Users and User Groups.
For simple instructions to enable the tunnel service on an author instance, see Tunnel Service.
Members of the Community Administrators group are able to create community sites, manage sites, manage members (they can ban members from the community), and moderate content.
Create a user on author, who is assigned the role of Community Administrator:
On the author instance
Sign in with administrator privileges
From the main console, navigate to Tools > Operations > Security > Users.
From the Edit menu, select Add User
Create New User dialog enter:
Scroll down to
Add User to Groups:
Enter ‘C’ to search
Community Enablement Managers
Before the demonstration versions of social login with Facebook and Twitter may be used, it is necessary to
For production servers, it is necessary to create the cloud services necessary to provide social login.
See Social Login with Facebook and Twitter.
Create tags to use for the engage and enablement tutorials, using the tag namespace of
Use the Tagging console to create the following tags:
Tutorial: Sports / Baseball
Tutorial: Sports / Gymnastics
Tutorial: Sports / Skiing
Tutorial: Arts / Visual
Tutorial: Arts / Auditory
Tutorial: Arts / History
Then follow the instructions to:
Sample package of tags created for the AEM Communities Getting Started Tutorials
It is recommended, but optional, to set MSRP (MongoDB) as the common store to experience the flexibility of moderating all UGC from either publish and/or author environments.
For instructions visit How to Setup MongoDB for Demo.
By default, the installation of the author and publish AEM instances result in user generated content (UGC) being stored in JCR Tar storage which is accessed using JSRP. JSRP is not a common store, which means UGC is visible only on the instance on which it was entered. Typically, UGC is entered on a publish instance and would not be visible in the author environment, resulting in all moderation tasks needing to use the publish instance.