[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M736AVWZG3A5T6MXBSDP8JZP":3,"skill-same:01M736AVWZG3A5T6MXBSDP8JZP":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M736AVWZG3A5T6MXBSDP8JZP","replicate-content",null,"Activate and deactivate content in AEM 6.5 LTS using replication agents for publishing to target instances","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-replication\u002Freplicate-content\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: replicate-content\ndescription: Activate and deactivate content in AEM 6.5 LTS using replication agents for publishing to target instances\nlicense: Apache-2.0\n---\n\n# Replicate Content in AEM 6.5 LTS\n\nThis skill guides you through activating (publishing) and deactivating (unpublishing) content in Adobe Experience Manager 6.5 LTS. Replication moves content from the Author environment to one or more Publish instances, making it available to end users.\n\n## When to Use This Skill\n\nUse this skill when you need to:\n- Publish pages from Author to Publish environment\n- Activate modified content to make changes live\n- Deactivate (unpublish) content to remove it from Publish\n- Perform tree activation for entire site sections\n- Use programmatic replication via API\n- Trigger replication via workflows\n- Schedule content activation\u002Fdeactivation\n- Replicate assets and DAM content\n- Perform package-based replication\n\n## Prerequisites\n\n- AEM 6.5 LTS Author instance with configured replication agents\n- At least one replication agent enabled and working (see `configure-replication-agent` skill)\n- Author permissions to activate\u002Fdeactivate content\n- Content created and ready for publication\n- Understanding of content approval workflows (if implemented)\n\n## Content Replication Methods\n\nAEM 6.5 LTS provides seven primary methods for triggering replication:\n\n| Method | Use Case | Scope | Access |\n|--------|----------|-------|--------|\n| **Quick Publish** | Simple page activation | Single page (shallow) | Page\u002FSites console |\n| **Manage Publication** | Advanced control | Single\u002Fmultiple pages | Page\u002FSites console |\n| **Tree Activation** | Hierarchical publishing | Page tree | Classic UI Tools |\n| **Package Manager** | Specific content sets | Custom packages | Tools console |\n| **Workflows** | Approval-based | Any content | Workflow console |\n| **Scheduled Activation** | Time-based | Single\u002Fmultiple pages | Page properties |\n| **Replication API** | Programmatic | Any resource | Custom code |\n\n## Method 1: Quick Publish (Recommended for Simple Cases)\n\nQuick Publish provides the fastest way to activate content with minimal clicks.\n\n### Steps:\n\n1. **Navigate to Sites console:**\n   ```\n   http:\u002F\u002Flocalhost:4502\u002Fsites.html\u002Fcontent\n   ```\n\n2. **Select content:**\n   - Click checkbox next to page(s) to publish\n   - Multiple selection supported\n\n3. **Click \"Quick Publish\":**\n   - Button appears in top toolbar\n   - Alternatively: Right-click → Quick Publish\n\n4. **Confirmation:**\n   - Green success message appears\n   - Page status shows \"Published\" with green checkmark\n   - Replication timestamp updates\n\n### Characteristics:\n- **Shallow replication**: Only selected page(s), not child pages\n- **Immediate**: No delay or scheduling\n- **Default agents**: Uses all enabled default replication agents\n- **No preview**: Content publishes immediately without review\n\n### When to use Quick Publish:\n- Simple page updates\n- Single page activation\n- No approval workflow needed\n- Immediate publication required\n\n## Method 2: Manage Publication (Advanced Control)\n\nManage Publication wizard provides granular control over what, when, and how content is published.\n\n### Steps:\n\n1. **Select content in Sites console:**\n   ```\n   Select page(s) → Click \"Manage Publication\" in toolbar\n   ```\n\n2. **Choose action:**\n   - **Publish**: Activate to Publish instances\n   - **Unpublish**: Deactivate from Publish instances\n   - **Publish Later**: Schedule future activation\n   - **Unpublish Later**: Schedule future deactivation\n\n3. **Configure scheduling (if \"Later\" selected):**\n   ```\n   Activation Date: [YYYY-MM-DD]\n   Activation Time: [HH:MM]\n   ```\n\n4. **Select scope:**\n   - **Selected**: Only chosen pages\n   - **Modified**: Pages modified since last publication\n   - **Published**: Already published pages\n   - **Include children**: Replicate child pages (tree activation)\n\n5. **Configure options:**\n   - **Create version**: Snapshot before publish\n   - **Workflow**: Trigger approval workflow\n   - **References**: Include referenced assets\u002Fpages\n   - **Activate modified pages only**: Skip unchanged content\n\n6. **Select workflow (if applicable):**\n   ```\n   Workflow Model: [Request for Activation \u002F Approval Workflow \u002F Custom]\n   Workflow Title: \"Publish Homepage Updates\"\n   ```\n\n7. **Review and confirm:**\n   - Summary shows:\n     - Pages to publish\n     - Schedule details\n     - Workflow assignment\n   - Click \"Publish\" or \"Next\" to proceed\n\n8. **Monitor progress:**\n   - Progress bar shows replication status\n   - Success\u002Ffailure notifications appear\n\n### Advanced Options:\n\n**Include References:**\n- Automatically publishes linked assets\n- Includes DAM images, documents\n- Publishes referenced experience fragments\n- Ensures no broken links on Publish\n\n**Create Version Before Publish:**\n- Creates snapshot in version history\n- Enables rollback if needed\n- Recommended for major updates\n\n**Only Modified Pages:**\n- Skips pages unchanged since last activation\n- Improves performance for large trees\n- Reduces replication queue load\n\n### When to use Manage Publication:\n- Publishing multiple pages with dependencies\n- Scheduled activation\u002Fdeactivation needed\n- Approval workflow required\n- Tree activation with selective inclusion\n- Creating version snapshots before publish\n\n## Method 3: Tree Activation (Hierarchical Publishing)\n\nTree Activation publishes an entire content tree hierarchy in one operation.\n\n### Steps (Classic UI):\n\n1. **Navigate to Tools console:**\n   ```\n   http:\u002F\u002Flocalhost:4502\u002Fmiscadmin\n   ```\n\n2. **Access Replication tools:**\n   - Click \"Replication\" in left sidebar\n   - Select \"Activate Tree\"\n\n3. **Configure tree activation:**\n   ```\n   Start Path: \u002Fcontent\u002Fmysite\u002Fen\n   \n   Options:\n   - Only Modified: ✓ (publish only changed pages)\n   - Only Activated: ✓ (publish only previously activated)\n   - Ignore Deactivated: ✓ (skip deactivated pages)\n   \n   Dry Run: ✓ (test without actually publishing)\n   ```\n\n4. **Execute or dry run:**\n   - **Dry Run**: Preview what will be published\n   - **Activate**: Execute actual replication\n   - Progress indicator shows page count\n\n5. **Review results:**\n   - Success count\n   - Failed pages (if any)\n   - Log details for troubleshooting\n\n### When to use Tree Activation:\n- Publishing entire site sections\n- Initial site launch\n- Large content migrations\n- Bulk replication operations\n\n### Performance considerations:\n- Can generate large replication queues\n- May take significant time for large trees\n- Use \"Only Modified\" to reduce load\n- Consider off-peak hours for large activations\n\n## Method 4: Package-Based Replication\n\nPackage Manager allows replicating specific content sets across environments.\n\n### Steps:\n\n1. **Create package:**\n   ```\n   Navigate to: http:\u002F\u002Flocalhost:4502\u002Fcrx\u002Fpackmgr\u002Findex.jsp\n   Click \"Create Package\"\n   \n   Package Name: content-update-2024-04\n   Group: myproject\n   Version: 1.0.0\n   ```\n\n2. **Define package filters:**\n   ```\n   Click \"Edit\" → \"Filters\" tab\n   \n   Add filter(s):\n   Root Path: \u002Fcontent\u002Fmysite\u002Fen\u002Fproducts\n   Rules: Include (default)\n   \n   Add another:\n   Root Path: \u002Fcontent\u002Fdam\u002Fmysite\u002Fimages\u002Fproducts\n   Rules: Include\n   ```\n\n3. **Build package:**\n   ```\n   Click \"Build\"\n   Wait for completion\n   Package .zip created\n   ```\n\n4. **Replicate package:**\n   ```\n   Click \"More\" → \"Replicate\"\n   Package sent to replication queue\n   Distributed to all enabled Publish instances\n   ```\n\n5. **Verify on Publish:**\n   ```\n   Navigate to Publish CRX Package Manager:\n   http:\u002F\u002Fpublish:4503\u002Fcrx\u002Fpackmgr\u002Findex.jsp\n   \n   Package should appear in list\n   Status: Installed\n   ```\n\n### When to use Package Replication:\n- Complex content sets with dependencies\n- Cross-environment deployments\n- Backup and restore operations\n- Specific node structure replication\n- Configuration replication\n\n## Method 5: Workflow-Based Replication\n\nWorkflows enable approval processes before content goes live.\n\n### Built-in Workflow: Request for Activation\n\n1. **Trigger workflow:**\n   ```\n   Select page(s) → Timeline panel (left sidebar)\n   Click \"Start Workflow\"\n   ```\n\n2. **Select workflow model:**\n   ```\n   Workflow: Request for Activation\n   Title: \"Homepage Redesign Approval\"\n   Comment: \"Please review updated homepage design\"\n   ```\n\n3. **Assign approver:**\n   ```\n   Participant: [User or Group]\n   Example: content-approvers\n   ```\n\n4. **Submit request:**\n   ```\n   Click \"Create\"\n   Workflow initiates\n   Notification sent to approver\n   ```\n\n5. **Approver actions:**\n   ```\n   Approver receives inbox notification:\n   http:\u002F\u002Flocalhost:4502\u002Faem\u002Finbox\n   \n   Options:\n   - Approve: Content activates to Publish\n   - Reject: Returns to author with comments\n   - Request changes: Sends back for revisions\n   ```\n\n6. **After approval:**\n   - Content automatically replicates\n   - Workflow completes\n   - Status updates to \"Published\"\n\n### Custom Workflow Models\n\nCreate custom workflows for complex approval chains:\n\n```\nNavigate to: Tools → Workflow → Models\n\nExample workflow steps:\n1. Content Author creates\u002Fmodifies\n2. → Content Lead reviews\n3. → Legal compliance check\n4. → Final approval\n5. → Automatic activation\n6. → Notification to stakeholders\n```\n\n## Method 6: Scheduled Activation\u002FDeactivation\n\nSchedule content to publish or unpublish at specific date\u002Ftime.\n\n### Configure via Page Properties:\n\n1. **Open page properties:**\n   ```\n   Select page → Properties (toolbar or right-click)\n   ```\n\n2. **Navigate to Advanced tab:**\n   ```\n   Click \"Advanced\" in left sidebar\n   ```\n\n3. **Set On Time (activation):**\n   ```\n   On Time: 2024-04-15 09:00:00\n   \n   Effect: Page automatically activates at specified time\n   Requires: Replication agent with \"On-\u002FOfftime reached\" trigger enabled\n   ```\n\n4. **Set Off Time (deactivation):**\n   ```\n   Off Time: 2024-05-15 23:59:00\n   \n   Effect: Page automatically deactivates at specified time\n   Removes from Publish instances\n   ```\n\n5. **Save properties:**\n   ```\n   Click \"Save & Close\"\n   ```\n\n### Verify Scheduled Activation:\n\n```\nReplication agent configuration:\nNavigate to: \u002Fetc\u002Freplication\u002Fagents.author\u002F[agent-name]\nTriggers tab: \"On-\u002FOfftime reached\" must be enabled\n```\n\n### When to use Scheduled Activation:\n- Marketing campaigns with specific launch dates\n- Time-sensitive announcements\n- Content embargoes\n- Temporary promotions\n- Event-based content\n\n## Method 7: Programmatic Replication (API)\n\nUse the Replication API for custom code integration.\n\n### Java API Example:\n\n```java\nimport com.day.cq.replication.Replicator;\nimport com.day.cq.replication.ReplicationActionType;\nimport com.day.cq.replication.ReplicationException;\nimport org.apache.sling.api.resource.ResourceResolver;\n\n@Reference\nprivate Replicator replicator;\n\npublic void activatePage(ResourceResolver resolver, String pagePath) \n    throws ReplicationException {\n    \n    \u002F\u002F Activate (publish) content\n    replicator.replicate(\n        resolver.adaptTo(Session.class),\n        ReplicationActionType.ACTIVATE,\n        pagePath\n    );\n}\n\npublic void deactivatePage(ResourceResolver resolver, String pagePath) \n    throws ReplicationException {\n    \n    \u002F\u002F Deactivate (unpublish) content\n    replicator.replicate(\n        resolver.adaptTo(Session.class),\n        ReplicationActionType.DEACTIVATE,\n        pagePath\n    );\n}\n\npublic void deleteFromPublish(ResourceResolver resolver, String pagePath) \n    throws ReplicationException {\n    \n    \u002F\u002F Delete content from Publish\n    replicator.replicate(\n        resolver.adaptTo(Session.class),\n        ReplicationActionType.DELETE,\n        pagePath\n    );\n}\n```\n\n### ReplicationActionType Options:\n\n| Type | Purpose | Effect |\n|------|---------|--------|\n| `ACTIVATE` | Publish content | Sends to Publish instances |\n| `DEACTIVATE` | Unpublish content | Removes from Publish |\n| `DELETE` | Delete from Publish | Permanent removal |\n| `TEST` | Test replication | Verifies connectivity |\n| `REVERSE` | Reverse replicate | Publish → Author |\n\n### Advanced API: ReplicationOptions\n\n```java\nimport com.day.cq.replication.ReplicationOptions;\nimport com.day.cq.replication.AgentFilter;\n\n\u002F\u002F Custom replication with options\nReplicationOptions opts = new ReplicationOptions();\n\n\u002F\u002F Synchronous replication (wait for completion)\nopts.setSynchronous(true);\n\n\u002F\u002F Suppress versions\nopts.setSuppressVersions(true);\n\n\u002F\u002F Filter to specific agents\nopts.setFilter(new AgentFilter() {\n    public boolean isIncluded(Agent agent) {\n        return agent.getId().equals(\"publish_instance_1\");\n    }\n});\n\n\u002F\u002F Execute with options\nreplicator.replicate(session, ReplicationActionType.ACTIVATE, pagePath, opts);\n```\n\n### CURL API Examples\n\n**Activate page (with error handling):**\n```bash\n# Note: Replace $AEM_USER:$AEM_PASSWORD with your service account credentials\nresponse=$(curl -s -w \"\\n%{http_code}\" -u $AEM_USER:$AEM_PASSWORD -X POST \\\n  http:\u002F\u002Flocalhost:4502\u002Fbin\u002Freplicate.json \\\n  -F \"cmd=Activate\" \\\n  -F \"path=\u002Fcontent\u002Fmysite\u002Fen\u002Fproducts\")\n\nhttp_code=$(echo \"$response\" | tail -n1)\nbody=$(echo \"$response\" | sed '$d')\n\nif [ \"$http_code\" -eq 200 ]; then\n  # Validate JSON response structure and success status\n  if command -v jq &> \u002Fdev\u002Fnull; then\n    success=$(echo \"$body\" | jq -r '.success \u002F\u002F empty')\n    path=$(echo \"$body\" | jq -r '.path \u002F\u002F empty')\n    \n    if [ \"$success\" = \"true\" ]; then\n      echo \"Activation successful for path: $path\"\n    else\n      error=$(echo \"$body\" | jq -r '.message \u002F\u002F \"Unknown error\"')\n      echo \"Activation reported failure: $error\"\n      exit 1\n    fi\n  else\n    echo \"Activation successful (HTTP 200)\"\n    echo \"$body\"\n  fi\nelse\n  echo \"Activation failed with HTTP $http_code\"\n  echo \"$body\"\n  exit 1\nfi\n```\n\n**Deactivate page (with error handling):**\n```bash\n# Note: Replace $AEM_USER:$AEM_PASSWORD with your service account credentials\nresponse=$(curl -s -w \"\\n%{http_code}\" -u $AEM_USER:$AEM_PASSWORD -X POST \\\n  http:\u002F\u002Flocalhost:4502\u002Fbin\u002Freplicate.json \\\n  -F \"cmd=Deactivate\" \\\n  -F \"path=\u002Fcontent\u002Fmysite\u002Fen\u002Fproducts\")\n\nhttp_code=$(echo \"$response\" | tail -n1)\nbody=$(echo \"$response\" | sed '$d')\n\nif [ \"$http_code\" -eq 200 ]; then\n  # Validate JSON response structure and success status\n  if command -v jq &> \u002Fdev\u002Fnull; then\n    success=$(echo \"$body\" | jq -r '.success \u002F\u002F empty')\n    path=$(echo \"$body\" | jq -r '.path \u002F\u002F empty')\n    \n    if [ \"$success\" = \"true\" ]; then\n      echo \"Deactivation successful for path: $path\"\n    else\n      error=$(echo \"$body\" | jq -r '.message \u002F\u002F \"Unknown error\"')\n      echo \"Deactivation reported failure: $error\"\n      exit 1\n    fi\n  else\n    echo \"Deactivation successful (HTTP 200)\"\n    echo \"$body\"\n  fi\nelse\n  echo \"Deactivation failed with HTTP $http_code\"\n  echo \"$body\"\n  exit 1\nfi\n```\n\n**Tree activation via CURL (with error handling):**\n```bash\n# Note: Replace $AEM_USER:$AEM_PASSWORD with your service account credentials\nresponse=$(curl -s -w \"\\n%{http_code}\" -u $AEM_USER:$AEM_PASSWORD -X POST \\\n  http:\u002F\u002Flocalhost:4502\u002Fetc\u002Freplication\u002Ftreeactivation.html \\\n  -F \"path=\u002Fcontent\u002Fmysite\u002Fen\" \\\n  -F \"onlyModified=true\")\n\nhttp_code=$(echo \"$response\" | tail -n1)\nbody=$(echo \"$response\" | sed '$d')\n\nif [ \"$http_code\" -eq 200 ]; then\n  # Note: Tree activation returns HTML, not JSON\n  # Check for success indicators in HTML response\n  if echo \"$body\" | grep -q \"successfully\"; then\n    echo \"Tree activation initiated successfully\"\n    # Extract and display any useful information from the HTML response\n    if command -v jq &> \u002Fdev\u002Fnull && echo \"$body\" | jq empty 2>\u002Fdev\u002Fnull; then\n      # If response is JSON (rare but possible)\n      status=$(echo \"$body\" | jq -r '.status \u002F\u002F \"initiated\"')\n      echo \"Status: $status\"\n    fi\n  else\n    echo \"Tree activation may have encountered issues. Check response:\"\n    echo \"$body\"\n  fi\nelse\n  echo \"Tree activation failed with HTTP $http_code\"\n  echo \"$body\"\n  exit 1\nfi\n```\n\n**Simple examples (without error handling):**\n\nFor quick testing, you can use simpler commands:\n```bash\n# Quick activate (no error handling)\ncurl -u $AEM_USER:$AEM_PASSWORD -X POST \\\n  http:\u002F\u002Flocalhost:4502\u002Fbin\u002Freplicate.json \\\n  -F \"cmd=Activate\" \\\n  -F \"path=\u002Fcontent\u002Fmysite\u002Fen\u002Fproducts\"\n\n# Quick deactivate (no error handling)\ncurl -u $AEM_USER:$AEM_PASSWORD -X POST \\\n  http:\u002F\u002Flocalhost:4502\u002Fbin\u002Freplicate.json \\\n  -F \"cmd=Deactivate\" \\\n  -F \"path=\u002Fcontent\u002Fmysite\u002Fen\u002Fproducts\"\n```\n\nNote: Simple examples above don't check for errors - use error handling versions in production scripts.\n\n## Asset Replication (DAM)\n\nReplicate digital assets from Author to Publish.\n\n### Steps:\n\n1. **Navigate to Assets console:**\n   ```\n   http:\u002F\u002Flocalhost:4502\u002Fassets.html\u002Fcontent\u002Fdam\n   ```\n\n2. **Select asset(s):**\n   - Click checkbox on images, videos, documents\n   - Multiple selection supported\n\n3. **Click \"Quick Publish\" or \"Manage Publication\":**\n   - Same options as page replication\n   - Assets replicate to Publish DAM\n\n4. **Verify asset renditions:**\n   - Original asset replicates\n   - All renditions replicate (thumbnails, web-optimized, etc.)\n   - Metadata replicates\n\n### Asset Replication Considerations:\n\n**Large file handling:**\n- Binary-less replication available for shared datastore\n- Direct binary access reduces replication overhead\n- Configure in replication agent: Serialization Type = Binary-less\n\n**Asset dependencies:**\n- Replicate referenced assets when publishing pages\n- Use \"Include References\" in Manage Publication\n- Avoids broken image links on Publish\n\n## Deactivation (Unpublishing)\n\nRemove content from Publish instances.\n\n### Quick Unpublish:\n\n```\nSites console → Select page(s) → Quick Unpublish\n```\n\n### Manage Publication (Unpublish):\n\n```\nSites console → Select page(s) → Manage Publication\nAction: Unpublish\nScope: Selected \u002F Include children\nClick \"Unpublish\"\n```\n\n### Effect of Deactivation:\n- Content removed from Publish instances\n- URLs return 404 on Publish\n- Content remains on Author (not deleted)\n- Can be re-activated later\n- Dispatcher cache invalidated\n\n## Monitoring Replication Status\n\n### Check Page Replication Status:\n\n**Sites console:**\n- Green checkmark = Published\n- Gray circle = Never published\n- Orange dot = Modified since last publish\n- Timeline shows replication history\n\n**Page Properties:**\n- Click page → Properties → Basic tab\n- Shows: Last published, Last published by, Last modified\n\n### Replication Queue Status:\n\n```\nNavigate to: Tools → Deployment → Replication\nClick: Agents on author\nSelect: [agent name]\n\nView:\n- Queue status (idle\u002Factive\u002Fblocked)\n- Pending items count\n- Last replication timestamp\n```\n\n### Replication Logs:\n\n```\nNavigate to: Tools → Operations → Logs\n\nLog file: replication.log\nLocation: crx-quickstart\u002Flogs\u002Freplication.log\n\nTypical entries:\n- Replication initiated: path, type, user\n- Replication succeeded\u002Ffailed: status, duration\n- Queue events: item added, processed, failed\n```\n\n## Troubleshooting Replication\n\n### Content Not Appearing on Publish\n\n**Check replication status:**\n1. Verify page shows \"Published\" in Sites console\n2. Check replication timestamp is recent\n3. Review replication agent queue (should be empty after processing)\n\n**Verify on Publish directly:**\n```\nhttp:\u002F\u002Fpublish-host:4503\u002Fcontent\u002Fmysite\u002Fen\u002Fpage-name.html\n```\n\n**Check Dispatcher cache:**\n- May serve cached old version\n- Wait for cache invalidation\n- Or manually flush cache\n- Verify Dispatcher Flush agent is enabled and working\n\n### Replication Fails\n\n**Common causes:**\n\n1. **Replication agent blocked:**\n   - Check agent status (should be green)\n   - Review queue for failed items\n   - Click \"Force Retry\" or \"Clear\" failed item\n\n2. **Publish instance unavailable:**\n   - Verify Publish is running: `http:\u002F\u002Fpublish:4503\u002Fsystem\u002Fconsole`\n   - Test agent connection\n   - Check network connectivity\n\n3. **Insufficient permissions:**\n   - Verify Agent User Id has replication privileges\n   - Check user permissions on target content paths\n   - Review error logs for permission denied messages\n\n4. **Content locked:**\n   - Check if page is locked by another user\n   - Unlock page: Page → Unlock\n   - Retry replication\n\n### Page Modified After Publication\n\nIf page shows orange dot (modified since publish):\n\n```\nOption 1: Re-publish changes\nSelect page → Quick Publish\n\nOption 2: Review changes first\nSelect page → Manage Publication\nCheck \"Modified\" scope to see what changed\nProceed with publication\n```\n\n## Best Practices\n\n1. **Use appropriate method:**\n   - Quick Publish for simple single-page updates\n   - Manage Publication for complex scenarios\n   - Tree Activation for entire sections\n   - Workflows for approval processes\n\n2. **Verify before publishing:**\n   - Preview content in Author\n   - Use staging\u002FUAT environment first\n   - Test with limited user group before full launch\n\n3. **Monitor replication:**\n   - Check replication status after activation\n   - Verify content appears correctly on Publish\n   - Review logs for errors\n\n4. **Schedule large activations:**\n   - Use off-peak hours for tree activations\n   - Avoid business hours for major content releases\n   - Coordinate with operations team\n\n5. **Handle dependencies:**\n   - Always publish referenced assets\n   - Use \"Include References\" option\n   - Verify asset paths are correct\n\n6. **Use workflows for sensitive content:**\n   - Implement approval for homepage, legal pages\n   - Multi-stage review for compliance\n   - Audit trail via workflow history\n\n7. **Clean up deactivated content:**\n   - Regularly review unpublished pages\n   - Delete obsolete content from Author\n   - Maintain organized content tree\n\n8. **Test replication agents:**\n   - Periodically test agent connectivity\n   - Verify multiple Publish instances receiving content\n   - Monitor agent performance metrics\n\n## Security Considerations\n\n**Replication permissions:**\n- Grant minimum required activation rights\n- Use groups for permission management\n- Audit replication activity via logs\n\n**Sensitive content:**\n- Use workflows for approval\n- Restrict activation to authorized users\n- Implement content security policies\n\n**API usage:**\n- Secure service user accounts for programmatic replication\n- Never hardcode credentials\n- Use resource resolver with appropriate permissions\n\n## Related Skills\n\n- `configure-replication-agent`: Set up and configure replication agents\n- `troubleshoot-replication`: Diagnose and fix replication issues\n- For AEM as a Cloud Service, see content distribution documentation (different architecture)\n\n## Success Criteria\n\n- ✓ Content successfully published to Publish instance(s)\n- ✓ Page status shows \"Published\" with green checkmark\n- ✓ Content visible on Publish URL\n- ✓ Replication agent queue processed without errors\n- ✓ Referenced assets also published\n- ✓ Dispatcher cache invalidated (if applicable)\n- ✓ Scheduled activation configured correctly (if used)\n- ✓ Workflow approval completed (if required)\n- ✓ Deactivation removes content from Publish (if tested)\n- ✓ Replication logs show successful entries\n\n## Additional Resources\n\n- [Official AEM 6.5 LTS Replication Documentation](https:\u002F\u002Fexperienceleague.adobe.com\u002Fen\u002Fdocs\u002Fexperience-manager-65-lts\u002Fcontent\u002Fimplementing\u002Fdeploying\u002Fconfiguring\u002Freplication)\n- [AEM 6.5 LTS Replication Troubleshooting Guide](https:\u002F\u002Fexperienceleague.adobe.com\u002Fen\u002Fdocs\u002Fexperience-manager-65-lts\u002Fcontent\u002Fimplementing\u002Fdeploying\u002Fconfiguring\u002Ftroubleshoot-rep)\n- [AEM 6.5 LTS Documentation Hub](https:\u002F\u002Fexperienceleague.adobe.com\u002Fen\u002Fdocs\u002Fexperience-manager-65-lts)\n- [Replication API JavaDoc (Package Summary)](https:\u002F\u002Fdeveloper.adobe.com\u002Fexperience-manager\u002Freference-materials\u002F6-5-lts\u002Fjavadoc\u002Fcom\u002Fday\u002Fcq\u002Freplication\u002Fpackage-summary.html)\n- [Managing Publications Documentation](https:\u002F\u002Fexperienceleague.adobe.com\u002Fdocs\u002Fexperience-manager-65\u002Fauthoring\u002Fauthoring\u002Fpublishing-pages.html)\n- Workflow Models documentation for approval processes\n","# Replicate Content in AEM 6.5 LTS\n\nThis skill guides you through activating (publishing) and deactivating (unpublishing) content in Adobe Experience Manager 6.5 LTS. Replication moves content from the Author environment to one or more Publish instances, making it available to end users.\n\n## When to Use This Skill\n\nUse this skill when you need to:\n- Publish pages from Author to Publish environment\n- Activate modified content to make changes live\n- Deactivate (unpublish) content to remove it from Publish\n- Perform tree activation for entire site sections\n- Use programmatic replication via API\n- Trigger replication via workflows\n- Schedule content activation\u002Fdeactivation\n- Replicate assets and DAM content\n- Perform package-based replication\n\n## Prerequisites\n\n- AEM 6.5 LTS Author instance with configured replication agents\n- At least one replication agent enabled and working (see `configure-replication-agent` skill)\n- Author permissions to activate\u002Fdeactivate content\n- Content created and ready for publication\n- Understanding of content approval workflows (if implemented)\n\n## Content Replication Methods\n\nAEM 6.5 LTS provides seven primary methods for triggering replication:\n\n| Method | Use Case | Scope | Access |\n|--------|----------|-------|--------|\n| **Quick Publish** | Simple page activation | Single page (shallow) | Page\u002FSites console |\n| **Manage Publication** | Advanced control | Single\u002Fmultiple pages | Page\u002FSites console |\n| **Tree Activation** | Hierarchical publishing | Page tree | Classic UI Tools |\n| **Package Manager** | Specific content sets | Custom packages | Tools console |\n| **Workflows** | Approval-based | Any content | Workflow console |\n| **Scheduled Activation** | Time-based | Single\u002Fmultiple pages | Page properties |\n| **Replication API** | Programmatic | Any resource | Custom code |\n\n## Method 1: Quick Publish (Recommended for Simple Cases)\n\nQuick Publish provides the fastest way to activate content with minimal clicks.\n\n### Steps:\n\n1. **Navigate to Sites console:**\n   ```\n   http:\u002F\u002Flocalhost:4502\u002Fsites.html\u002Fcontent\n   ```\n\n2. **Select content:**\n   - Click checkbox next to page(s) to publish\n   - Multiple selection supported\n\n3. **Click \"Quick Publish\":**\n   - Button appears in top toolbar\n   - Alternatively: Right-click → Quick Publish\n\n4. **Confirmation:**\n   - Green success message appears\n   - Page status shows \"Published\" with green checkmark\n   - Replication timestamp updates\n\n### Characteristics:\n- **Shallow replication**: Only selected page(s), not child pages\n- **Immediate**: No delay or scheduling\n- **Default agents**: Uses all enabled default replication agents\n- **No preview**: Content publishes immediately without review\n\n### When to use Quick Publish:\n- Simple page updates\n- Single page activation\n- No approval workflow needed\n- Immediate publication required\n\n## Method 2: Manage Publication (Advanced Control)\n\nManage Publication wizard provides granular control over what, when, and how content is published.\n\n### Steps:\n\n1. **Select content in Sites console:**\n   ```\n   Select page(s) → Click \"Manage Publication\" in toolbar\n   ```\n\n2. **Choose action:**\n   - **Publish**: Activate to Publish instances\n   - **Unpublish**: Deactivate from Publish instances\n   - **Publish Later**: Schedule future activation\n   - **Unpublish Later**: Schedule future deactivation\n\n3. **Configure scheduling (if \"Later\" selected):**\n   ```\n   Activation Date: [YYYY-MM-DD]\n   Activation Time: [HH:MM]\n   ```\n\n4. **Select scope:**\n   - **Selected**: Only chosen pages\n   - **Modified**: Pages modified since last publication\n   - **Published**: Already published pages\n   - **Include children**: Replicate child pages (tree activation)\n\n5. **Configure options:**\n   - **Create version**: Snapshot before publish\n   - **Workflow**: Trigger approval workflow\n   - **References**: Include referenced assets\u002Fpages\n   - **Activate modified pages only**: Skip unchanged content\n\n6. **Select workflow (if applicable):**\n   ```\n   Workflow Model: [Request for Activation \u002F Approval Workflow \u002F Custom]\n   Workflow Title: \"Publish Homepage Updates\"\n   ```\n\n7. **Review and confirm:**\n   - Summary shows:\n     - Pages to publish\n     - Schedule details\n     - Workflow assignment\n   - Click \"Publish\" or \"Next\" to proceed\n\n8. **Monitor progress:**\n   - Progress bar shows replication status\n   - Success\u002Ffailure notifications appear\n\n### Advanced Options:\n\n**Include References:**\n- Automatically publishes linked assets\n- Includes DAM images, documents\n- Publishes referenced experience fragments\n- Ensures no broken links on Publish\n\n**Create Version Before Publish:**\n- Creates snapshot in version history\n- Enables rollback if needed\n- Recommended for major updates\n\n**Only Modified Pages:**\n- Skips pages unchanged since last activation\n- Improves performance for large trees\n- Reduces replication queue load\n\n### When to use Manage Publication:\n- Publishing multiple pages with dependencies\n- Scheduled activation\u002Fdeactivation needed\n- Approval workflow required\n- Tree activation with selective inclusion\n- Creating version snapshots before publish\n\n## Method 3: Tree Activation (Hierarchical Publishing)\n\nTree Activation publishes an entire content tree hierarchy in one operation.\n\n### Steps (Classic UI):\n\n1. **Navigate to Tools console:**\n   ```\n   http:\u002F\u002Flocalhost:4502\u002Fmiscadmin\n   ```\n\n2. **Access Replication tools:**\n   - Click \"Replication\" in left sidebar\n   - Select \"Activate Tree\"\n\n3. **Configure tree activation:**\n   ```\n   Start Path: \u002Fcontent\u002Fmysite\u002Fen\n   \n   Options:\n   - Only Modified: ✓ (publish only changed pages)\n   - Only Activated: ✓ (publish only previously activated)\n   - Ignore Deactivated: ✓ (skip deactivated pages)\n   \n   Dry Run: ✓ (test without actually publishing)\n   ```\n\n4. **Execute or dry run:**\n   - **Dry Run**: Preview what will be published\n   - **Activate**: Execute actual replication\n   - Progress indicator shows page count\n\n5. **Review results:**\n   - Success count\n   - Failed pages (if any)\n   - Log details for troubleshooting\n\n### When to use Tree Activation:\n- Publishing entire site sections\n- Initial site launch\n- Large content migrations\n- Bulk replication operations\n\n### Performance considerations:\n- Can generate large replication queues\n- May take significant time for large trees\n- Use \"Only Modified\" to reduce load\n- Consider off-peak hours for large activations\n\n## Method 4: Package-Based Replication\n\nPackage Manager allows replicating specific content sets across environments.\n\n### Steps:\n\n1. **Create package:**\n   ```\n   Navigate to: http:\u002F\u002Flocalhost:4502\u002Fcrx\u002Fpackmgr\u002Findex.jsp\n   Click \"Create Package\"\n   \n   Package Name: content-update-2024-04\n   Group: myproject\n   Version: 1.0.0\n   ```\n\n2. **Define package filters:**\n   ```\n   Click \"Edit\" → \"Filters\" tab\n   \n   Add filter(s):\n   Root Path: \u002Fcontent\u002Fmysite\u002Fen\u002Fproducts\n   Rules: Include (default)\n   \n   Add another:\n   Root Path: \u002Fcontent\u002Fdam\u002Fmysite\u002Fimages\u002Fproducts\n   Rules: Include\n   ```\n\n3. **Build package:**\n   ```\n   Click \"Build\"\n   Wait for completion\n   Package .zip created\n   ```\n\n4. **Replicate package:**\n   ```\n   Click \"More\" → \"Replicate\"\n   Package sent to replication queue\n   Distributed to all enabled Publish instances\n   ```\n\n5. **Verify on Publish:**\n   ```\n   Navigate to Publish CRX Package Manager:\n   http:\u002F\u002Fpublish:4503\u002Fcrx\u002Fpackmgr\u002Findex.jsp\n   \n   Package should appear in list\n   Status: Installed\n   ```\n\n### When to use Package Replication:\n- Complex content sets with dependencies\n- Cross-environment deployments\n- Backup and restore operations\n- Specific node structure replication\n- Configuration replication\n\n## Method 5: Workflow-Based Replication\n\nWorkflows enable approval processes before content goes live.\n\n### Built-in Workflow: Request for Activation\n\n1. **Trigger workflow:**\n   ```\n   Select page(s) → Timeline panel (left sidebar)\n   Click \"Start Workflow\"\n   ```\n\n2. **Select workflow model:**\n   ```\n   Workflow: Request for Activation\n   Title: \"Homepage Redesign Approval\"\n   Comment: \"Please review updated homepage design\"\n   ```\n\n3. **Assign approver:**\n   ```\n   Participant: [User or Group]\n   Example: content-approvers\n   ```\n\n4. **Submit request:**\n   ```\n   Click \"Create\"\n   Workflow initiates\n   Notification sent to approver\n   ```\n\n5. **Approver actions:**\n   ```\n   Approver receives inbox notification:\n   http:\u002F\u002Flocalhost:4502\u002Faem\u002Finbox\n   \n   Options:\n   - Approve: Content activates to Publish\n   - Reject: Returns to author with comments\n   - Request changes: Sends back for revisions\n   ```\n\n6. **After approval:**\n   - Content automatically replicates\n   - Workflow completes\n   - Status updates to \"Published\"\n\n### Custom Workflow Models\n\nCreate custom workflows for complex approval chains:\n\n```\nNavigate to: Tools → Workflow → Models\n\nExample workflow steps:\n1. Content Author creates\u002Fmodifies\n2. → Content Lead reviews\n3. → Legal compliance check\n4. → Final approval\n5. → Automatic activation\n6. → Notification to stakeholders\n```\n\n## Method 6: Scheduled Activation\u002FDeactivation\n\nSchedule content to publish or unpublish at specific date\u002Ftime.\n\n### Configure via Page Properties:\n\n1. **Open page properties:**\n   ```\n   Select page → Properties (toolbar or right-click)\n   ```\n\n2. **Navigate to Advanced tab:**\n   ```\n   Click \"Advanced\" in left sidebar\n   ```\n\n3. **Set On Time (activation):**\n   ```\n   On Time: 2024-04-15 09:00:00\n   \n   Effect: Page automatically activates at specified time\n   Requires: Replication agent with \"On-\u002FOfftime reached\" trigger enabled\n   ```\n\n4. **Set Off Time (deactivation):**\n   ```\n   Off Time: 2024-05-15 23:59:00\n   \n   Effect: Page automatically deactivates at specified time\n   Removes from Publish instances\n   ```\n\n5. **Save properties:**\n   ```\n   Click \"Save & Close\"\n   ```\n\n### Verify Scheduled Activation:\n\n```\nReplication agent configuration:\nNavigate to: \u002Fetc\u002Freplication\u002Fagents.author\u002F[agent-name]\nTriggers tab: \"On-\u002FOfftime reached\" must be enabled\n```\n\n### When to use Scheduled Activation:\n- Marketing campaigns with specific launch dates\n- Time-sensitive announcements\n- Content embargoes\n- Temporary promotions\n- Event-based content\n\n## Method 7: Programmatic Replication (API)\n\nUse the Replication API for custom code integration.\n\n### Java API Example:\n\n```java\nimport com.day.cq.replication.Replicator;\nimport com.day.cq.replication.ReplicationActionType;\nimport com.day.cq.replication.ReplicationException;\nimport org.apache.sling.api.resource.ResourceResolver;\n\n@Reference\nprivate Replicator replicator;\n\npublic void activatePage(ResourceResolver resolver, String pagePath) \n    throws ReplicationException {\n    \n    \u002F\u002F Activate (publish) content\n    replicator.replicate(\n        resolver.adaptTo(Session.class),\n        ReplicationActionType.ACTIVATE,\n        pagePath\n    );\n}\n\npublic void deactivatePage(ResourceResolver resolver, String pagePath) \n    throws ReplicationException {\n    \n    \u002F\u002F Deactivate (unpublish) content\n    replicator.replicate(\n        resolver.adaptTo(Session.class),\n        ReplicationActionType.DEACTIVATE,\n        pagePath\n    );\n}\n\npublic void deleteFromPublish(ResourceResolver resolver, String pagePath) \n    throws ReplicationException {\n    \n    \u002F\u002F Delete content from Publish\n    replicator.replicate(\n        resolver.adaptTo(Session.class),\n        ReplicationActionType.DELETE,\n        pagePath\n    );\n}\n```\n\n### ReplicationActionType Options:\n\n| Type | Purpose | Effect |\n|------|---------|--------|\n| `ACTIVATE` | Publish content | Sends to Publish instances |\n| `DEACTIVATE` | Unpublish content | Removes from Publish |\n| `DELETE` | Delete from Publish | Permanent removal |\n| `TEST` | Test replication | Verifies connectivity |\n| `REVERSE` | Reverse replicate | Publish → Author |\n\n### Advanced API: ReplicationOptions\n\n```java\nimport com.day.cq.replication.ReplicationOptions;\nimport com.day.cq.replication.AgentFilter;\n\n\u002F\u002F Custom replication with options\nReplicationOptions opts = new ReplicationOptions();\n\n\u002F\u002F Synchronous replication (wait for completion)\nopts.setSynchronous(true);\n\n\u002F\u002F Suppress versions\nopts.setSuppressVersions(true);\n\n\u002F\u002F Filter to specific agents\nopts.setFilter(new AgentFilter() {\n    public boolean isIncluded(Agent agent) {\n        return agent.getId().equals(\"publish_instance_1\");\n    }\n});\n\n\u002F\u002F Execute with options\nreplicator.replicate(session, ReplicationActionType.ACTIVATE, pagePath, opts);\n```\n\n### CURL API Examples\n\n**Activate page (with error handling):**\n```bash\n# Note: Replace $AEM_USER:$AEM_PASSWORD with your service account credentials\nresponse=$(curl -s -w \"\\n%{http_code}\" -u $AEM_USER:$AEM_PASSWORD -X POST \\\n  http:\u002F\u002Flocalhost:4502\u002Fbin\u002Freplicate.json \\\n  -F \"cmd=Activate\" \\\n  -F \"path=\u002Fcontent\u002Fmysite\u002Fen\u002Fproducts\")\n\nhttp_code=$(echo \"$response\" | tail -n1)\nbody=$(echo \"$response\" | sed '$d')\n\nif [ \"$http_code\" -eq 200 ]; then\n  # Validate JSON response structure and success status\n  if command -v jq &> \u002Fdev\u002Fnull; then\n    success=$(echo \"$body\" | jq -r '.success \u002F\u002F empty')\n    path=$(echo \"$body\" | jq -r '.path \u002F\u002F empty')\n    \n    if [ \"$success\" = \"true\" ]; then\n      echo \"Activation successful for path: $path\"\n    else\n      error=$(echo \"$body\" | jq -r '.message \u002F\u002F \"Unknown error\"')\n      echo \"Activation reported failure: $error\"\n      exit 1\n    fi\n  else\n    echo \"Activation successful (HTTP 200)\"\n    echo \"$body\"\n  fi\nelse\n  echo \"Activation failed with HTTP $http_code\"\n  echo \"$body\"\n  exit 1\nfi\n```\n\n**Deactivate page (with error handling):**\n```bash\n# Note: Replace $AEM_USER:$AEM_PASSWORD with your service account credentials\nresponse=$(curl -s -w \"\\n%{http_code}\" -u $AEM_USER:$AEM_PASSWORD -X POST \\\n  http:\u002F\u002Flocalhost:4502\u002Fbin\u002Freplicate.json \\\n  -F \"cmd=Deactivate\" \\\n  -F \"path=\u002Fcontent\u002Fmysite\u002Fen\u002Fproducts\")\n\nhttp_code=$(echo \"$response\" | tail -n1)\nbody=$(echo \"$response\" | sed '$d')\n\nif [ \"$http_code\" -eq 200 ]; then\n  # Validate JSON response structure and success status\n  if command -v jq &> \u002Fdev\u002Fnull; then\n    success=$(echo \"$body\" | jq -r '.success \u002F\u002F empty')\n    path=$(echo \"$body\" | jq -r '.path \u002F\u002F empty')\n    \n    if [ \"$success\" = \"true\" ]; then\n      echo \"Deactivation successful for path: $path\"\n    else\n      error=$(echo \"$body\" | jq -r '.message \u002F\u002F \"Unknown error\"')\n      echo \"Deactivation reported failure: $error\"\n      exit 1\n    fi\n  else\n    echo \"Deactivation successful (HTTP 200)\"\n    echo \"$body\"\n  fi\nelse\n  echo \"Deactivation failed with HTTP $http_code\"\n  echo \"$body\"\n  exit 1\nfi\n```\n\n**Tree activation via CURL (with error handling):**\n```bash\n# Note: Replace $AEM_USER:$AEM_PASSWORD with your service account credentials\nresponse=$(curl -s -w \"\\n%{http_code}\" -u $AEM_USER:$AEM_PASSWORD -X POST \\\n  http:\u002F\u002Flocalhost:4502\u002Fetc\u002Freplication\u002Ftreeactivation.html \\\n  -F \"path=\u002Fcontent\u002Fmysite\u002Fen\" \\\n  -F \"onlyModified=true\")\n\nhttp_code=$(echo \"$response\" | tail -n1)\nbody=$(echo \"$response\" | sed '$d')\n\nif [ \"$http_code\" -eq 200 ]; then\n  # Note: Tree activation returns HTML, not JSON\n  # Check for success indicators in HTML response\n  if echo \"$body\" | grep -q \"successfully\"; then\n    echo \"Tree activation initiated successfully\"\n    # Extract and display any useful information from the HTML response\n    if command -v jq &> \u002Fdev\u002Fnull && echo \"$body\" | jq empty 2>\u002Fdev\u002Fnull; then\n      # If response is JSON (rare but possible)\n      status=$(echo \"$body\" | jq -r '.status \u002F\u002F \"initiated\"')\n      echo \"Status: $status\"\n    fi\n  else\n    echo \"Tree activation may have encountered issues. Check response:\"\n    echo \"$body\"\n  fi\nelse\n  echo \"Tree activation failed with HTTP $http_code\"\n  echo \"$body\"\n  exit 1\nfi\n```\n\n**Simple examples (without error handling):**\n\nFor quick testing, you can use simpler commands:\n```bash\n# Quick activate (no error handling)\ncurl -u $AEM_USER:$AEM_PASSWORD -X POST \\\n  http:\u002F\u002Flocalhost:4502\u002Fbin\u002Freplicate.json \\\n  -F \"cmd=Activate\" \\\n  -F \"path=\u002Fcontent\u002Fmysite\u002Fen\u002Fproducts\"\n\n# Quick deactivate (no error handling)\ncurl -u $AEM_USER:$AEM_PASSWORD -X POST \\\n  http:\u002F\u002Flocalhost:4502\u002Fbin\u002Freplicate.json \\\n  -F \"cmd=Deactivate\" \\\n  -F \"path=\u002Fcontent\u002Fmysite\u002Fen\u002Fproducts\"\n```\n\nNote: Simple examples above don't check for errors - use error handling versions in production scripts.\n\n## Asset Replication (DAM)\n\nReplicate digital assets from Author to Publish.\n\n### Steps:\n\n1. **Navigate to Assets console:**\n   ```\n   http:\u002F\u002Flocalhost:4502\u002Fassets.html\u002Fcontent\u002Fdam\n   ```\n\n2. **Select asset(s):**\n   - Click checkbox on images, videos, documents\n   - Multiple selection supported\n\n3. **Click \"Quick Publish\" or \"Manage Publication\":**\n   - Same options as page replication\n   - Assets replicate to Publish DAM\n\n4. **Verify asset renditions:**\n   - Original asset replicates\n   - All renditions replicate (thumbnails, web-optimized, etc.)\n   - Metadata replicates\n\n### Asset Replication Considerations:\n\n**Large file handling:**\n- Binary-less replication available for shared datastore\n- Direct binary access reduces replication overhead\n- Configure in replication agent: Serialization Type = Binary-less\n\n**Asset dependencies:**\n- Replicate referenced assets when publishing pages\n- Use \"Include References\" in Manage Publication\n- Avoids broken image links on Publish\n\n## Deactivation (Unpublishing)\n\nRemove content from Publish instances.\n\n### Quick Unpublish:\n\n```\nSites console → Select page(s) → Quick Unpublish\n```\n\n### Manage Publication (Unpublish):\n\n```\nSites console → Select page(s) → Manage Publication\nAction: Unpublish\nScope: Selected \u002F Include children\nClick \"Unpublish\"\n```\n\n### Effect of Deactivation:\n- Content removed from Publish instances\n- URLs return 404 on Publish\n- Content remains on Author (not deleted)\n- Can be re-activated later\n- Dispatcher cache invalidated\n\n## Monitoring Replication Status\n\n### Check Page Replication Status:\n\n**Sites console:**\n- Green checkmark = Published\n- Gray circle = Never published\n- Orange dot = Modified since last publish\n- Timeline shows replication history\n\n**Page Properties:**\n- Click page → Properties → Basic tab\n- Shows: Last published, Last published by, Last modified\n\n### Replication Queue Status:\n\n```\nNavigate to: Tools → Deployment → Replication\nClick: Agents on author\nSelect: [agent name]\n\nView:\n- Queue status (idle\u002Factive\u002Fblocked)\n- Pending items count\n- Last replication timestamp\n```\n\n### Replication Logs:\n\n```\nNavigate to: Tools → Operations → Logs\n\nLog file: replication.log\nLocation: crx-quickstart\u002Flogs\u002Freplication.log\n\nTypical entries:\n- Replication initiated: path, type, user\n- Replication succeeded\u002Ffailed: status, duration\n- Queue events: item added, processed, failed\n```\n\n## Troubleshooting Replication\n\n### Content Not Appearing on Publish\n\n**Check replication status:**\n1. Verify page shows \"Published\" in Sites console\n2. Check replication timestamp is recent\n3. Review replication agent queue (should be empty after processing)\n\n**Verify on Publish directly:**\n```\nhttp:\u002F\u002Fpublish-host:4503\u002Fcontent\u002Fmysite\u002Fen\u002Fpage-name.html\n```\n\n**Check Dispatcher cache:**\n- May serve cached old version\n- Wait for cache invalidation\n- Or manually flush cache\n- Verify Dispatcher Flush agent is enabled and working\n\n### Replication Fails\n\n**Common causes:**\n\n1. **Replication agent blocked:**\n   - Check agent status (should be green)\n   - Review queue for failed items\n   - Click \"Force Retry\" or \"Clear\" failed item\n\n2. **Publish instance unavailable:**\n   - Verify Publish is running: `http:\u002F\u002Fpublish:4503\u002Fsystem\u002Fconsole`\n   - Test agent connection\n   - Check network connectivity\n\n3. **Insufficient permissions:**\n   - Verify Agent User Id has replication privileges\n   - Check user permissions on target content paths\n   - Review error logs for permission denied messages\n\n4. **Content locked:**\n   - Check if page is locked by another user\n   - Unlock page: Page → Unlock\n   - Retry replication\n\n### Page Modified After Publication\n\nIf page shows orange dot (modified since publish):\n\n```\nOption 1: Re-publish changes\nSelect page → Quick Publish\n\nOption 2: Review changes first\nSelect page → Manage Publication\nCheck \"Modified\" scope to see what changed\nProceed with publication\n```\n\n## Best Practices\n\n1. **Use appropriate method:**\n   - Quick Publish for simple single-page updates\n   - Manage Publication for complex scenarios\n   - Tree Activation for entire sections\n   - Workflows for approval processes\n\n2. **Verify before publishing:**\n   - Preview content in Author\n   - Use staging\u002FUAT environment first\n   - Test with limited user group before full launch\n\n3. **Monitor replication:**\n   - Check replication status after activation\n   - Verify content appears correctly on Publish\n   - Review logs for errors\n\n4. **Schedule large activations:**\n   - Use off-peak hours for tree activations\n   - Avoid business hours for major content releases\n   - Coordinate with operations team\n\n5. **Handle dependencies:**\n   - Always publish referenced assets\n   - Use \"Include References\" option\n   - Verify asset paths are correct\n\n6. **Use workflows for sensitive content:**\n   - Implement approval for homepage, legal pages\n   - Multi-stage review for compliance\n   - Audit trail via workflow history\n\n7. **Clean up deactivated content:**\n   - Regularly review unpublished pages\n   - Delete obsolete content from Author\n   - Maintain organized content tree\n\n8. **Test replication agents:**\n   - Periodically test agent connectivity\n   - Verify multiple Publish instances receiving content\n   - Monitor agent performance metrics\n\n## Security Considerations\n\n**Replication permissions:**\n- Grant minimum required activation rights\n- Use groups for permission management\n- Audit replication activity via logs\n\n**Sensitive content:**\n- Use workflows for approval\n- Restrict activation to authorized users\n- Implement content security policies\n\n**API usage:**\n- Secure service user accounts for programmatic replication\n- Never hardcode credentials\n- Use resource resolver with appropriate permissions\n\n## Related Skills\n\n- `configure-replication-agent`: Set up and configure replication agents\n- `troubleshoot-replication`: Diagnose and fix replication issues\n- For AEM as a Cloud Service, see content distribution documentation (different architecture)\n\n## Success Criteria\n\n- ✓ Content successfully published to Publish instance(s)\n- ✓ Page status shows \"Published\" with green checkmark\n- ✓ Content visible on Publish URL\n- ✓ Replication agent queue processed without errors\n- ✓ Referenced assets also published\n- ✓ Dispatcher cache invalidated (if applicable)\n- ✓ Scheduled activation configured correctly (if used)\n- ✓ Workflow approval completed (if required)\n- ✓ Deactivation removes content from Publish (if tested)\n- ✓ Replication logs show successful entries\n\n## Additional Resources\n\n- [Official AEM 6.5 LTS Replication Documentation](https:\u002F\u002Fexperienceleague.adobe.com\u002Fen\u002Fdocs\u002Fexperience-manager-65-lts\u002Fcontent\u002Fimplementing\u002Fdeploying\u002Fconfiguring\u002Freplication)\n- [AEM 6.5 LTS Replication Troubleshooting Guide](https:\u002F\u002Fexperienceleague.adobe.com\u002Fen\u002Fdocs\u002Fexperience-manager-65-lts\u002Fcontent\u002Fimplementing\u002Fdeploying\u002Fconfiguring\u002Ftroubleshoot-rep)\n- [AEM 6.5 LTS Documentation Hub](https:\u002F\u002Fexperienceleague.adobe.com\u002Fen\u002Fdocs\u002Fexperience-manager-65-lts)\n- [Replication API JavaDoc (Package Summary)](https:\u002F\u002Fdeveloper.adobe.com\u002Fexperience-manager\u002Freference-materials\u002F6-5-lts\u002Fjavadoc\u002Fcom\u002Fday\u002Fcq\u002Freplication\u002Fpackage-summary.html)\n- [Managing Publications Documentation](https:\u002F\u002Fexperienceleague.adobe.com\u002Fdocs\u002Fexperience-manager-65\u002Fauthoring\u002Fauthoring\u002Fpublishing-pages.html)\n- Workflow Models documentation for approval processes\n",{"name":5,"license":15,"description":7},"main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fadobe-aem-replication\u002Freplicate-content","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kalash33\u002Fkstack --skill replicate-content",{"tool":38,"command":39},"bunx","bunx skills add kalash33\u002Fkstack --skill replicate-content",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill replicate-content","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-replication\u002Freplicate-content\u002FSKILL.md",true,[],[47,55,62,69,76,83],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]