Adobe Experience Manager Tutorials

Interact with CQ/AEM

Location of CQ5 elements

1 OSGi Bundles

2 Templates
3 components - page, contents [JSP Scripts or Servlets are used to render components in CQ.]
4 Static files

global.jsp
------------
What is the use of including Global.JSP <%@include file="/libs/foundation/global.jsp"%> ? Why global.JSP file is getting included default when you create a new component?

global.jsp file is having many useful implicit objects available once included.
it supports usage of cq taglibs

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

API's to interact with CQ/AEM Apps
-------------
1 CQ or WCM API
2 Sling API
3 JCR API

Side kick-

How the sidekick appear/disappear in a page?
----------
WCM initialization code calls the side kick. So it appears
location of side kick code: /libs/wcm/core/components/init/init.jsp

Just include below code in your JSP. It brings side kick
<cq:include script="/libs/wcm/core/components/init/init.jsp" />

Include option for JSP
------------------------
Compile time - <%@include file="/libs/foundation/global.jsp" %>
run time - <cq:include script="/libs/foundation/global.jsp" %>
run time - <sling:include resource="<%=par%>" %>

Options available to access content in CQ5 WCM/AEM

=============WCM API [currentPage object ]================ 

<%=currentPage.getTitle()%> 

=============Sling API[properties object ]================ 

<%=properties.get("jcr:title")%> 

=============JCR API[currentNode object ]================== 

<%=currentNode.getProperty("jcr:title").getString()%>

AEM Run modes - Ports - CRX

CQ/AEM Run modes

1 Author
2 publish

default is always author

AEM - CQ Ports:

Default port of AEM is 4502,if this port is not available its next look up ports as 8080,8081...

AEM installation first time takes more time:
This is the time all set up is done in system level. All packages, jar files, lucene, webserver etc installed during this time.

Accessing AEM Main console:
http://localhost:4505/

CRX interface:
http://localhost:4505/crx/explorer/index.jsp

Felix console:
http://localhost:4505/system/console/bundles

IDE's for CQ- AEM

CRXDE Lite- browser based

http://localhost:4505/crx/de or http://localhost:4505/crxde

Limitations of CRXDE Lite:

You cannot debug JSP/Java code
No Auto code completion

CRXDE Eclipse

Below given the image of CRXDE once loaded first time. It contains 3 folders by default.

apps
etc
libs.

Configuring CRXDE to add more directories can be done at below location

/etc/crxde/profiles/default -> crxde:paths -> To add new directories, add required directories here as shown.

Directory structure CRX
----------------------------

content dir-all contents like page,
tmp-file moved from desktop to cq will be placed first in tmp
Home- All created user & groups are stored in home directory
apps- ALL new CQ apps/projects created here
etc- all website design, client lib, css, js
lib- code of the core functionality
var- all auditing info stored here like adding page, deleting page etc. all user compiled class files are cached here
jcr:System- version contents stored here
rep:policy,rep:repoPolicy- repository level permission(users & groups) are stored here
bin- to deploy our custom servlets.

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

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

Thursday 5 June 2014

Interact with CQ/AEM

AEM Run modes - Ports - CRX

AEM(Adobe Experience Manager)- Day CQ Basics