DAY CQ(Communique)

DAY CQ(Communique)

AEM 6.1- Version 5.6 onwards is called AEM

2 kinds of modes 

1)Author

2)Publish

Server naming 

Cq-<Run-Mode>-p<portnumber>.jar

Cq-author-p4502.jar

Cq-publish-p4503.jar

Author instances run on even number ports (4504,4506,4508..)

It is possible to have multiple instances running on a single machine

An author instanes requires approximately close to 3 GB – 8 GB RAMS recommended

AEM infrastructure 2 ways

1)On premise – admin , Initial setup,Deploy,monitor the production env

2)AMS(Adobe managed  services) 

To access any url in AEM

http://<servername>:<portnumber>/ -  Login page

http://localhost:4502/

Pre-requisites for AEM startup

1)JDK 1.7 or higher running – SET JAVA_HOME and path variables

2)4 gb of ram

=======================================

Cq-publish-p4503.jar

3 ways of starting server

1)1st Way of startin server - Double click the jar file

CRX-quick start folder gets generated

• - Jetty webserver 

5.6.1and older versions – CQSE(Cq servlet engines)

)2nd way of starting server –  During startup if you want to allocate the heap memory

To extract the jar by commandline

Java –jar cq-author-p4502.jar

-Xms or -XmX (Minum and maximum heap size)

java -XX:MaxPermSize=256m -Xmx1024M -jar cq-author-p4502.jar

-XMs: Minimum heap size

-XmX- Maximum heap size

Permanent generation (Permgen)-

Which holds informations about all the classes,methods,objects in your JVM classloader

My AEM is starting because there are 400 odd OSGI bundles that get added into the container and these bundles go into the active state

AEM uses log 4 framework for logging

• - LOG4j – WARN,INFO,ERROR,DEBUG

TroubleShooting the Instance

1. 1) http://localhost:4502/system/console - Felix - Ensure all bundles in active state

First time server start up takes time – 3 mins

        2)Go the crx-quickstart/Logs and inspect error.logs,stderr.logs and Stdout.logs

To view the bundless

OSGI is the specification

Apache felix is the implementation of OSGI that AEM uses

http://localhost:4502/system/console - Felix

Bundle is a jar +metadata

3)Go to CRX-Quickstart folder, 

  - Bin - Start and stop batch scripts

  - You can start in 3rd way Only if you have started the server in the 1s or 2nd way for the first time

When AEM starts, Automatically a web server is getting started in the backend(Apache JETTY) – 6 Onwards

Which was web server was getting started in AEM 5.6.1 and older – CQSE(Cq Servlet engine)

Its also possible to deploy AEM on top of an existing APP server.

It is also Possible to deploy AEM on a running application server

AEM distribution -WAR file

https://docs.adobe.com/docs/en/cq/5-6/howto/install_application_server.html

==================================================================================

ARCHITECTURE/Technology stack of AEM

1)Storage-

JCR(java content repository)

Hierarchical based storage model

Data is stored in the form of nodes and properties

(/) Top most node in your hierarchy

  JCR is a specification(JSR 283 spec)

Every node has its associated properties where every property is a key/value pair

There are different types of nodes in JCR

AEM uses 2 implementations of JCR 

1)Apache jackrabbit OAK and

2)Adobe’s implementation – CRX(Content repository extreme)

To browse the repository

http://<servername>:<portnumber/crx/de - Lightweight way of accessing crx

http://<servername>:<port number>/crx/explorer

Every node is identified by a property called jcr:primary type which is a mandatory property

Whenever we have a cq:page its child has to be jcr:content

What are the features of  over DBMS/advtgs of jcr

1)Versioning

2)Searching

3)Indexing (/oak:index)

4)User permissoning

5)Observation  I want to observe my node, the moment a node changes I want a java piece of code to get executed Trigger

http://<servername>:<portnumber/

In our case http://localhost:4502/

There are 2 kinds of views in AEM

1)Classic mode or developer mode- Index page - http://localhost:4502/welcome.html  

Classic view of a page

http://localhost:4502/cf#/content/geometrixx/en.html

Intial versions- 5.5,5.6.1

2)Touch UI - Responsive framework for authors – Index page

 http://localhost:4502/projects.html

Touch Ui mode for a page

http://localhost:4502/editor.html/content/geometrixx/en.html

My development remains same for components – I need to create separate dialogs and separate dialogs for classic Ui

AEM architecture

Data storage

1)No concept of database

2)Hierarchical model for storage

ROOT NODE(/)

      Child nodes

JCR  Java content repository (Specification)  - JSR283

– Interface(Set of rules)

Data is stored in the form of nodes and properties

Every node has associated properties

A property is a key value pair – Property has a data type

Which implementation of JCR does AEM USE?

      Apache Jackrabit OAK and

      Adobes’s implementation of JCR CRX(Content Repository extreme)

How do I explore the repository

http://localhost:4502/crx/de or

http://locahost:4502/crx/explorer

Everything is a node in JCR

My Entire website is based on the nodes and properties

Everything is a node in JCR

APACHE SLING 

Is a rest based protocol to access the JCR over the web

Is used to Webify the content

OSGI(Open service gateway initiative) - Specification

JAVA CODE –

Modular programming approach

My Application can be divided into modules or Bundles

What is a bundle?

JAR(collection of compiled classes,interfaces and so ) + Metadata

Apache Felix – Implementation of OSGI

http://<ServerName>:<Portnumber>/

http://localhost:4502/system/console

1)Every bundle has its own lifecycle( It has its own class loader)

This is what enables every bundle to be started/stopped?

OSGI support multiple of a versions to be deployed on a container

There are 2 kinds of views in AEM

1)CLASSIC UI ( Legacy view) – Non responsive ( Light green backgrounds)

http://localhost:4502/welcome.html - Index page

http://localhost:4502/cf#/content/geometrixx/en.html

EXT JS framework (Sencha)

2)TOUCH UI – 5.6.1 onwards

http://localhost:4502/projects.html

Responsive framework for authors

CORAL UI 

A common look and feel across all the Adobe marketing cloud solutions