replication-orchestrator

Orchestrates multi-step AEM 6.5 LTS replication workflows across configuration, replication, and troubleshooting sub-skills.

1|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aemgdc/aemdev --skill replication-orchestrator-aemgdc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: replication-orchestrator
Source: https://github.com/aemgdc/aemdev/tree/main/.agents/skills/replication-orchestrator
Command: npx skills add https://github.com/aemgdc/aemdev --skill replication-orchestrator-aemgdc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing AEM 6.5 LTS replication across environments involves many coordinated steps—configuring agents, testing content flow, diagnosing queue failures, and tuning performance. This Skill orchestrates those end-to-end workflows so nothing is missed during environment setup, incident response, optimization, or Cloud Service migration. ## Core Features & Use Cases - New Environment Setup: Step-by-step workflow to configure default replication agents, Dispatcher flush agents, test content replication, and enable JMX monitoring with verification checkpoints. - Production Incident Response: Structured triage covering symptom gathering, root-cause diagnosis (network, authentication, capacity, Dispatcher), fix implementation, and post-incident review. - Performance Optimization: Baseline measurement, bottleneck identification, and optimizations such as asynchronous replication, batching, and timeout tuning. - Migration Preparation: Audit of Replication API usage and planning for migration to AEM as a Cloud Service Sling Distribution patterns. - Use Case: A publish instance stops receiving content in production. Use this Skill to triage symptoms, diagnose the blocked queue via JMX metrics, apply the fix, verify resolution, and document the post-incident review. ## Quick Start Use the replication orchestrator to set up and verify replication between my AEM 6.5 author and publish instances, including the Dispatcher flush agent.

Frequently Asked Questions about replication-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up replication between AEM author and publish instances?▼

Create a default replication agent on Author pointing to the publish instance's /bin/receive endpoint with service user credentials, then enable and test it. Follow with a Dispatcher flush agent on each publish instance and verify with a test page activation.

How do I troubleshoot a blocked AEM replication queue?▼

Check the agent's JMX metrics (QueueNumEntries, QueueBlocked) and review error.log for root causes like network failures, 401 authentication errors, or an overloaded target instance. Retry failed items via the JMX retryFirst() operation after fixing the cause.

How do I configure a Dispatcher flush agent in AEM 6.5?▼

Create a flush agent on each publish instance with the transport URI pointing to the Dispatcher's /dispatcher/invalidate.cache endpoint and set the serialization type to Dispatcher Flush. Test connectivity to confirm cache invalidation works.

Does the AEM Replication API work in AEM as a Cloud Service?▼

No, the Replication API does not exist in AEM as a Cloud Service. Content distribution is handled automatically by the platform, so custom replication code must be refactored to use Cloud Service content publishing workflows and Sling Distribution patterns.

How can I improve AEM replication performance for bulk content?▼

Use asynchronous replication with ReplicationOptions.setSynchronous(false) and batch 100-500 paths per replicate call. For large DAM assets, increase connection and socket timeouts, and scale horizontally by adding publish instances.