Issue is Sling content Distribution setup across publishers. - AEM 6.5 | Community
Skip to main content
naveen_kvs
naveen_kvs
August 25, 2025
Solved

Issue is Sling content Distribution setup across publishers. - AEM 6.5

  • August 25, 2025
  • 2 replies
  • 1925 views

I have a use case that is resource-intensive, and I cannot run it on the author instance. Instead, I want to execute it on a single publisher, save the output as a DAM file, and then sync it across other publishers.

To achieve this, I decided to use Sling Content Distribution (forward distribution). Here’s what I’ve done so far:

  • Set up a forward distribution agent and a trigger on the source publisher.

  • Configured a local distribution package importer on the target instance.

From the source publisher side, the connection test is successful, and when I try distributing content from the console it reports “package delivered.” However, I don’t see any updates reflected in the target instance.

One observation: I can see the POST calls in the target instance’s request logs, but the actual content updates aren’t showing up.

 

Has anyone faced a similar issue or know what I might be missing in this setup?

 

Best answer by VishalKa5

Hi @naveen_kvs ,

 

Since you already switched to FileVault importer, used admin creds, and see no errors, the issue is likely a mismatch between exporter and importer or the package not being applied. In newer AEM, /system/console/slingdistribution isn’t always exposed—check Tools → Deployment → Distribution or /system/console/configMgr to verify configs. On the target, confirm if .zip packages are created under /var/sling/distribution/packages; if they exist but don’t unpack, the importer config is wrong, and if they don’t appear at all, the exporter/importer types don’t match. Also double-check that the forward agent is exporting the correct DAM path.

 

Thanks,

Vishal

2 replies

VishalKa5
VishalKa5
Level 5
August 25, 2025

Hi @naveen_kvs ,

 

Your setup is correct up to delivery, but the content not showing on the target means the package isn’t being applied. Common causes are:

  • Wrong importer type on target (must be Local Package Importer).
  • Package builder mismatch (FileVault vs JSON).
  • Service user permissions missing for /content/dam.
  • Check /system/console/slingdistribution on target for queue errors.
  • Inspect target error.log for access issues.

Try using a FileVault Package Importer to confirm packages are delivered; if they are, the issue is with applying them.

    naveen_kvs
    naveen_kvsAuthor
    August 25, 2025

    Hi @vishalka5,

    Thanks for your response and suggestions.

     

    My initial config is Local Package importer. Now, I have changed it to filevault, still the same.

    • Check /system/console/slingdistribution on target for queue errors. - I cannot find it and i do not see any errors in error.log 

    Also i have given admin creds in the forward agent so do not think it might be an access issue.

    VishalKa5
    VishalKa5Accepted solution
    Level 5
    August 25, 2025

    Hi @naveen_kvs ,

     

    Since you already switched to FileVault importer, used admin creds, and see no errors, the issue is likely a mismatch between exporter and importer or the package not being applied. In newer AEM, /system/console/slingdistribution isn’t always exposed—check Tools → Deployment → Distribution or /system/console/configMgr to verify configs. On the target, confirm if .zip packages are created under /var/sling/distribution/packages; if they exist but don’t unpack, the importer config is wrong, and if they don’t appear at all, the exporter/importer types don’t match. Also double-check that the forward agent is exporting the correct DAM path.

     

    Thanks,

    Vishal

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      September 2, 2025

      @naveen_kvs just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!

      Kautuk Sahni
      Terms & ConditionsAccessibility statement

      Loading footer...