Showing posts with label AEM basics. Show all posts
Showing posts with label AEM basics. Show all posts

Wednesday 28 March 2018

Summary of release details : Adobe Experience Manager

AEM Release history

Product: Adobe Experience Manager
  • 6.6 , 2020 - Major Release  - Date not finalized
  • 6.5 April 8, 2019 - Major Release
  • 6.4 April 4, 2018 - Major Release
  • 6.3 April 26, 2017 - Major Release
  • 6.2 April 21, 2016 - Major Release
  • 6.1 May 28, 2015 - Minor Release
  • 6.0 May 28, 2014 - Major Release

List of new features/ capabilities in each release

AEM 6.6
To be updated

AEM 6.5
Content Velocity, Fluid Experiences improvements, Cloud Agility, Experience Intelligence

AEM 6.4
Fluid Experiences, AI Based crop features, Core components etc.

AEM 6.3
Oak Segment Tar File Format, User Interface, Security, OAuth

AEM 6.2
MongoDB support, User Interface  changes

AEM 6.1
Authoring enhancements, Enhancements to AEM Forms app, Experience targeting in AEM forms

Jackrabbit Oak,Touch UI,Sightly, More open source with Jetty & Apache Solr

Note: Please let us know if you find any discrepancy in the content/ data.

Subscribe Our YouTube Channel Here.

Thursday 4 January 2018

A program managers thoughts on site migration to AEM

Let us see how a project manager should think before he starts with a site migration to AEM. What things he needs to consider? The history of AEM has seen thousands of migration to AEM. But how many were successful? How many of them were cost effective? Let us do an analysis.

Planning before he starts.
There are multiple planning sessions to be done before actual migration starts.

Cost/ Budget Planning

The PM should think of the total cost estimated for the complete implementation. This includes initial setup, UI development/ UI changes, developing new feature additions, QA tools, platforms, integration costs, licensing costs etc.

Technical Planning

PM should get a clarity on the total number of sites, UX changes, data conversions, system integration, any analytical and personalization items.

Team Planning

Right mix of technology team is necessary for any development. For an AEM, the considerations should be the back-end, front-end capabilities of a developer including various integration through web-service layer, analytics, search etc.

Implementation Planning

Define the correct time frame with a proper sprint planning. Include the team in discussions is necessary for this.

Integration planning

Third party integration can be complex task when the developers are not aware of it. Always try to add a developer who knows the various integration like search, analytics, web-service etc.

QA Planning
Define a QA Strategy and ensure the test cases are prepared well before the actual development.

Deployment Planning

Ensure the DEV and QA work together to make the deployment process success. Define a deployment strategy considering latest tools and technologies available.

Set a well defined communication channel for the deployment process which makes the deployment smooth and success. Ensure the roll back and disaster recovery are considered in planning.

Post deployment planning

Regular Monitoring of performance and any backups are to be planned as part of this.

He or she should also consider the partnerships for AEM implementation, Adobe cloud solutions and infrastructure in course of time. Let me know your migration experiences through comments section.

Videos on AEM & Persistence
AEM Persistence TarMk & MongoMK Series 1
AEM Persistence TarMk & MongoMK Series 2  AEM with TarMK
AEM Persistence TarMk & MongoMK Series 3  AEM with MongoMK
AEM Persistence TarMk & MongoMK Series 4  TarMK Vs MongoMK

Read More
Rule Engine integration with AEM

Thursday 5 June 2014

AEM(Adobe Experience Manager)- Day CQ Basics

AEM(Adobe Experience Manager)- Day CQ

As we all know CQ/AEM(Adobe Experience Manager) is one of the latest Content Management System(CMS) available in market. All cms do below tasks on its own.

  • Versioning
  • publishing
  • work flow
  • indexing & searching

History of CQ/AEM
  • cq1 beginner product of CQ

  • cq2 used c language, files system to store data(platform dependent)

  • 2002 cq3- java(started using internal WAP server for http requests CQSE - servlet engine)
           Also having connectors to connect various data bases
  • 2005 CQ 4 (added independent storage part)
         CRX repository was added.Later was provided to Apache commons
  • 2008 CQ 5
          0,2.0,2.1,3,4,5 fixed bugs and added new features.
  • 2010 Adobe acquired day

  • 2013 AEM 5.6 version

  • AEM 6.0 architecture changed,

           Features include Global Site Management, DAM AND Dynamic media, Social Collaboration features, newer development features and some architectural changes, etc

Technologies involved in CQ/AEM

Technology Features
Apache Jackrabit open source repository (following JCR specifications) crx repository
Apache felix OSGI container
Apache PDF box indexing of the pdf files
Apache shinding only for hosting gadgets
Apache aries JMS functionality
Apache tika Indexing of all items/binding content except pdf
EXTJS to implement user interface components
JQuery JS framework
Less.js java script framework
CQSE-(not open source) internal WAP

Read More: 
Solr and AEM
JSON for Solr
Search Persistance
Navigation in AEM
Website design steps in AEM