AEM Installations

The AEM software package is available in two forms:
cq-quickstart-6.3.0.jar: A standalone executable jar file that includes everything needed to get up and running.
cq-quickstart-6.3.0.war: A war file for deployment in a third-party application server.

Default behaviour when installing AEM in an Application Server
AEM comes as a single war file to deploy.
If deployed the following will happen by default:
the run mode is author
the instance (Repository, Felix OSGI environment, bundles, etc.) is installed in ${user.dir}/crx-quickstart where ${user.dir} is the current working directory, this path to crx-quickstart is called sling.home
the context root is the war file name e.g: aem-6

Configuration
You can change the default behavior in the following way:

• run mode: configure the sling.run.modes parameter in the WEB-INF/web.xml file of the AEM war file before deployment sling.home: configure the sling.home parameter in the WEB-INF/web.xml file of the AEM war file before deployment
• context root: rename the AEM war file

When using an EAR file, the web.xml file is located in EAR/WAR/Web-Inf.

Publish installation
To get a publish instance deployed you need to set the run mode to publish:

• Unpack the WEB-INF/web.xml from the AEM war file
• Change sling.run.modes parameter to publish
• Repack web.xml file into AEM war file
• Deploy AEM war file

Standalone installation
There are various rules to be followed when renaming the quickstart jar file:

• When you rename the file, it must start with cq; as in cq5-publish-p4503.jar.
• It is recommended that you always prefix the port number with -p; as in cq5-publish-p4503.jar or cq5-author-p6754.jar.

This is to ensure that you do not need to worry about fulfilling the rules used for extracting the port number:

• the port number must be 4 or 5 digits
• these digits must come after a dash
• if there are any other digits in the filename, then the port number must be prefixed with -p
• the “cq5” prefix at the beginning of the filename is ignored

cq-<instance-type>-p<port-number>.jar
Starting and Stopping
Once AEM has unpacked itself and started up for the first time, double clicking on the jar file in the install directory simply starts the instance, it does not re-install it.

To stop the instance fom the GUI, simply click the on/off switch on the desktop application window.
You can also stop and start AEM from the command line. Assuming you have already installed the instance for the first time, the command-line scripts are located here:
<aem-install>/crx-quickstart/bin/
This folder contains the following Unix bash shell scripts:
start: Starts the instance
stop: Stops the instance
status: Reports the status of the instance
quickstart: Used to configure start information, if necessary.

Different ways to start AEM
1) Double click jar
2) bin/start.bat – First time we cannot use this as this folder doesn't exist
3) Execute through command prompt for jar and bat file through command prompt we can allocate memory

While starting AEM
1) Jetty starts in the background
2) Approx. 400 osgi bundle are existing and all the osgi should be active then only AEM will function properly

UNPACKED INSTALL DIRECTORY
When the quickstart jar is launched for the first time it will unpack itself into the same directory under a new sub-directory called crx-quickstart. You should end up with the following:

• <aem-install>/
• license.properties
• cq-quickstart-6.1.0.jar
• crx-quickstart/
• app/
• bin/
• conf/
• launchpad/
• logs/
• monitoring/
• opt/
• repository/
• eula-de_DE.html
• eula-en_US.html
• eula-fr_FR.html
• eula-ja_JP.html
• readme.txt