Install local AEM Instances
Minimum requirements for installing Adobe Experience Manager:
- Installed Java Platform, Standard Edition JDK, or other supported Java Virtual Machines
- Experience Manager QuickStart file (Standalone JAR or web-application deployment WAR)
Minimum Sizing Requirements
Minimum requirements for running Adobe Experience Manager:
- 5 GB free disk space in the installation directory
- 2 GB memory
To Set up a Local AEM Development Environment:
Setting up a local development environment is the first step when developing for Adobe Experience Manager or AEM. Take the time to set up a quality development environment to increase your productivity and write better code, faster. We can break an AEM local development environment into 4 areas:
- Local AEM instances
- Apache Maven project
- Integrated Development Environments (IDE)
- Troubleshooting
Install local AEM Instances
When we refer to a local AEM instance, we are talking about a copy of Adobe Experience Manager that is running on a developer’s personal machine. All AEM development should start by writing and running code against a local AEM instance.
If you are new to AEM, there are two basic run modes can be installed: Author and Publish. The Author runmode is the environment that digital marketers will use to create and manage content. When developing most of the time you will be deploying code to an Author instance. This allows you to create new pages as well as add and configure components. AEM Sites is a WYSIWYG authoring CMS and therefore most of the CSS and JavaScript can be tested against an authoring instance.
It is also critical test code against a local Publish instance. The Publish instance is the AEM environment that visitors to your website will interact with. While the Publish instance is the same technology stack as the Author instance, there are some major distinctions with configurations and permissions. Code should always be tested against a local Publishinstance before being promoted to higher level environments.
Steps:
- Ensure Java is installed.
- Prefer Java JDK 11 for AEM 6.5+
- Java JDK 8 for AEM versions prior to AEM 6.5
- Get a copy of the AEM QuickStart Jar and a license.properties.
- Create a folder structure on your computer like the following:
Rename the QuickStart JAR to aem-author-p4502.jar and place it beneath the /author directory. Add the license.properties file beneath the /author directory.
Make a copy of the QuickStart JAR, rename it to aem-publish-p4503.jar and place it beneath the /publish directory. Add a copy of the license.properties file beneath the /publish directory.
- Double-click the aem-author-p4502.jar file to install the Author instance. This will start the author instance, running on port 4502 on the local computer.
- Double-click the aem-publish-p4503.jar file to install the Publish instance. This will start the Publish instance, running on port 4503 on the local computer.
Depending on your development machine’s hardware it may be difficult to have both an Author and Publish instance running at the same time. Rarely do you need to run both simultaneously on a local setup.
For more information see Deploying and Maintaining an AEM instance.
Install Apache Maven
Apache Maven is a tool to manage the build and deploy procedure for Java-based projects. AEM is a Java-based platform and Maven is the standard way to manage code for an AEM project. When we say AEM Maven Project or just your AEM Project, we are referring to a Maven project that includes all of the custom code for your site.
All AEM projects should be built off the latest version of the AEM Project Archetype: https://github.com/adobe/aem-project-archetype. The AEM Project Archetype will create a bootstrap of an AEM project with some sample code and content. The AEM Project Archetype also includes AEM WCM Core Components configured to be used on your project.
When starting a new project it is a best practice to use the latest version of the archetype. Keep in mind that there are multiple versions of the archetype and not all versions are compatible with earlier versions of AEM
Steps
Download Apache Maven
Install Apache Maven and ensure that the installation has been added to your command-line PATH.
- macOS users can install Maven using Homebrew
Verify that Maven is installed by opening a new command line terminal and executing the following:
Download Apache Maven
Install Apache Maven and ensure that the installation has been added to your command-line
PATH.- macOS users can install Maven using Homebrew
Verify that Maven is installed by opening a new command line terminal and executing the following:
In the past the addition of adobe-public Maven profile was needed to point nexus.adobe.com to download AEM artifacts. All AEM artifacts are now available via Maven Central and the adobe-public profile is not needed.

Comments
Post a Comment