 Overview of AEM.

 Installation of Author and Publish Instances.

 Views in AEM – Classic vs Touch UI.
 Technology Stack of AEM – Overview.
 AEM Consoles Walkthrough – DAM/CRXDE/TOOLS etc.

Overview
Adobe Experience Manager (AEM), is a comprehensive content management platform solution for building
websites, mobile apps and forms - making it easy to manage your marketing content and assets
AEM is a component of the Adobe Marketing Cloud, which is a suite of solutions that integrate with AEM such as
Adobe Target, Adobe Analytics, Adobe Campaign, Adobe Social, Adobe Primetime, Adobe Media Optimizer and
Adobe Audience Manager. You can use AEM alone, or in conjunction with one or more of the other components for
a complete digital marketing solution.
History
CQ5 is a version of Day CQ portfolio developed by a Swiss-based software company Day Software in 2008, followed
by Day CQ 3.5, 4.0, 4.1 and 4.2. Adobe Systems renamed Day CQ5 as Adobe CQ5 after acquiring Day Software in
2010. Following the release of the fifth version of CQ5 i.e., 5.5, Adobe renamed it as Adobe Experience Manager
(AEM) in 2013 with a sixth version AEM 5.6, Latest version is 6.4.
Reference:
https://helpx.adobe.com/in/experience-manager/aem-previous-versions.html
Can obtain the documentation of previous versions.
Installation of Author and Publish Instances
a• a. Pre-requisite: Installed Java Platform, Standard Edition JDK - or other supported Java Virtual Machines.
b• b. Go to command prompt and check whether Java installed/Configured in environmental variables.

cmd->java -version
JAVA_HOME -> JDK path, path ->JDK/bin
Experience Manager Quick-start file (Standalone JAR or web-application deployment WAR – Without build in servlet
engine / server).
Naming Convention before installing AEM instance:
When first installing AEM or CQ, the name of the quickstart jar can be used to determine whether the instance uses the
author run mode or the publish run mode.
The naming convention to use for CQ 5.6 and earlier is:
cq-<optional-version-or-identifier>-<standard-run-mode>-<port-number>
The naming convention to for AEM 5.6.1 and later is:
aem-<optional-version-or-indentifier>-<standard-run-mode>-<port-number>
As an example, the quickstart jar for an AEM 6.0 instance running as an author instance with the port of 4502 could be
named:
aem-6.0.0.20140515-author-4502.jar or aem-author-p4502
Reference: https://helpx.adobe.com/experience-manager/kb/RunModeSetUp.html
Different Ways to start AEM Instance:
1. Double Click on Jar file.
2. Java command to execute Jar.
java –Xms1024m -jar AEM-author-p4502.jar –p 4502 –r author –gui
Note: As we know Java allocate objects at heap area, some time it happens we get the ‘Out of memory’ exception, using
above command helps in allocating the extra space to heap so that we can avoid memory exceptions.
Also, we can bind the debug port, it helps in debugging the issues with Java Bundles/Code.
3. Once the file is extracted using option-1, it can be started by going
crx-quickstart folder -> bin -> Start.bat (Unix compatible command also can be found)
Stop.bat ->Stop file.
Webserver - AEM
Once AEM instance is started, A webserver is also get started at the back end.
Apache Jetty - Internal implementation of AEM comes default. – It’s a servlet engine and HTTP Server.
More info: https://www.eclipse.org/jetty/
If needed, different application server can be configured like JBoss/WebLogic – AEM War file is required.
Author and Publish Instances
author
Author is usually located behind the internal firewall as it is the environment where you and your colleagues will input
your content and administrate the system
publish
This environment holds the content you have made available to visitors to your website; be it public, or within your
intranet [Type here]
Svsoft solutions - An Online Training Institute<info@svsoftsolutions.com>
Views in AEM.
Classic UI -> http://localhost:4502/welcome.html
Legacy UI, Extended JS implementation, Not compatible for devices i.e. Unresponsive
Touch UI -> http://localhost:4502/aem/start.html
Touch -> Coral UI and Granite UI based, responsive and mobile first.
WCM Authoring UI mode Service. (Can change the behavior while opening the page in content or site admin), Modes
(TOUCH & CLASSIC)
ROOT Mapping: /welcome.html /projects.html
Technology Stack of AEM – Overview.
• • JCR (Content Repository API for Java): It can be defined as the specifications for accessing
content repository using JAVA API in uniform manner. So, JCR is “type of repository”. CRX is an Adobe
implementation of JCR. Similarly, Apache Jackrabbit is an external implementation of JCR by apache.
Example of traditional Databases – Oracle/SQL Server – Table Concept.
A JCR is an object database that provides various services for storing, accessing, and managing content.
In addition to a hierarchically structured storage, common services of a content repository are versioning, access
control, full-text searching, and event monitoring (JCR Observation Framework - Event Handling (Modified / Added etc.)
The JCR provides a generic application data store for structured hierarchical data, plus observation, versioning and full
text search.
JCR stores data in form of (Nodes -> Properties (Key/Value) ), it forms the hierarchical data model.
• Entire Site data gets stored in form of Node and Properties.
• Every File, Folder, Image treats as a node. To differentiate, there is an jcr: primaryType [sling:folder, nt:folder, etc.]
• Each node will be having jcr: primaryType property and every page would be having a child node jcr:content, every
page will be of type cq: page under content.
• Open JCR node, and see in property console (Protected, Mandatory, Multiple, Auto Created]
• Data is stored in form of TAR (Tape Archive files. (Unix compressed files – Non-readable format)
• Data will be lost if any segment is deleted.
• Tar Location under crx-quickstart/repository/segments

To view the repository:

http://localhost:4502/crx/de
http://localhost:4502/crx/explorer
Sling:
Apache Sling is a web application framework for content-centric applications, using a Java Content Repository, such as
Apache Jackrabbit or CRX, to store and manage content:

• is based on REST principles to provide easy development of content-oriented applications.

• is embedded within CQ5.
• is used to process HTTP rendering and data-storage requests which assemble, render and send the content to a client.
• maps Content objects to Components (which render them and process incoming data).
• comes with both server-side and AJAX scripting support.
• can be used with a range of scripting languages, including JSP, ESP and Ruby.
• started as an internal project of Day Management.
• has been contributed to the Apache Software Foundation.
OSGI
CQ5 is built within an application framework which is based on the OSGi Service Platform.
OSGI Technology:
• “is the dynamic module system for Java™.”
• “provides the standardized primitives that allow applications to be constructed from small, reusable and collaborative
components. These components can be composed into an application and deployed.”
• OSGi bundles can contain compiled Java code, scripts, content that is to be loaded in the repository, and configuration
or additional files, as needed.

AEM Consoles Walkthrough:

CQ5 is made available through various specialized web consoles:
• Websites for creating and managing multiple websites.
• Digital Assets for organizing various digital assets.
• Campaigns for managing marketing campaigns.
• Community for moderating content of the social network.
• Inbox for managing your inbox items.
• Users for managing user accounts and groups.
• Tools for maintaining and configuring the CQ5 system.
• Tagging for organizing tags and their namespaces.