Saturday 24 February 2018

AEM 6.4 Features

Our team had a chance to attend partner session of AEM 6.4 and excited to see the new features of AEM 6.4.

We are going to explain all of them in latest blog posts soon.

AEM 6.4 New Features

AEM 6.4 is a powerful digital marketing single platform which takes advantage of cloud, online & physical channel connectivity utilization of machine learning to personalized customer experience. AEM 6.4 is basically a cloud based architecture and shift content management from 'channel driven' to 'journey driven' now.

The latest AEM features are given below

1. Features based on cloud integration:
Efficient Omni-channel experience:
The latest tightly integrated Adobe Marketing cloud and Adobe experience cloud helps utilize content and data more closely than before. This helps in a fluid experience across all touchpoints.

Adobe Experience Cloud and Security:
Now the managed service clients have access to cloud manager which accelerates deployments and updates through a dedicated and powerful devops system which also ensures the security across channels.

Intelligent content delivery:
Utilizing the Sensei,  we can design , automate the best experiences to provide a 360 degree view of content which is most sensible to a specific user when ever he requires and in a suitable place.

What s Adobe Sensei?
 Adobe Sensei, is Adobe's Artificial Intelligence and machine learning framework, which automates the delivery of personalized content, empowering marketers to work smarter and faster.

Flexibility of accessing assets from Experience Manager to Creative cloud.
The Marketing cloud - Creative cloud(AMC-ACC) integration helps search, access, modify an asset stored in Experience Manager more quicker from a creative cloud.

3D capabilities:
Experience manager integration with Adobe Dimension CC, 3D assets can be easily convert to marketing assets.

2. Features based on AEM Usability

New Single Page Applications(SPA ) capability in AEM:
Now we can utilize the SPA editor and utilize any latest technology to integrate across multi channels.

Smart Tags and utilization:
Now using smart tags , we can discover relevant images easily & quickly. Utilizing

Dynamic Media Capabilities & Smart Imaging
Now utilizing the intelligent media capabilities, smart imaging understands the situation and compress the images and ensures a faster delivery. Smart crop is based on Adobe Sensei and detects the image which helps to crop the images more efficiently.

Automated Forms conversion:
A smart way of converting forms in other formats like PDF to a more user friendly mobile supported presentation.

Find our site violate something? Please notify us through the comments section or email us.

the Adobe Sensei capabilities, we can train the algorithm and in future use this information to automatically add metadata keywords.

Subscribe Our YouTube Channel Here.

Read More

What’s New in Adobe Experience Manager

Adobe Redefines Content Intelligence to Transform Customer Experiences

AEM Capabilities

Interested in taking a first look at AEM 6.4 UI and dash board? Watch this video.

AEM 6.4 Features

Advantages of using Adobe Cloud Manager for AEM

Dynamic Media & Related Features in AEM 6.4


Machine Learning Enabled Features in AEM

Tuesday 13 February 2018

WCMUsePojo class & Alternatives in AEM?

AEM’s component development needs a back end logic to retrieve values from back end. Sightly is a templating language which together with WCMPojo helps to create components.

This approach(Sightly + WCMUseClass) provided better decoupling of the presentation layer vs business logic, thus code will be more maintainable and also easier to debug. AEM 6.1 or 6.2 uses WCMUsePojo class (or even Sling Models) for back end logic. Adobe recommends Sling Models as a best way of implementing AEM WCM Components with version AEM 6.3.

So in Brief,

We can use simple Pojo (without extending Adobe's class) with java-use-api. Cases where resources/services are not easily available, we can extend WCMUsePojo to get the ability to use resources/services. In an advanced way, we can go with Sling Models which will give more flexibility and ease, because it uses annotations.

Important Sling Annotation Reference are given below.

@Model : declares a model class or interface

@Inject : marks a field or method as injectable

@Named : declare a name for the injection (otherwise, defaults based on field or method name).

@Optional : marks a field or method injection as optional

@Source : explicitly tie an injected field or method to a particular injector (by name). Can also be on other annotations.

@Filter : an OSGi service filter

@PostConstruct : methods to call upon model option creation (only for model classes)

@Via : change the adaptable as the source of the injection

@Default : set default values for a field or method

@Path : only used together with the resource-path injector to specify the path of a resource

@Exporters/@Exporter/@ExporterOptions/@ExporterOption : for Exporter Framework

WCMUsePojo Vs Sling Models

  • Mixed POJOs - Pure POJOs
  • Extends from WCMUsePojo - Standalone class with '@Model' annotation and having no keyword
  • More code required to retrieve common objects or property values - Easier methods to retrieve common objects or property values
  • Uses  Felix annotation '@Reference' to reference to an available OSGI service - Uses '@Inject' or '@OSGiService'
  • In case of WCMUsePojo, we have to overwrite the activate() method - init() method will be called in the @PostConstruct annotation
  • Not annotation driven - Annotation driven

Thursday 1 February 2018

How do we estimate an AEM Migration project?

There are scenarios where we need to migrate any existing CMS content to AEM. The steps for migration are given in my previous post.

Now let us see how do we estimate the migration activities.

Below given the activities for doing a proper estimation. The assumption is that the entire site is re-created in AEM as is.
  1.         List down the templates: Identify all the templates in site.
  2.         Estimate the templates: Estimate time for creating each template.(Skip the same types, consider only unique ones)
  3.         List components: Identify all the identical components to be created.
  4.         Estimate the components: Define time for each unique component creation.
  5.         Analyze the current CMS content ( XML/JSON Data) : Analyse the content. It may have textual content, metadata, tags etc.
  6.         Estimate the scripts for each components (XML/JSON Data to AEM Component): Now estimate time required to migrate the content using any of the content migration approach/ scripts.
  7.         Analyse asset migration: Find out how the assets are organised in current system. Find out the ways to move them to AEM.
  8.         Estimate asset migration and categorization(Extract and update metadata for digital assets on AEM): Here we need to calculate time required to move entire asset(not duplicates) to AEM.
  9.         Estimate Analytics part: Calculate the analytics implementation
  10.         Analyse the integrations: Find out all integration points and ways to replicate it in AEM.
  11.         Estimate Integration (Login, Authorization, Search): List out the time for integration implementation
  12.         Analyse the workflows:Find all the workflows to be created in AEM
  13.         Estimate Workflow creation: Estimate time for creating workflows based on the complexity.
If the site has to be redesigned, we need to consider the design activities also as part of estimation. We also need to estimate time for,
  • Environment setup(dev,qa,prod,dr)
  • Testing
  • Release configurations & activities
  • Additional authoring after the content migration.
Above activities helps to provide a valid estimation for any migration project.
Migrating a CMS website content to AEM? Follow this steps:

Read More:
AEM Integration with DOJO
Analytics Integration with AEM
WCM Use class
AngularJS with AEM
New features in AEM 6.3
HTL Tips