Multi Site Manager (MSM) functionality in Adobe Experience Manager (AEM) enables users to reuse content that is authored once and reused across multiple web-locations. The same is available for digital assets as MSM for Assets functionality. Using MSM for Assets, you can:
To use MSM for Assets, install at least Service Pack 5. For more information, see the release notes.
To understand the usage scenarios for reusing same content (text and assets) across multiple web-locations, see possible MSM scenarios. AEM maintains a link between the original asset and its linked copies, called as live copies (LCs). The maintained linking allows centralized changes to be pushed to many live copies. This allows for faster updates while doing away with the limitations of managing duplicate copies. The propagation of changes is error-free and centralized. The functionality allows room for updates that are limited to selected live copies. Users can detach the linking, that is break inheritance, and make local edits that are not overwritten when next time the primary copy is updated and changes are rolled out. The detaching can be done for a few select metadata fields or for an entire asset. It allows for flexibility to locally update assets that are originally inherited from a primary copy.
MSM maintains a live relationship between the source asset and its live copies so that:
Changes to the source assets are applied (rolled out) to live copies as well, that is the live copies are synchronized with the source.
You can update the live copies by suspending the live relationship or remove the inheritance for a few limited fields. The modifications to the source are no longer applied to the live copy.
Source: The original assets or folders. Primary copy from which live copies are derived.
Live copy: The copy of the source assets/folders that is in synchronization with its source. Live copies can be a source of further live copies. See how to create LCs.
Inheritance: A link/reference between a live copy asset/folder and its source that the system uses to remember where to send the updates. Inheritance exists at a granular level for metadata fields. Inheritance can be removed for selective metadata fields while preserving the live relationship between source and its live copy.
Rollout: An action that pushes the modifications made to the source downstream to its live copies. It is possible to update one or more live copies in one go using rollout action. See rollout.
Rollout config: Rules that determine which properties are synchronized, how and when. These configurations are applied when creating live copies; can be edited later; and a child can inherit rollout configuration from its parent asset. For MSM for Assets, use only the Standard rollout config. The other rollout configurations are not available for MSM for Assets.
Synchronize: Another action, in addition to rollout, that brings parity between source and its live copy by sending the updates from source to live copies. A sync is initiated for a particular live copy and the action pulls the changes from the source. Using this action, is possible to only update one of the live copies. See synchronize action.
Suspend: Temporarily remove the live relationship between a live copy and its source asset/folder. You can resume the relationship. See suspend action.
Resume: Resume the live relationship so that a live copy again starts receiving the updates from source. See resume action.
Reset: Reset action makes the live copy again a replica of the source by overwriting any local changes. It also removes inheritance cancellations and resets inheritance on all metadata fields. To make local modifications in the future, you must again cancel the inheritance of specific fields. See local modifications to LC.
Detach: Irrevocably remove the live relationship of a live copy asset/folder. After detach action, the live copies can never receive updates from source and it stops being a live copy anymore. See remove relationship.
To create live copy from one or more source assets or folders, follow either of the following:
You can create live copies of an asset or a folder one at a time. You can create live copies that are derived from an asset or a folder that is a live copy itself.
Content Fragments (CFs) are not supported for the use case. When attempting to create their live copies, CFs are copied over as is without any relationship. The copied CFs are a snapshot in time and does not update when original CFs are updated.
To create live copies using the first method, follow these steps:
To create live copies using the second method, follow these steps:
When a source or a live copy is moved, the relationships are retained. When a live copy is deleted, the relationships are removed.
You can view the information and MSM-related statuses of live copy such as relationship, synchronization, rollouts, and more from the various areas of the AEM user interface. The following two methods work for assets and folders:
To check the status of a few separate live copies, use the first method that is see the Properties page. To check statuses of many live copies, use the second method, that is, see Relationship Status page.
To check the information and statuses of a live copy asset or a folder, follow these steps.
AEM provides a console to check the statues of all the live copies of a source folder. This console displays the status of all child assets.
You can quickly see the statuses of live copies of other folders without having to browse too much. Just change the folder in the pop-up list in the upper middle part of the Live Copy Overview interface.
For a source asset or folder, you can see the following information and take the following actions directly from the References rail:
Select the source asset or folder, open the left rail, and click References. Alternatively, select an asset or folder and use the keyboard shortcut
Alt + 4.
For a specific live copy, click Edit Live Copy to suspend relationship or change rollout configuration.
For a live copy asset or folder, you can see the following information and take the following actions directly from the References rail:
Select a live copy asset or folder, open the left rail, and click References. Alternatively, select an asset or folder and use the keyboard shortcut
Alt + 4.
After a source is modified the changes can be propagated to the live copies using either a synchronize action or a rollout action. To understand the difference between both the actions, see glossary.
You can initiate a rollout action from the source asset and update all or a few select live copies.
Modifications made in a source asset are rolled out only to the directly related live copies. If a live copy is derived from another live copy, the modifications are not rolled out to the derived live copy.
Alternatively, you can initiate a rollout action from the References rail after selecting a specific live copy. For more information, see Quick actions from References rail for live copy. In this method of rollout, only the selected live copy and optionally its children are updated.
A synchronize action pulls the modifications from a source only to the selected live copy. Sync action respects and maintains the local modifications done after canceling inheritance. The local modifications are not overwritten and the canceled inheritance is not re-established. You can initiate a sync action in three ways.
|Where in AEM interface||When and why to use||How to use|
|References rail||Quickly synchronize when you already have the source selected.||See Quick actions from References rail for source|
|Toolbar in the Properties page||Initiate a sync when you already have the live copy properties open.||See Synchronize a live copy|
|Live Copy Overview console||Quickly synchronize multiple assets (not necessarily all) when source folder is selected or Live Copy Overview console is already open. Sync action is initiated for one asset at a time but is a faster way to do sync for multiple assets in one go.||See Actions on many assets in a live copy folder|
To start a sync action, open Properties page of a live copy, click Live Copy and click the desired action from the toolbar.
To know the statuses and information related to a synchronize action, see Information and statuses of all live copies of a folder.
If the relationship is suspended, the synchronize action is not available in the toolbar. While synchronize action is available in the References rail, the modifications are not propagated even after a reportedly successful rollout.
You can temporarily suspend the relationship to prevent a live copy from receiving modifications made to the source asset or folder. The relationship can also be resumed for live copy to start receiving the modifications from source.
To suspend or resume, open Properties page of a live copy, click Live Copy and click the desired action from the toolbar.
Alternatively, you can quickly suspend or resume relationships of multiple assets in a live copy folder from the Live Copy Overview console. See Take actions on many assets in live copy folders.
A live copy is a replica of the original source when it is created. The metadata values of a live copy are inherited from the source. The metadata fields individually maintain inheritance with the respective fields of the source asset.
However, you have the flexibility to make local modifications to a live copy to change a few select properties. To make local modifications, cancel the inheritance of the desired property. When inheritance of one or more metadata fields is canceled, the live relationship of the asset and the inheritance of the other metadata fields is retained. Any synchronization or rollout does not overwrite the local modifications. To do so, open Properties page of a live copy asset, click cancel inheritance icon next to a metadata field.
You can undo all the local modifications and revert the asset to the state of its source. Reset action irrevocably and instantly overrides all local modifications and re-establishes inheritance on all metadata fields. To revert, from the Properties page of a live copy asset, click Reset from the toolbar.
You can completely remove the relationship between a source and a live copy using Detach action. The live copy becomes a stand-alone asset or folder after it is detached. It is displayed as a new asset in AEM interface, immediately after detaching. To detach a live copy from its source, follow these steps.
The relationship is removed as soon as you click Detach from the dialog. You cannot undo it by clicking Cancel on the Properties page.
Alternatively, you can quickly detach multiple assets in a live copy folder from the Live Copy Overview console. See Take actions on many assets in live copy folders.
If you have multiple assets in a live copy folder, initiating actions on each asset can be tedious. You can quickly initiate the basic actions on many assets from Live Copy Console. The above methods continue to work for individual assets.
AEM allows you to extend the functionality using the MSM Java APIs. For Assets, the extending works just the same as it works with MSM for Site. For details, see Extending the MSM and the following sections for information about specific tasks:
Live copies and sources are assets or folders that can be managed, to a certain extent, as digital assets. Some asset management tasks in AEM have a specific impact on the live copies.
In more scenarios, MSM for Assets matches the behavior of MSM for Sites functionality. Some key differences to note are:
Following are the limitation with MSM for Assets.