You are on page 1of 24

Adobe AEM CoE - ECM Group EntSol

AEM 6 Overview and Features

1. WCM Basics

2. Leading WCM Products

3. Adobe AEM
4. AEM 6 Features

5. Upgrading to AEM 6.0

TCS Siruseri State of the Art
Campus in Chennai, India

6. Installation of AEM

WCM Use Case

Business Case
Customer has Internet Site which has different product pages of Banking Products. Whenever
there is a change in the content (Interest Rate, Text, Image etc.,) Business Unit has to raise a
Change request that goes through approval cycle and finally assigned to IT Dept. The IT team will
work on the request and the changes will be incorporated in the site. The changes will be pushed
to live after it is reviewed and finally approved by the business. To implement such kind of a
change in the website it takes few business days/weeks to complete.
Need to reduce the time it takes to modify product pages on website from a few business days to 1
Technology/Tools Used : Java, JSP, HTML, CSS, Microsoft VSS, Microsoft IIS

Solution : WCM
Allows the business to modify and review the pages without depending on IT. It reduces the time it
takes to modify product pages on website from a few business days to 1 hour.

WCM Basics
Web Content Management System - is content management system (CMS) software, implemented as
a Web application, for creating and managing Web content. It is used to manage and control a large,
dynamic collection of Web material (HTML documents and their associated images).
WCM is a software system that provides website authoring, collaboration, and administration tools
designed to allow users with little knowledge of web programming languages or markup languages
to create and manage website content with relative ease.

Web Content: It could be any content on the web, be it a full page or building blocks of web page namely


.JSPs , . ASPxs, PHPs etc




Videos, Audios, Flash

Word Docs, PDF Files as links

Content created by WCM Tool

WCM - High Level Architecture

Business Analyst

Business User

Runtime /
Production /










Other External

External Systems Integration

End Users or Web Site Users

Type of Users - Authoring Environment

Business Users
Content Contributors / Authors
Content Reviewers
Content Editors
Systems Analysts
People who create Templates, Components etc., such that Business Users can user
them to create web pages.
People who ensure that the application is up and running.
Provide access to Authoring environment.
Apply patches / perform upgrades etc.,

Key Features of a WCM solution

Key Features


Authoring Interface

Good authoring interface such that business users are able to create
web pages , normally using templates and components

Version Control

Versioning is a process by which documents are checked in or out of the

system, allowing users to retrieve previous versions and to continue
work from a selected point.


Empowers users to tag and categorize metadata (data that describes a

document) either manually or automatically . Using a pre-defined
Taxonomy structure and by Metadata.


Identifies and enforces document stages such as reviewed, approved,

published, archived and retired


Feature that ensures the business users are able to view the output of
the web page without deploying the page to any other environment,
during the process of authoring.

Key Features of a WCM solution

Key Features



Defines and automates business processes associated with creating ,

approving and distributing web contents


Ability to deploy entire web site or a page to runtime environments.

Deployments can be manual or scheduled (automated). Deployments can be
rolled back if not successful to one server in a clustered environment


Ability to display content in multiple languages . Should also be able to

author content in Multiple Languages. Also called localization if a Country
Language code is involved like UK-en, US-en

Delivery / Mobility

Seamless delivery of content across multiple channels like Desktop, Phone

and Tablet . Content and Layout should change as per the device requesting
the web page.

Bulk Import

To import contents using a Bulk Import feature, that uploading them


Access control

Ensuring access to contents are as per defined permissions. Permissions to

be controlled by business users.

Key Features of a WCM solution

Key Features


Ability to display content as per the profile of the logged in user. Targeting
is also possible based on IP, Geography etc.

Management (DAM)

DAM ensures that digital assets like Images, Audio, Video files are stored
as a single repository , then rendered as per specifications.

A / B Testing

To support A/B Testing ( Multi Variant Testing) . Usually a plugin to a WCM


Web Analytics

Seamless integration with web analytics to analyze web site traffic and
user behaviors


Create campaigns for faster promotion of Marketing concepts. Campaigns

can be targeted for particular segments.

Focus on Customer Experience


Web Content and Experience


Web Experience

Web Content


Static Text
Based Sites

Automation of
web publishing

Marketing focus
with analytics
and social

Focus on multichannel &

mediums for

Leveraging web
for e-commerce

information display
brochure kind of


Leading WCM Products

WCM Solution from Adobe, Adobe procured Day CQ in
2010. Currently being branded as Adobe AEM ( Adobe
Experience Manager)

Currently being marketed as Sitecore Experience Platform

WCM Solution from HP, Originally from Interwoven, autonomy procured

interwoven. HP procured Autonomy. Currently being branded as HP
SDL acquired Tridion, currently being marketed as SDL

Note: Lots of Open Source products as well Alfresco, Drupal

and Liferay are leading players
Legacy WCM Systems:
Opentext Vignette, EMC WebPublisher

Gartner Magic Quadrant October 2014


Adobe Experience Manager


AEM Technology Stack


AEM Technology Stack

Granite Platform : Granite is Adobe's open web stack. It forms the technical
foundation on which AEM is built.
CRX It is a commercial implementation of Apache Jackrabbit(From AEM 6, it
is Jackrabbit Oak). It is content repository implementing the Content Repository
API for Java Technology (JCR 2.0).

JCR - is a specification for a Java platform application programming interface (API) to

access content repositories in a uniform manner. (Java package is javax.jcr)

OSGi Framework: Framework for modular application development using java.

Each module called bundle can be independently started and stopped.
Apache Felix: Apache Felix is an open source implementation of the OSGi. The
OSGi container that is included in CRX.
Apache Sling :RESTful framework to access a JCR over http protocol. It maps
the request url to the node in jcr.


AEM 6.0 Platform Changes


AEM 6.0 Platform Changes


AEM 6.0 Technical Requirements

Java Version :
Oracle SE 7 JRE 1.7.x
Java 8 is supported starting SP1
App Servers :
Quickstart built-in Servlet Engine (Jetty 8.1)
Apache Tomcat 7 and Tomcat 8
IBM WebSphere 8,8.5,8.5.5
Oracle WebLogic Server 12.1 (12c)

Browser :
IE 9+
Google Chrome 38+,
Mozilla Firefox 33
Dispatcher :
Microsoft IIS 7.5, 8.0 and 8.5
Apache httpd 2.2 and 2.4.x


Amazon EC2
Microsoft Azure Virtual Machines
Rackspace Cloud
VMware vCloud


AEM 6.0 Features

New Repository Foundation
Jackrabbit Oak(CRX 3) : Enhance performance and scalability of the content repository.
Storage Options:
TarMK(default): Local, fast, easy to operate. A microkernel that uses the Tar persistence
system for storage.
MongoMK : Distributed, remote. A microkernel that uses MongoDB for storage. Horizontal,
linear scaling of the content repositories based on open-source document database.
Distributed, remote
Sightly : New HTML template language. It is based on HTML5.

Sightly components are compatible with components written in JSP or ESP

Even within the same component, Sightly templates can be used alongside JSPs and
ESPs. For example, a JSP can include a Sightly template like this,
<cq:include script="footer.html"/>
and a Sightly template can include a JSP like this,
<div data-sly-include="footer.jsp"></div>
More open source : Jetty 8 and Apache Solr
Developer Mode : Provides Debugging and Testing tools directly in AEM Authoring
Developer Mode is only given to users who have write access on /apps, by default.
Hobbes,js - A testing library written in Javascript

AEM 6.0 Features Cont.

New and Updated Features :

Optimized UI based on Jquery and Coral UI.

Social Communities - a collection of redesigned social components based on Social
Component Framework which now allow also storage in Adobe Social cloud.
Mobile Apps support - simplifies management and deployment of mobile applications to
multiple platforms using PhoneGap Build.
Many DAM enhancements - including 2-way syncing with Creative Cloud, Dynamic
Media support integrated directly into AEM, processing profiles, metadata schemas,
enhanced search and improved team collaboration with projects, workflows and tasks.
Operations Dashboard - allows monitoring and diagnosis of the AEM platform and
running maintenance tasks and various health checks, all this from one place,
Improved and new integrations with Adobe Marketing Cloud services (including Target
and Campaign)
eCommerce Integration Framework extensions for Elastic Path and Intershop.
Adaptive Forms - easy-to-use solution to create complex and responsive forms.
No Automatic Indexes - you have to create your own custom indexes otherwise your
searches will be very slow.


JackRabbit Oak aka CRX 3

Oak is the successor of Jackrabbit 2 and is also, based on , JSR 283.It uses MVCC(MultiVersion Concurrency Control) model.
Micro Kernel - The MicroKernel API, provides an abstraction on top of actual storage of
content on the file systems. It is based on Strings and leverages JSOP - HTTP Based protocol
for working with JSON Objects.
Currently Oak has two main Microkernel implementations : DocumentMK and SegmentMK


Upgrading to AEM 6.0

In-Place Upgrade: Drop in the new jar file in place of the original one in your <aem-install>
directory.This leaves the existing CRX 2 repository as-is.
For upgrades from versions up to and including AEM 5.5, we need to explicitly stated via
the "crx2" runmode
ojava -jar aem-quickstart.jar -r crx2
For custom LoginModules configured for authentication(In AEM 5.6.1 configuration was
placed in the repository.xml ) , you need to do it in Apache Felix JAAS Configuration
Factory service via the Web Console.

Migrating to Oak: Once the in place upgrade is complete, you can optionally migrate the
existing CRX 2 repository to the new Jackrabbit Oak-based CRX 3 repository.
Adobe provides a tool - CRX2OAK repository migration tool (crx2oak-1.0.6.jar) 10 Mins /GB
(It doesnt migrate binary content)



Set the JAVA_HOME with JDK 1.7

Create a Folder C:\Adobe\AEM\Author

Copy AEM quickstart JAR and file into created folder structure.

Rename AEM quickstart JAR to aem-author-4502.jar

aem=Application, -author = the WCM mode that it will run(e.g. author or publish)
-4502 = the port it will run (e.g. any available port is acceptable.)

Command Line Start: java -Xmx1024M -jar aem6-author-p4502.jar


AEM Environments
Edit Mode This is the default mode and allows
you to edit the page, adding or deleting
components and making other changes.
Design Mode In this mode, the sidekick is
minimized and you have the possibility to edit the
design of the page:
Preview Mode This mode allows you to preview
the page as if it were appearing on your website in
its final form.
Edit Mode This is the default mode and allows
you to edit the page, adding or deleting
components and making other changes.

Various modes in Author environment

Design Mode In this mode, the sidekick is

minimized and you have the possibility to edit
the design of the page.
Preview Mode This mode allows you to
preview the page as if it were appearing on your
website in its final form.