Configure Multi Site Management


MSM - Multi Site Management is a configurable framework for automating content deployment. It works on Language master and blueprint model. 

 Let's discuss about how MSM Rollout configuration works.

 Step 1: Go to site landing page Properties where Blueprint and Live Copy tabs are a part of dialog. Language master will have Blueprint active tab and Live Copy tab disabled.


Step 2: Go to Tools section and navigate to MSM folder. Roll out Configurations are done here.


Step 3: Open any Rollout Config and edit settings.It will have synchronization trigger based on drop down selection which is on rollout of page, on modification of content, on page activation and on page deactivation.


Step 4: Set up MSM Control center. Under tools section, select MSM Control Center folder where blueprint being set up.


.
Step 5: Set up blueprint for language master.Select root path of language master from where content needs to be rollout.



Step 6: Open Control Center to see list of configured live copies from language master.


Step 7:Validate current status of live copies.


Step 8: Open Live copy landing page properties, it will have Blueprint tab disabled and Live Copy tab active. Here again rollout configuration can be seen.





Step 9: Read more about AEM MSM Best Practices and Customization of Rollout actions.

 https://docs.adobe.com/docs/en/aem/6-2/administer/sites/msm/best-practices.html

Comments

Post a Comment

Popular posts from this blog

AEM 6.3 | Apache Sling Content Disposition Filter | Hosting Static HTML in JCR

Image
In AEM 6.2 and 6.3, when we attempt to hit the static content such as (/content/site/static-page.html), it is treated as a binary download and does the same for all other file types(pdf,css, js, images) where r esponse header shows Content-Disposition as an attachment. In previous versions of AEM (6.1 and below),  com.day.cq.dam.core.impl.servlet.SafeBinaryGetServlet  was there to control response header to render page instead of download.  However from 6.2, this component is  deprecated and t he reason is Apache Sling Content Disposition Filter(org.apache.sling.security.impl.ContentDispositionFilter) took precedence and an intended change made in product from AEM 6.2 onward and was introduced as part of Sling Security Fix. Here we have steps to render static pages: Apache Sling Content Disposition Filter Configuration where static files needs to be added to meet requirements. Configuration can be reverted back to render static pages without adding it manually in OSGI by u
Read more

Image Component Customization - Image Size Restriction - Drag/Drop - Touch UI

Image
Customization of Image component or file upload resource type drag and drop from content/asset finder and restrict it to 1 MB or to any size. Step 1 : Create a AEM Image Component or use file upload resource type to drag and drop images in Touch UI dialog. Step 2 : Create Client library in your project application structure or inside component. Use categories as  cq.authoring.dialog or add extra clientlibs as needed . Step 3: Create a js file and add below piece of code which talks about file upload functions and accommodate for drag and drop behavior for coral classes from Content/Asset finder. As the page div for drag and drop creates on run time and becomes messy to retrieve the image size, hence a ajax call is used to get the image size post adapting resource to Asset. (function($, $document, ns) {     var FILE_UPLOAD_SELECTOR = ".cq-dialog .cq-FileUpload"; function imageSizeValidation(widget, elementName, imageSize, operation) {         if (widget &
Read more

Access OSGI ser­vice from Sightly WCMUsePojo | AEM 6.3

Create AEM 6.3 component making use of WCMUsePojo accessing OSGI Service. Step 1:  Create an interface name  OSGITestInterface.java  that will be implemented by service impl. public interface OSGITestInterface { String getOSGIName(); String getOSGIDesc(); String getOSGIuse(); String getOSGIData();  } Step 2:  Create a Interface Implementation class name  OSGITestInterfaceImpl.java import org.slf4j.Logger; import org.slf4j.LoggerFactory; import org.apache.felix.scr.annotations.Component; import org.apache.felix.scr.annotations.Service; @Component @Service public class OSGITestInterfaceImpl implements OSGITestInterface { Logger logger = LoggerFactory.getLogger(OSGITestInterfaceImpl.class); @Override public String getOSGIName() { return "Test Service"; } @Override public String getOSGIDesc() { return "AEM OSGI Service"; } @Override public String getOSGIuse() { return "OSGI Service data"; }        
Read more