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

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) {      ...
Read more

AEM 6.3 | MSM Extended | JCR Properties Rollout

Image
AEM OOB excludes certain properties like jcr:title, jcr:description, cq:designPath  in live copy content rollout and  update . These properties are configured and controlled by O SGi configuration and can be modified accordingly.  Step 1 : Go to Configuration Manager Search for CQ MSM Content Update Action Step 2 : Open the OSGI configuration and it is as below snapshot. com.day.cq.wcm.msm.impl.actions.ContentUpdateActionFactory Step 3 : Override in application level OSGi folders(runmodes) as below. com.day.cq.wcm.msm.impl.actions.ContentUpdateActionFactory.config and do the modifications as needed in  Excluded Page Properties . Ex: By default  jcr:.* is excluded and if a requirement is to e nable jcr title and description, we have below expression to be  jcr:(?!(title|description)$).*                      Step 4: Content ready for Rollout.
Read more

ACS Commons Sitemap Servlet extension to support Multiple Languages Domain

Image
ACS Commons provides OSGI Sitemap config service to generate sitemap xml file which is used by web crawler to optimize web search results. The provided sitemap servlet takes input from externalizer configuration which acts as domain to the list of content pages. This hosted configuration would have a root domain to the list of locales available for an application. This remains constant for applications having more than one domain and the purpose of multiples domains is not achieved. This can be achieved via switching externalizer domain config to page properties values. Example shown below: From externalizer setting : Code from :  String loc = externalizer.externalLink(resolver, externalizerDomain,  String.format("%s.html", page.getPath()));  writeElement(stream, "loc", loc);        New Page properties Config value to be taken from each country landing page:    Code to :             ...
Read more