Saturday, 9 May 2020

AEM Log Tracer: Chrome Plugin


AEM Log Tracer


AEM Log Tracer is a Chrome browser extension that exposes server-side log information per-request in the browser.

AEM Log Tracer collects and exposes per-request:

  1. AEM Logs
  2. Request Progress
  3. Queries executed

AEM as a Cloud Service: Dispatcher Setup

Local Dispatcher Setup

Dispatcher Setup

The AEM as a Cloud Service SDK includes a validator tool and docker image for simulating it locally.
 Dispatcher Tools is comprised of:
  • a baseline set of Apache HTTP Web server and Dispatcher configuration files, located in .../dispatcher-sdk-x.x.x/src
  • a configuration validator CLI tool, located at .../dispatcher-sdk-x.x.x/bin/validator
  • a configuration deployment CLI tool, located at .../dispatcher-sdk-x.x.x/bin/docker_run
  • a Docker image that runs Apache HTTP Web server with the Dispatcher module

AEM as a Cloud Service: Local Setup

Adobe is providing AEM SDK to install it locally.
AEM as a Cloud Service


Follow below steps to install SDK locally and install WKND site.

Navigate to Experience Cloud Software Distribution

Go to the General tab, download the latest Java version.
Experience Cloud Software Distribution

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.