Installing AEM

Rename the quickstart JAR file to aem-author-4502.jar

aem Application Name

author WCM Mode it will run, author or publish
4502 Port number it will run (any available port is acceptable)

Note: If no port no is provided then AEM will select first available port from the
following list:
1. 4502
2. 8080
3. 8081
4. 8082
5. 8083
6. 8084
7. 8085
8. 8888
9. 9362
10.Random
There are two ways to install AEM, graphical and through command line. The
latter is more powerful because user has the possibility to provide additional
performance tuning parameters to the JVM. In command line we can start AEM by
increasing heap size, which will increase the performance.
java Xmx1024m jar aem-author-4502.jar gui
-Xms Assigns the initial heap size
Default value for JVM running in 32-bit machine is 64 MB and 64-bit machine is 83
MB
-Xms512m sets initial heap size to 512 MB
-Xmx Assigns the maximum heap size
Default value for JVM running in 32-bit machine is 64 MB and 64-bit machine is 83
MB
-Xmx1024m Sets maximum heap size to 1024 MB
NOTE: To run AEM, it is recommended to allocate at least 1024 MB heap size
RUN MODES
Installation Run Modes are used during installation and then they fixed for
entire lifetime of the instance, they cannot be changed.
Installation run modes provided are

author
publish

samplecontent
nosamplecontent

Define either author or publish, not both at the same time.

Combine author with either samplecontent or nosamplecontent, not both.
Customized run modes are:

author + development
publish + test
publish + test + golive
publish + intranet

The samplecontent run mode will install this content(default)

The nosamplecontent run mode will not install the content.
Note: nosamplecontent run mode is designed for production installation.
CONFIGURATION PROPERTY FOR A RUN MODE
config Applicable for all run modes.
config.author Applicable for author run mode.
config.publish Applicable for publish run mode.
config.<runmode> - Used for applicable run mode.

We can check current run modes by navigating into /system/console and then by
checking status sling settings
Run Modes = [test, crx3, samplecontent, publish, crx3tar]

SPECIFIC RUN MODES

1.
2.
3.
4.

sling.properties
r option
System properties (D)
Filename detection

Using sling.properties sling.run.modes=author

Using the r option java jar aem-author-4502.jar r author dev
Using system properties -Dsling.run.modes=publish, prod
Using File name detection aem-author-4502.jar or aem-publish-4503.jar

DEBUG MODE

To start a server in debug mode we need to add some parameter in start.bat file.
From command prompt also we can start the server in debug mode by using the
following command.
java Xmx1024m Xdebug
Xrunjdwp:transport=dt_socket,server=y,address=9000, suspend=n jar
aem-author-4502.jar

LOG FILES
Log files can be found inside <crx-quickstart>/logs
Apache sling logging logger configuration is used to configure the root logger. This
defines the global setting for logging in AEM.
AEM uses the following to write the log messages to file:
1. An OSGi service(logger) writes a log message. Apache Sling Logging
Configuration
2. A Logging Logger takes this message and formats it according to
specification. Apache Sling Logging Logger Configuration
3. A Logging Writer writes all these messages into the physical file that we
have defined. Apache Sling Logging Writer Configuration

Apache Sling Referrer Filter To address known security issue with CSRF in CRX
and WebDAV and Apache Sling need to be configured in Referrer Filter.
The referrer filter service is an OSGi service that allows us to configure:

Which http method should be filtered

Whether an empty referrer header is allowed
And a white list of servers to be allowed in addition to the server host.

Apache Sling Resource Resolver Factory Configure central aspects of sling

resource resolution
URL mapping
Mapping Location