Adobe Experience Manager (AEM) is part of the Adobe Marketing Cloud. It's initially a content management platform but now has expanded to
AEM can be installed as a standalone executable JAR file or through web application servers, such as JBoss and WebSphere, as a WAR file.
AEM 6.2 needs at minimum the following in order to run
The standalone installation is the simplest. It only requires quickstart jar file. This is provided by Adobe to you or your company.
Simply double click on the jar file and AEM will start. This might take a while on the initial install (~10 minutes).
Once the initial setup has been completed, a browser window will open (
http://localhost:4502 ). You can login using the default admin credentials (user:
admin / pass:
admin ). The initial login will prompt you to enter the license details.
By default, AEM will be accessible through HTTP at port 4502. If port 4502 is unavailable, it will be set to one of these ports (in order of preference):
To set the port to a different port number, there are two options:
java -jar aem-quickstart.jar -p 6754)
Run modes are identifiers that allow to differentiate AEM instances (e.g. development, test, production, authoring, publish). Run modes for an instance can be configured by (in order of resolution):
java -jar cq-publish-p6754.jar -r publish)
publishrun modes using the following template
AEM can be deployed in application servers such as
Websphere . You simple need to deploy a
war file provided to you by Adobe.
sling.run.modes property in