Sunday, 8 March 2020

AEM Cloud Manager

Cloud Manager, part of the Adobe Managed Cloud Services, enables organizations to self-manage Experience Manager in the cloud. It includes a continuous integration and continuous delivery (CI/CD) framework that lets IT teams and implementation partners expedite the delivery of customizations or updates without compromising performance or security.


AEM as a Cloud Service



For the last few years, Adobe Experience Manager (AEM) has been available as On-prem and Adobe Managed Services (AMS)

There are intrinsic differences between these previous approaches and AEM as a Cloud Service:

AEM as a Cloud Service Benefits

Version Less AEM: 

No need to worry about upgrading to the latest AEM version. When a new version is available, we can upgrade from the Cloud Manager CI/CD pipeline which is fully automated.

Quick Time to Market: 

AEM as a Cloud Service assists you in quickly delivering the products, services, and experiences faster without developing customized content management systems.

Auto-scalable: 

It can scale automatically based on traffic and operations. It requires less support and maintenance efforts.

Separation of code and content: 

Custom code and configurations are clubbed into the AEM base image which is then used to create multiple Author and Publish nodes. The changes to the code and configurations are made only through CI/CD pipelines in Cloud Manager.

 Security: Industry standard security measures will be taken care of. 

References:

Tuesday, 3 March 2020

Fetch Content Fragment using Sling Model

We have seen how to create a content fragment in the previous post.

Content Fragments can be rendered onto a page by below different ways:
  1. Using AEM core components
  2. Using Custom Sling Model
  3. Using Servlet to access Content Fragment.

Fetch Content Fragment using AEM Core Components

We have seen how to create a content fragment in the previous post.

Content Fragments can be rendered onto a page by below different ways:
  1. Using AEM core components
  2. Using Custom Sling Model
  3. Using Servlet to access Content Fragment.

Let's see how to render Content Fragment using AEM Core Components.

Enable AEM core components

Create a new project called “aemquickstart” using Adobe’s project archetype. Below is a maven archetype command to use. This will generate a boilerplate project with the latest version of Core Components.
mvn -B archetype:generate 
 -D archetypeGroupId=com.adobe.granite.archetypes 
 -D archetypeArtifactId=aem-project-archetype 
 -D archetypeVersion=23 
 -D aemVersion=cloud 
 -D appTitle="AEM Quickstart" 
 -D appId="aemquickstart" 
 -D groupId="com.aemquickstart" 
 -D frontendModule=general 
 -D includeExamples=n

Run below maven command to install the package in AEM
mvn clean install -PautoInstallPackage

Content fragment and content fragment list core components under ui.apps sub module
  • /aemquickstart/ui.apps/src/main/content/jcr_root/apps/aemquickstart/components/content/contentfragment
  • /aemquickstart/ui.apps/src/main/content/jcr_root/apps/aemquickstart/components/content/contentfragmentlist

Let's add these components on to the page.
  1. Go to AEM Start > Sites > aemquickstart > US > English
  2. Click on the parsys
  3. Click the plus icon
  4. Select Content Fragment
  5. Edit the content fragment
  6. Select the "AEM Book" content fragment that we created in the previous post
  7. Add Title, Description, Release Date and Image elements as shown below.
  8. Save the dialog

Now we can see the content fragment info on the page.

Create Content Fragment in AEM

What is Content Fragment?

Content Fragments are editorial content, primarily text, and related images. They are pure content, without design and layout. Content fragments are not available in the classic UI. AEM also supports the translation of fragment content. Learn more about content fragments here.

Create Content Fragment Model Configuration:


Before we create content fragment we need to create a content fragment model. AEM configurations allow you to do many things such as editable templates, contextual site configurations, and content fragment configurations.
  1. Go to AEM Start > Tools > General > Configuration Browser > Create
  2. Enter “AEM Quickstart Site” for the title
  3. Check the “Content Fragment Models” checkbox
  4. Click create

Create a DAM Folder

Content fragments are stored in the AEM DAM and are simply treated as an asset like an image or pdf. We will want to create a DAM folder for storing all of our content fragments.
  1. Go to AEM Start > Assets > Files > Create > Folder
  2. Enter the title
  3. Click create

Sunday, 1 March 2020

Update Content using Launches in AEM

Launches in AEM enable you to efficiently develop content for a future release. A launch is created to allow you to make content changes for future publication (while maintaining current pages). After editing the launch page, you need to promote the Launch. So the edited launch page will be published on the live date.

For example, you have an online store and you need to display promotional info x-mas and New Year. To do this, you can create a launch page and set it to publish on 25th Dec. Create another launch page for New Year.

Creating a Launch:

Launch can be created from two consoles in AEM
  1. From Navigation -> Sites -> Create button ->Launch 
  2. From Tools -> Sites -> Launch
Navigate to Sites, create a Launch