1.2 Multi-Site Management (MSM) & Blueprint/Live Copy Architecture

1.2 Multi-Site Management (MSM) & Blueprint/Live Copy Architecture

Quick Answer: Multi-Site Management (MSM) automates the replication of content hierarchies from source Blueprints to target Live Copies. Live relationships are maintained at page and component levels via cq:LiveRelationship and cq:LiveSyncConfig. Authors can cancel inheritance locally on components, but re-enabling inheritance and performing a rollout overwrites local edits. For global sites, Adobe best practice pairs Language Copies (one-time translated content in Language Masters) with Live Copies (regional sites inheriting layout and shared assets from those masters).

Large enterprises operating global digital footprints face a dual imperative: maintaining centralized brand consistency across hundreds of localized websites while empowering regional marketing teams to customize content for local markets, legal requirements, and languages. Adobe Experience Manager resolves this challenge through Multi-Site Management (MSM) and its foundational Blueprint and Live Copy architecture.

---

MSM Core Concepts & JCR Architecture

MSM establishes a formal parent-to-child synchronization relationship between a master content repository branch and one or more localized target sites. This architecture applies not only to web pages (cq:Page) under /content but also to Experience Fragments (/content/experience-fragments), allowing modular UI components to be managed across sites.

The Anatomy of Blueprints and Live Copies

• Blueprint: A master content tree explicitly registered in AEM (via the Blueprint Console or /apps/msm/blueprint/config) that serves as the source of truth for downstream sites. For example: /content/wknd/language-masters/en.
• Live Copy: A target content tree generated from a Blueprint or an existing site. The Live Copy maintains an ongoing technical relationship with its source, allowing updates to be rolled out across the hierarchy.

JCR Structure of a Live Copy

Behind the scenes, MSM is driven by specialized JCR node types, mixins, and child nodes:

/content/wknd/us/en (cq:Page)
  └── jcr:content (cq:PageContent, mixin: cq:LiveSync, mixin: cq:LiveRelationship)
        ├── cq:LiveSyncConfig (cq:LiveSyncConfig)
        │     ├── cq:master = "/content/wknd/language-masters/en"
        │     ├── cq:rolloutConfigs = ["/libs/msm/wcm/rolloutconfigs/default"]
        │     └── cq:isDeep = true
        └── root (nt:unstructured)
              └── responsivegrid
                    └── teaser (nt:unstructured, mixin: cq:LiveRelationship)
                          ├── jcr:title = "Global Promotion"
                          └── cq:propertyInheritanceCancelled = ["jcr:title"]

• cq:LiveRelationship: A mixin applied to every page jcr:content node and individual component node that is actively tracked by MSM.
• cq:LiveSyncConfig: A configuration node stored directly under the Live Copy root's jcr:content. It defines the path to the master blueprint (cq:master), the bound rollout configurations (cq:rolloutConfigs), and whether child pages are included (cq:isDeep = true).
• cq:propertyInheritanceCancelled: A multi-value string property added to a component when a local author cancels inheritance on specific fields (such as jcr:title), recording exactly which attributes are detached from the blueprint.

---

Deep vs. Shallow Live Copies

When creating a Live Copy, an administrator must choose between two structural scopes:

---

Rollout Configurations and Triggers

A Rollout Configuration controls when synchronization occurs and what actions are executed during that synchronization. Rollout configurations are defined under /libs/msm/wcm/rolloutconfigs (system) or /apps/msm/wcm/rolloutconfigs (custom).

Standard Rollout Configurations & Triggers

Every rollout configuration binds a specific Trigger to a sequence of Live Actions:

Exam Trap: Be cautious with pushonmodify in large enterprise environments. If a Blueprint has 60 Live Copies, editing a single component fires 60 concurrent JCR write events. In production, this can degrade author instance performance. Standard manual rollout is generally preferred for large-scale multi-site architectures.

Core Live Actions

Live Actions are OSGi services implementing the LiveAction interface that execute the actual content synchronization:

• contentCopy: Creates new child pages and components in the Live Copy if they exist in the Blueprint.
• contentUpdate: Updates properties, text, and asset references on existing Live Copy pages and components.
• contentDelete: Removes pages or components in the Live Copy if they have been deleted from the Blueprint.
• orderChildren: Reorders sibling pages and component nodes in the Live Copy to match the exact sequence in the Blueprint.
• editProperties: Handles property inheritance exclusions based on configured rollout rules.

---

Inheritance Management: Cancellation & Re-synchronization

A core strength of MSM is granular inheritance management. Regional authors can override global content where necessary while maintaining synchronization across the rest of the page.

Component-Level Inheritance Lifecycle

1. Inherited State (Locked): When a Live Copy is created, every component displays a green lock icon in the Touch UI. The component is read-only for local authors. Properties match the Blueprint.
2. Canceling Inheritance (Unlocked): To localize text or imagery, the regional author clicks the component toolbar lock icon and selects Cancel Inheritance. The lock turns into an open padlock. AEM adds the cq:propertyInheritanceCancelled property to the component node. The author can now edit and save local content.
3. Rollout Behavior While Unlocked: When a central author rolls out changes from the Blueprint, the contentUpdate action skips the unlocked component. The local edits remain intact.
4. Re-enabling Inheritance: If the regional team later decides to align with the global brand, an author clicks the open padlock and chooses Re-enable Inheritance.

Critical Exam Scenario: Re-enabling inheritance does not instantly overwrite local content in the UI. Instead, it re-attaches the live relationship (cq:propertyInheritanceCancelled is removed). The local content is completely overwritten upon the very next rollout from the Blueprint. If an author re-enables inheritance and triggers a rollout, all local modifications are permanently replaced by Blueprint values.

Global Multi-Site Architecture: Language Copies vs. Live Copies

A frequent area of confusion on the AD0-E128 exam is the distinction between Language Copies and Live Copies.

Core Architectural Differences

Adobe Recommended Global Site Hierarchy

To build a scalable, multi-national web presence, Adobe recommends decoupling translation from regional live synchronization using a Language Masters pattern:

/content/mybrand/
  ├── language-masters/              <-- Central Translation Hub (No Live Relationship)
  │     ├── en/                      <-- Global English Master (Reference Language)
  │     ├── fr/                      <-- French Language Copy (Translated from en)
  │     ├── de/                      <-- German Language Copy (Translated from en)
  │     └── es/                      <-- Spanish Language Copy (Translated from en)
  │
  ├── us/                            <-- Regional Country Site: United States
  │     └── en/                      <-- Live Copy of /language-masters/en
  │
  ├── ca/                            <-- Regional Country Site: Canada (Bilingual)
  │     ├── en/                      <-- Live Copy of /language-masters/en
  │     └── fr/                      <-- Live Copy of /language-masters/fr
  │
  └── ch/                            <-- Regional Country Site: Switzerland (Multilingual)
        ├── de/                      <-- Live Copy of /language-masters/de
        └── fr/                      <-- Live Copy of /language-masters/fr

Operational Workflow

1. Content Authoring: Global authors create new master content in /content/mybrand/language-masters/en.
2. Translation Framework: Authors initiate an AEM Translation Project to create or update Language Copies (/language-masters/fr, /language-masters/es). Machine or human translation workflows populate the translated language roots. There is no live copy relationship between /en and /fr.
3. Regional Rollout: Regional sites (e.g., /content/mybrand/ca/en and /content/mybrand/ca/fr) are created as Live Copies connected to their respective language masters. When changes in the language master are rolled out, they cascade down to the country sites while preserving local component customizations.

This architecture ensures that translation is executed once per language rather than once per country, dramatically reducing translation costs while retaining full local authoring flexibility.