MSM is a configurable framework for automating content deployment. Implementations often involve major portions of a website and span organizations and geographies. It is therefore highly recommended to plan MSM implementations as carefully as you plan your website:
Carefully plan structure and content flows before starting implementation.
Customize as much as necessary, but as little as possible. While MSM supports a high degree of customization (e.g. rollout configurations) typically the best practice for the performance, reliability and upgradeability of your website is to minimize customization.
Establish a governance model early, and train users accordingly, to ensure success. A best practice from a governance point of view is to minimize the authority that local content producers have to allocate/connect content to other local users and their respective live copies. This is because un-governed, chained inheritances can significantly increase the complexity of a MSM structure and compromise its performance and reliability.
Once a plan exists for your structure, content flows, automation and governance - prototype and thoroughly test your system, before starting live implementation.
Keep in mind that Adobe Consulting and leading System Integrators have deep experience planning and implementing content automation with MSM, so they can help you both get started with your MSM project and throughout its entire implementation.
The additional benefits of using a blueprint configuration are that they:
In the case that a blueprint configuration is not referenced, rollouts can only be initiated from the live copies themselves, essentially pulling content from source.
When creating a new site with live copy, it is advantageous to create blueprint configurations to ensure the availability of the full MSM feature set.
CUG groups cannot be rolled out to Live Copies from Blueprints. Please plan around this when configuring Live Copy.
In general, the rollout rule in MSM regarding the synchronization of components is:
This means that components are treated as an aggregate, and in a rollout the component itself and all its children are replaced with those in the blueprints. This means that if a resource is added to such a component locally, it will be lost to the content of the blueprint at rollout.
To support the nesting of components such that locally added components are maintained in a rollout, the component must be declared as a container. As an example, the default parsys is declared as a container so it can support locally-added content.
Add the property
cq:isContainer to the component to designate it as a container.
Notice that AEM has two main approaches for creating live copies:
When creating a Live Copy
This can be considered as the more generic approach, allowing you to create live copies from any page. The content structure of a live copy exactly matches the source.
When creating a Site
This is a more specialized approach, primarily for creating websites with a multilingual structure.
Following are a few considerations to keep in mind when creating a site:
To create a new site, you need a blueprint configuration.
To allow the selection of language paths to create in a new site, the corresponding language roots must exist in the blueprint (source).
Once a new site has been created as a live copy (using Create, then Site), the first two levels of this live copy are shallow. Children of the page do not belong to the live-relationship, but a roll-out will still descend if a live-relationship that matches the trigger is found.
It helps avoid:
MSM can assist in the creation of multilingual websites in two ways:
When creating language masters.
While MSM itself does not provide content translation, it can be integrated with third-party translation connectors that do. Please note that:
MSM allows you to cancel inheritance at the page- and/or component- level. This helps prevent overwriting translated content (from a live copy, with not-yet-translated content from a blueprint) on the next rollout.
Some third-party translation connectors automate this management of MSM inheritances.
Please check with your translation service provider for more information.
An alternative approach for creating and translating language masters is to use language copies in conjunction with AEM’s out-of-the-box translation integration framework.
When rolling out content from language masters.
Modifications to the content structure in a blueprint/source tree are reflected differently in a live copy. This is dependent on the modification type:
Creating new pages in a blueprint will result in corresponding pages being created in live copies after rollout with the standard rollout configuration.
Deleting pages in a blueprint will result in corresponding pages being deleted from live copies after rollout with standard rollout configuration.
Moving pages in a blueprint will not result in corresponding pages being moved in live copies after rollout with standard rollout configuration:
This will work only with the On Rollout trigger.
Create a custom rollout configuration:
This new configuration must include the action:
Do not add other actions to this configuration.
Position the new configuration:
To fully roll out the page move, while deleting respective pages at their old location in the live copy:
Position the newly created configuration before the standard rollout configuration.
The standard rollout configuration will take care of deleting the pages in their old location.
To roll out the page move while keeping respective pages in their old location in the live copies (essentially duplicating the content):
Position the newly created configuration after the standard rollout configuration.
This will ensure no content is deleted in the live copy or deactivated from publish.
MSM rollout configurations are highly customizable. You should be aware that automating rollouts can have far reaching consequences. As a best practice, you should plan very carefully before, for example:
When using the rollout trigger
onModify you should consider that:
Automating rollouts with
onModify triggers may have a negative impact on authoring performance as they trigger rollouts after every page modification.
The rollout result may differ from the one expected as:
Using such a rollout configuration could lead to commit conflicts if concurrent updates of the same resource occur.
Therefore, it is recommended that you only use
onModify triggers if the benefits of automatic rollout initiation outweigh any potential performance issues.
This and the following pages cover the related issues: