Set up a Local AEM Development Environment

To set up a local AEM development environment, you will need the following prerequisites:

Computer with a supported operating system such as Windows, macOS, or Linux.
Java Development Kit (JDK) version 8 or above installed on your computer.
Apache Maven build tool installed on your computer.
Adobe Experience Manager software downloaded from Adobe website.
Knowledge of Java programming language, web development, and AEM architecture.

Make sure to check the system requirements for the specific version of AEM you will be installing.

Standalone installation

A standalone installation of Adobe Experience Manager (AEM) is a single-instance installation of AEM that runs on a single server. It is suitable for development, testing, and small-scale production deployments.

The standalone installation of AEM consists of the following components:

AEM Jar file: The core AEM software that is packaged as a jar file.
Quickstart: A script that runs the AEM instance.
Configuration files: The configuration files required to run AEM, including the web.xml and sling.properties files.

To perform a standalone installation of AEM, follow these general steps:

Download the AEM jar file from Adobe website.
Install the Java Development Kit (JDK) and Apache Maven build tool on your computer.
Set up the AEM environment by editing the configuration files and setting up the required environment variables.
Run the Quickstart script to start the AEM instance.
Access the AEM author and/or publish environments through a web browser.

The standalone installation of AEM is a simple and quick way to set up a local development environment for AEM. However, it is not suitable for larger-scale production deployments, which require a more complex architecture.

Port Number

In the context of AEM installation, port numbers refer to the numerical values assigned to different network communication protocols used by AEM. These protocols include HTTP, HTTPS, and the Apache Sling Resource Resolver, among others.

During the installation of AEM, you may be prompted to specify port numbers to use for various services. For example, you might be asked to specify the port number for the AEM author environment, or for the Apache Sling Resource Resolver.

Choosing the right port numbers is important to avoid conflicts with other applications running on your system. By default, AEM uses the following port numbers:

Author environment: 4502
Publish environment: 4503
Apache Sling Resource Resolver: 8888

It is possible to change these default port numbers during the AEM installation process or after installation by editing the relevant configuration files. However, if you do decide to change the default port numbers, be sure to choose values that are not already in use by other applications on your system.

Setting Run Modes in AEM

In Adobe Experience Manager (AEM), run modes are used to define the configuration and behavior of an AEM instance. Run modes allow you to specify different sets of configurations for different environments, such as development, testing, or production.

To set run modes in AEM, follow these steps:

Open the crx-quickstart/conf directory in your AEM instance.
Create a new file called sling.runmodes.
In the sling.runmodes file, specify the run modes you want to use separated by commas. For example, you might specify dev for the development environment, test for the testing environment, and prod for the production environment.
Save the sling.runmodes file.
Restart the AEM instance.

After restarting the AEM instance, the run modes you specified will be used to load the appropriate configurations. For example, if you specified dev as a run mode, AEM will load the configuration files associated with the development environment.

You can also set run modes using system properties, which can be specified as JVM parameters when starting the AEM instance. To do this, use the -Dsling.run.modes= parameter followed by a comma-separated list of run modes. For example: -Dsling.run.modes=dev,test. This will set the run modes to dev and test.

Share on Facebook

Save