Showing posts with label AEM 6.0 Features. Show all posts
Showing posts with label AEM 6.0 Features. Show all posts

AEM 6.0 New Features


Statement - AEM 6.0 new features

Features-
1.       Jackrabit 3(Oak) is used for repository re-write persistence.
§  Persistence Manager(PM)is out.
§  Uses Micro Kernels such as
o   SegmentMK – TarMK
o   DocumentMK – MongoMK
§  MVCC – Multi version concurrency control
§  Garbage collection(revision cleanup) on daily basis to avoid the repository/disk volume grow.
§  Oak run tool – for offline compaction – Server down time is required.
2.       Tar files are now memory mapped(off heap) , whereas for in older version in-heap CRX bundle cache concept has gone.
3.       Oak- All content are not indexed automatically, if at all required for efficient searches ,need to create/add manual indexes.
4.       Sling Health check monitoring tools.
5.       CQSE servlet engine is replaced with Eclipse Jetty.
6.       In Scene7 Image server – for creating dynamic image renditions on demand rather than prebuilt static image renditions.
7.       Clustering
1.       No more Active-Active CRX(Tar MK) Clustering
2.       TarMK cold standy active-passive clustering for availability but not for scaling
8.       New MongoDB based Active-Active(MongoMK) clustering
9.       New logback logging framework – for the configuration of external logging XML will be used
10.   ExtJS based sidekick has been deprecated, html5,CSS and JQuery used in new sidekick
11.   Binaries can be store on different disk volume (file Data Store), Data can be stored in S# data store AEM instance can be deployed on premise, cloud and non-cloud.
12.   Irrespective of data store (node store, data store..etc) all the binaries are stored and saved as *.tar  files in /crx-quickstart/segmentstore/ , lucene indexes also stored in the nodestore.
13.   Below console are renamed
§  Web content management(WCM) console to à Sites
§  Digital asset management(DAM) console to  à Assets
§  SoCo –Social communities to à Communities