AEM Content Service Step by Step | 6.3

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 to use.


Step 10: Activate it to use in publish.


Step 11: Crxde view of Entity content.

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