June 04, 2021
Hola amigos 👋! In this post, we will discuss how to run a local AEM instance and what are some useful consoles in it. So, without further ado, let’s have some fun 😎.
So first things first, let’s see how can we install AEM on our local system. There are two ways to do that —
In this article, we are going to look into only the first way as it is the most popular and easier way to install AEM.
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 —
java -jar aem-author-p4502.jar -gui
Username: admin Password: admin
Congratulations 🤝! You have successfully installed AEM on your local system. You should be proud of yourself 👏.
Now, we have AEM server up and running, we can explore it and see what it offers. We will see important consoles one by one. You will get to know about rest of the consoles as you go deeper into AEM stuff.
Here, we can find icons for different consoles in AEM. It looks like as follows -
This console will display the pages of the websites that we will create. In a normal installation, a sample website called We.Retail is present. You can go ahead and play with it.
This console will display all the assets in your organization. It lets you store, update, create, or delete assets.
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.
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.
There are many other consoles in AEM, but these four are the most important and a developer interacts with them frequently.
In this short post, we did our first hands-on on AEM. It’s not very interesting but doing this is essential before getting our hands dirty with some code.
In the next post, we will set up our AEM development environment and will get familiar with some tools which are important for an enjoyable AEM development journey.
I would love to hear your thoughts on this post and would like to have suggestions from you to make this post better.
Happy Learning 😊 and Namaste 🙏.