AEM Concepts

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

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"; }        

AEM provides content as a service module which can be developed on your local machines.  AEM 6.3 Content Service is a configurable module to provide an view of content within JCR. That content can be assets or pages intended for internal or external use. Uses would typically be  portals, internal or  external web applications within AEM or outside. These are configurable steps. Let us go through this step by step. Step 1: Enable Content Service OSGI config -  AEM Content Services Feature Flag. .   Step 2: Starting Content Service Configuration. http://localhost:4500/aem/start.html Step 3: Select Content Services -- click  Spaces Step 4 : Create a space. Step 5: Configure space. Step 6:Create Entity Module Step 6:Open and Configure Entity. Step 7: Select path from pathbrowser option. Step 8: Select path accordingly and save it. Step 9: Entity ready for preview on local, json path is created and ready