AEM Local Set Up notes
– Web Development
Some Notes about AEM Local Environment Setups
*There are already tons of detailed setup guidelines online, so I won’t cover the step-by-step stuff here.
More likely, this is the guide log page that may fetch some missing gaps between tutorials out there.
Setting up Java and Maven on your machine
First of all, you have to set Java 11 or above. Either you can go to the oracle website or grab the open JDK. I personally go to open JDK because I don’t bother to make my credentials with oracle.
If you are on a mac, you can try to install java through homebrew. I downloaded the open JDK for windows and extracted those /bin sources into the folder I wanted to locate.
Here is the detailed documentation explaining it. I don’t bother to go to this level. For the simpler way, I added the path of the JDK location to the path through environment variables.
Installing and using OpenJDK 11 for Windows OpenJDK 11 | Red Hat Customer Portal
In order to check if java is well installed, run the command below. For the windows, it’s –version.
java -version
Place your jar files where you will place your AEM project.
Generate two folders, ‘author’ and ‘publish’.
Run the script below within your author folder through the terminal or command prompt.
java -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n -jar aem-author-p4502.jar -gui
Once you run the command above, wait a couple of minutes…or longer, well - depending on your device’s performance.
You will see the login prompt. The default credential is admin and admin. It sounds dodge, but it is what it is.
After that, you need to set the maven installed. If you only need to do content writing, this running step will be enough, but most likely, you will either work on developing an AEM system or get involved in some front-end works for AEM themes. In either case, you need to set the bundle packages installed with your designated AEM architecture setups - which can be guided by leading AEM backend developers or whatsoever.
The versions of the main bundle dependency kits here are the minimum. You may need to install higher versions depending on what you have been told to do so.
I am staying with java 11 and maven 3.3.9 for now.
https://archive.apache.org/dist/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.zip
I normally use the Mac and still have a bit of confusion on Windows. The maven was not loaded but solved after adding ‘JAVA_HOME’ extra top of ‘PATH’ addition. For ‘JAVA_HOME’, do not go deeper to ‘/bin’ folder. That did not connect the Maven to the Java.
mvn --version
After typing this, things seem to set up well.](<### Some Notes about local environment setups
There are already tons of detailed setup guidelines online, so I won’t cover the step-by-step stuff here.
Plus, those documents from Adobe will be very helpful.
With reading this, most of the stuff will be covered - however, as Adobe usually dump all vast contexts on one page, you may get lost in the middle. This doc provides a bit of support if you are doing so.
This is likely the journey log page with a bit of a guide that may fetch some missing gaps between tutorials out there.
First of all, you have to set Java 8 or above. Either you can go to the oracle website or grab the open JDK. I personally go to open JDK because I don’t bother to make my credentials with oracle.
If you are on a mac, you can try to install java through homebrew. I downloaded the open JDK for windows and extracted those /bin sources into the folder I wanted to locate.
Here is the detailed documentation explaining it. I don’t bother to go to this level. For the simpler way, I added the path of the JDK location to the path through environment variables.
Installing and using OpenJDK 11 for Windows OpenJDK 11 | Red Hat Customer Portal
or grab it from the open jdk archive website.
In order to check if java is well installed, run the command below. For the windows, it’s –version.
java -version
Place your jar files where you will place your AEM project root folder.
Generate two folders, ‘author’ and ‘publish’. Copy the jar file and place the file in each folder.
Run the script below within your author folder through the terminal or command prompt.
java -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n -jar aem-author-p4502.jar -gui
Once you run the command above, wait a couple of minutes…or longer, well - depending on your device’s performance.
You will see the login prompt. The default credential is admin and admin. It sounds dodge, but it is what it is.
After that, you need to set the maven installed. If you only need to do content writing, this running step will be enough, but most likely, you will either work on developing an AEM system or get involved in some front-end works for AEM themes. In either case, you need to set the bundle packages installed with your designated AEM architecture setups - which can be guided by leading AEM backend developers or whatsoever.
The versions of the main bundle dependency kits here are the minimum. You may need to install higher versions depending on what you have been told to do so.
I am staying with java 11 and maven 3.3.9 for now.
https://archive.apache.org/dist/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.zip
If you see something after typing this, you set all the required environment setups well.
1mvn -v (or --version)
Extra step for maven:
On windows, sometimes “mvn: command not found” happens. (Did not have similar issues on Mac)
To make triple-sure, you can follow this way.
If you like to follow more details about archetypes, this tutorial from Adobe is good to go.