AEM 6.5 LTS Replication

Route user requests to the appropriate specialist skill based on intent.

Intent Router

How to Use

1. Match the user's request to one row in the Intent Router table above.
2. Read the linked SKILL.md for that specialist skill.
3. Follow the workflow and guidance defined in that skill.
4. For complex scenarios spanning multiple skills (e.g., configure agent then troubleshoot), start with the primary intent and cross-reference as needed.

Skill Overview

Configure Replication Agent

Set up and configure replication agents for:

• Default agents: Author to Publish content distribution
• Dispatcher Flush agents: Cache invalidation
• Reverse replication: Publish to Author user-generated content flow
• Multiple publish instances: Load balancing and high availability

When to use: First-time setup, adding new publish instances, reconfiguring agents

Replicate Content

Activate and deactivate content through:

• Quick Publish: Simple one-click activation
• Manage Publication: Advanced scheduling and approval workflows
• Tree Activation: Hierarchical bulk publishing
• Package Manager: Specific content set distribution
• Workflows: Approval-based publishing
• Scheduled Activation: Time-based content publishing

When to use: Publishing pages, assets, or DAM content; unpublishing content

Replication API

Programmatic replication using official AEM 6.5 LTS public APIs:

• Replicator interface: Core replication methods
• ReplicationOptions: Configure synchronous/asynchronous, agent filtering
• ReplicationStatus: Query replication state
• AgentManager, ReplicationQueue, ReplicationListener: Advanced queue management and monitoring

When to use: Custom code integration, bulk operations, workflow process steps, servlets

Troubleshoot Replication

Diagnose and fix common issues:

• Blocked queues: FIFO queue failures
• Connection errors: Network, authentication, SSL issues
• Content not appearing: Dispatcher cache, permissions
• Agent configuration: URI, credentials, triggers
• Event queue issues: Stuck replication jobs

When to use: Replication failures, performance issues, content not distributing

Replication Orchestrator

Coordinates end-to-end replication workflows spanning multiple sub-skills:

• New Environment Setup: Configure agents → Test replication → Troubleshoot
• Production Incident Response: Diagnose → Fix → Verify
• Performance Optimization: Monitor → Tune → Validate
• Migration Preparation: Audit → Plan → Execute

When to use: Multi-step scenarios requiring coordination across configure, replicate, API, and troubleshoot skills

Common Workflows

First-Time Setup

1. Use Configure Replication Agent to set up default agent
2. Use Replicate Content to test with a sample page
3. If issues occur, use Troubleshoot Replication

Production Operations

1. Use Replicate Content for day-to-day publishing
2. Use Replication API for automated/bulk operations
3. Use Troubleshoot Replication when issues arise

Advanced Integration

1. Use Replication API to understand available methods
2. Use Configure Replication Agent to understand agent configuration
3. Use Troubleshoot Replication for debugging custom replication code

Foundation References

Shared reference materials used across all replication skills:

• Agent Types: Default, Dispatcher Flush, Reverse, and Static agents
• Queue Mechanics: FIFO processing, retry logic, queue management
• AEM 6.5 LTS Guardrails: Service users, timeouts, batch limits, best practices
• API Quick Reference: Replicator, ReplicationOptions, ReplicationStatus methods

Official Documentation

All skills reference official Adobe AEM 6.5 LTS documentation:

• Replication Documentation
• Replication Troubleshooting
• Replication API JavaDoc

Related Skills

• AEM Workflow: Integrate replication with approval workflows
• Dispatcher: Configure Dispatcher Flush agents for cache invalidation

Migration to AEM as a Cloud Service

AEM as a Cloud Service uses the Sling Distribution API instead of replication agents. If planning migration:

• Review Cloud Service Distribution Documentation
• For code migration patterns, see skills/aem/cloud-service/skills/best-practices/references/replication.md
• Avoid agent-specific coupling (filter by agent ID) to reduce migration complexity