Copy this content to, and re-use this content in, other areas (live copies) of the same or other sites.

MSM then maintains the (live) relationships between your source content and its live copies so that:

When you make changes to the source content, the source and live copies are synchronized (to apply these changes to the live copies too).

You can make adjustments to the content of the live copies by disconnecting the live relationship for individual sub pages and/or components. By doing this, changes to the source will no longer be applied to the live copy.

Possible Scenarios

There are many use-cases for MSM and live copies, some scenerios include:

Multinationals - Global to Local Company

One typical use case that MSM supports is to reuse content in several multinational same-language sites. This allows the core content to be re-used, while allowing for national variations.

For example, the English section of the We.Retail Reference Site sample is created for customers in the USA. Most of the content in this site can also be used for other We.Retail sites that cater to English-speaking customers of different countries and cultures. The core content remains the same over all sites, while regional adjustments can be made.

The following structure can be used for sites for the United States, United Kingdom, Canada, and Australia:

Alternatively a company with a network of dealers might want separate websites for their individual dealerships - each being a variation of the main site provided by the head-office. This might be for a single company with multiple regional offices, or a national franchise system comprised of a central franchisor and multiple local franchisees.

The head office can supply the core information, whereas the regional entities can add local information, such as contact details, opening hours and events.

Or you can use MSM to create versions of a specific sub-branch, For example, a support sub-site holding details of the different versions of a specific product, where the base information remains constant and only the updated features need to be changed:

In such a scenario there is always the question of whether to make a straightforward copy or use live copies.

There is a balance of:

How much of the core content will need updating over the multiple versions.

Against:

How much of the individual copies will need to be adjusted.

MSM from the UI

MSM is directly accessible in the UI using various options from the appropriate console. To provide an introduction the following lists the main locations:

Create Site (Sites)

MSM helps you to manage multiple websites that share common content; for example, websites are often provided for international audiences such that most of the content is common across all countries, with a subset of the content specfic to each individual country. MSM allows you to create live copies that automatically update one or more sites based on your source site. This also helps you to enforce a common base structure, use the common content across the multiple sites, maintain a common look and feel and focus efforts on managing the content that actually differs between the sites.

Live Copies

An MSM live copy is a copy of specific site content for which a live relationship with the original source is maintained:

The live copy inherits content from its source.

Synchronization performs the actual transfer of content when changes are made to the source.

A live copy can be considered as either:

Shallow: a single page

Deep: the page, together with its child pages

Synchronization rules, called rollout configurations, determine which properties are synchronized and when the sychronization occurs.

In the previous example, /content/we-retail/language-masters/en is the global master site in English. To reuse the content of this site, MSM live copies are created:

The content below /content/we-retail/language-masters/en is the source.

The content below /content/we-retail/language-masters/en is copied below the /content/we-retail/us/en/, /content/we-retail/gb/en, /content/we-retail/ca/en, and /content/we-retail/au/en nodes. These are the live copies.

Live Copies - Composition

Huomautus:

The diagrams and descriptions in this section represent snapshots of potential live copies. They are not comprehensive, but provide an overview to highlight specific characteristics.

When you initially create a live copy, the selected source pages are reflected on a 1:1 basis in the live copy. After this, new resources (pages and/or paragraphs) can also be created directly within the live copy, so it is useful to be aware of these variations and how they impact synchronization. Possible compositions include:

Live Copy with non-Live-Copy pages

When you create a live copy in AEM you can see and navigate through the live copy branch - and use normal AEM functionality on the live copy branch. This means that you (or a process) can create new resources (pages and/or paragraphs) inside the live copy branch (e.g. myCanadaOnlyProduct).

Such resources have no live relationship to the source/blueprint pages and are not synchronized.

Scenarios can occur that MSM handles as special cases. For example, when you (or a process) create a page with the same position and name in both the source/blueprint and live copy branches. For such situations see MSM Rollout Conflicts for more information.

Nested Live Copies

When you (or a process) create a new page within an existing live copy this new page can also be set up as a live copy of a different blueprint. This is known as a Nested Live Copy, here the behavior of the second (inner) live copy is affected by the first (outer) live copy in the following way:

A deep rollout triggered for the top-level live copy can be continued into the nested live copy (for example, if the trigger matches).

Any links between the sources will be rewritten within the live copies.
For example, links from the second to the first blueprint will be rewritten as links from the nested/second live copy to the first live copy.

Huomautus:

If you move/rename a page within the live copy branch then (internally) this will be treated as a nested live copy to enable AEM to track the relationships.

Stacked Live Copies

A live copy is known as a Stacked Live Copy when it is created as the child of a shallow live copy. It behaves in the same manner as a Nested Live Copy.

Source, Blueprints and Blueprint Configurations

Any page or branch of pages can be used as the source of a live copy.

However, MSM also allows you to define a blueprint configuration that specifies a source path. The benefits of using a blueprint configuration are that they:

Allow the author to use the Rollout option on a blueprint - to (explicitly) push modifications to live copies that inherit from this blueprint.

Allow the author to use Create Site; this allows the user to easily select languages and configure the structure of the live copy.

Define a default rollout configuration for live copies that have a relationship with the blueprint.

The source for a live copy can be either regular pages or pages encompassed by a blueprint configuration - both are valid use cases.

The source forms the blueprint for the live copy. The blueprint is defined when you either:

When authoring a blueprint page you can use the Rollout command to push changes to the live copy.

The Rollout command is available on a blueprint page that is referenced by a blueprint configuration.

When authoring a live copy page you can use the Synchronize command to pull changes from the source to the live copy.

The Synchronize command is always available on the live copy page (regardless of whether the source/blueprint page is encompassed by a blueprint configuration).

Rollout Configurations

A rollout configuration defines when and how a live copy is synchronized with the source content. A rollout configuration consists of a trigger and one or more synchronization actions:

Trigger

A trigger is an event that causes the live action synchronization to occur, such as the activation of a source page. MSM defines the triggers that you can use.

Synchronization actions

Are performed on the live copy to synchronize it with the source. Example actions are copying content, ordering child nodes, and activating the live copy page. MSM provides a number of synchronzation actions.

Huomautus:

You can create custom actions for your instance using the Java API.

Rollout configurations can be re-used, so that more than one live copy can use the same rollout configuration. Several rollout configurations are included in a standard installation.

Rollout Conflicts

Rollouts can become complicated, especially when authors are editing content in both the source and the live copy, so it is useful to be aware of how AEM handles any conflicts that might occur during rollout.

Suspending and Cancelling Inheritance and Synchronization

Each page and component in a live copy is associated with its source page and component via a live relationship. The live relationship configures the synchronization of live copy content from the source.

You can Suspend the live copy inheritance for a live copy page so that you can change page properties and components. When you suspend inheritance, the page properties and components are no longer synchronized with the source.

When editing an individual page, authors can Cancel Inheritance for a component. When inheritance is cancelled, the live relationship is suspended and synchronization does not occur for that component. Cancelling inheritance and synchronization is useful when sub-sections of the content needs to be customized.

Detaching a Live Copy

Detach permanently removes the live relationship between a live copy and its blueprint page. All MSM-relevant properties are removed from the live copy and the live copy pages become a standalone copy.

Customizing MSM

MSM provides tools so that your implementation can adapt to the exceptional complexities that can exist when sharing content:

Custom Rollout ConfigurationsCreate a rollout configuration when the installed rollout configurations do not meet your requirements. You can use any available rollout trigger and synchronization action.