When AEM Communities uses JSRP as its storage option (the default), community content is stored in JCR and user generated content (UGC) is accessible only from the author or publish instance to which it was posted.
Because of the simplicity of deployment, JSRP is generally best suited for demonstration or development environments of one publish instance and one author instance.
By default, JSRP is the storage option for UGC.
The Storage Configuration console allows for the selection of the default storage configuration, which identifies which implementation of SRP to use.
In the author environment, to reach the Storage Configuration console
- from global navigation : Tools, Communities, Storage Configuration
While JSRP is the default configuration, to ensure the identical configuration is set in the publish environment :
- on author :
- from global navigation : Tools, Deployment, Replication
- select Activate Tree
- Start Path :
- browse to /etc/socialconfig/srpc/
- select Activate
Make sure JSRP has been configured to be the default provider by checking the configuration of the storage option. By default, the storage resource provider is JSRP.
On all author and publish AEM instances, revisit the Storage Configuration console or check the AEM repository :
This is not a bug. A characteristic of JSRP is that community content entered in the publish environment will only be visible in the publish environment.
If a single publish instance or if a publish cluster is deployed, then follow instructions for UGC Not Visible in JCR.
If a publish farm is deployed, a characteristic of JSRP is that community content will only be visible on the publish instance to which it was posted.
For UGC to be visible from any publish instance, a publish cluster is required.