


Requirement: Any content change under var folder for a project specific path should be replicated to publish instance.
Approach decided: Forward sling distribution.
Post configurations deployment on cloud environment. Agent is getting created on environment along with all the configuration are also in place. For the content changes triggers are also working and request is reaching to agent, as we can see request in agent logs.
Forward sling distribution is not working in AEM cloud. we are getting below error.
org.apache.sling.distribution.common.RecoverableDistributionException: not enough rights
Although same configuration we have used on AEM 6.5 local instance and it's working fine. We are not using default agents or service users. We have added all the required ACL's permissions to the user.
We have add following configs for environments :
Author Instance:
1. Forward agent config:
{
"name":"fwdistribution",
"title":"fwdistribution",
"details":"This agent pushes content from author to publish",
"enabled":true,
"serviceName": "distributionSubService",
"log.level":"info",
"allowed.roots":[
"/var/ugcContents"
],
"queue.processing.enabled":true,
"packageImporter.endpoints":[
"endpoint0=https://publish.adobeaemcloud.com/libs/sling/distribution/services/importers/ugcfwimporter"
],
"triggers.target":"(name=jcrsync)"
}
2. Trigger config:
{
"name":"jcrsync",
"path":"/var/ugcContents",
"serviceName":"distributionSubService",
"deep": true
}
Publish Instance:
1. Importer config:
{
"name":"ugcfwimporter",
"packageBuilder.target": "(name=default)"
}
Thanks in advance for any help.
Views
Replies
Sign in to like this content
Total Likes
Hi @binary0010
The error clearly says some issues with the permissions. Can you check if this is happening with other paths (like /content) as well to further understand the problem?
Thanks,
Kiran Vedantam.
Have changed path but still we are getting same error in the agent logs:
Hi @binary0010 ,
Could you please try the solution mentioned here, it seems related - https://helpx.adobe.com/uk/experience-manager/kb/cm/cloudmanager-deploy-fails-due-to-sling-distribut...
Thanks,
Chitra
We have followed the same and added all the required ACL's permissions but same issue we are facing.
Please refer this document https://www.albinsblog.com/2020/05/sling-content-distribution-sync-use.html#.Y7_gbnZBy5c
Same document has been followed and things were working fine in 6.5 version but not on cloud.
Why do you use Sling Distribution and not the replication API? It's not clear from your post if you need to distribute content from author to publish or from publish to publish.
We have requirement to implement forward and reverse content distribution. As of now we have done changes for forward distribution but facing these issues.
We need to distribute content from author to publish.