Professional Documents
Culture Documents
1. JCR
2. Apache Sling
3. Apache Felix
4. OSGI
JCR: The JCR is the storage layer or jcr is a database that looks like a file
system , it is unstructured and enables versioning and observation, jcr is
the base level of the AEM technology stack and Jcr provides services like
full text search, indexing, access control and event monitoring.
Prerequisites
Steps
2.Publish Environment - where the end user of the website sees the content.
6. Now, navigate to the author directory and run the following command
—
java -
agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n -
jar aem-author-p4502.jar -gui
This command runs the AEM in debug mode; which means you can debug your
code while developing. While developing on the local environment, it is always
useful to run AEM in debug mode. If you don’t want to run AEM in debug
mode then just run the following command —
7. When you first run this command, it will take some time to create the
CRX repository and load all the required stuff. After a few minutes, a
browser window will automatically open on http://localhost:4502/, and
you will see something like this -
8.Login using following credentials
Username: admin
Password: admin
AEM Consoles : Now, we have AEM server up and running, We will see
important consoles one by one.
AEM Home Screen: Here, we can find icons for different consoles in
AEM. It looks like as follows -
AEM Sites Console: This console will display the pages of the websites
that we will create.
Localhost:4502/sites.html/content
Felix Console: This console is the one where you can see all the OSGi
bundles — both out of the box and your custom ones. It has various
other consoles which we will see gradually.
Localhost:4502/system/console/bundles
CRX/DE: CRX DE stands for Content Repository eXtreme Development
Environment. It is an implementation of JCR and here we can see the
nodes and properties. We can also develop code here.
Localhost:4502/crx/de
There are many other consoles in AEM, but these are the most important and
a developer interacts with them frequently.
The development team has to develop the components once, and then they
can be used multiple times on any page.