AEM 6.4 has reached the end of extended support and this documentation is no longer updated. For further details, see our technical support periods. Find the supported versions here.
Run modes allow you to tune your AEM instance for a specific purpose; for example author or publish, test, development, intranet or others.
Define collections of configuration parameters for each run mode.
A basic set of configuration parameters is applied for all run modes, you can then tune additional sets to the purpose of your specific environment. These are applied as required.
Define additional bundles to be installed for a particular mode.
All settings and definitions are stored in the one repository and activated by setting the Run Mode.
Installation (or fixed) run modes are used at installation time and then fixed for the entire lifetime of the instance, they cannot be changed.
Installation run modes are provided out-of-the-box:
These are two pairs of mutually exclusive run modes; for example, you can:
publish, not both at the same time
author with either
nosamplecontent (but not both)
When using one of the above run modes (author, publish, samplecontent, nosamplecontent), the value used at installation time defines the run mode for the entire lifetime of that installation.
For these run modes you cannot change them after installation.
You can also create your own, customized, run modes. These can be combined to cover scenarios such as:
as required . . .
Customized run modes can also be selected at each startup.
These modes allow you to control the use of sample content. The sample content is defined before the quickstart is built and can include packages, configurations, etc:
samplecontent run mode will install this content (the default mode).
nosamplecontent mode will not install the sample content.
The nosamplecontent run mode is designed for production installations.
A collection of values for configuration properties, used for a particular run mode, can be saved in the repository.
The run mode is indicated by a suffix on the folder name. This allows you to store all configurations in one repository as. For example:
Applicable for all run modes
Used for author run mode
Used for publish run mode
Used for the applicable run mode; for example, config
See OSGi Configuration in the Repository for further details on defining the individual configuration nodes within these folders and for creating configurations for combinations of multiple run modes.
For Installation Run Modes (e.g. author) the run mode cannot be changed after installation. However, changes to the individual configuration properties will take effect upon restart.
Additional bundles that should be installed for a particular run mode can also be specified. For these definitions, install folders are used to hold the bundles. Again the run mode is indicated by a prefix:
These folders are of type
nt:folder and should contain the appropriate bundle.
If you have defined configurations for multiple run modes then you need to define which is to be used upon startup. There are several methods for specifying which run mode to use; the order of resolution is:
When you are using an application server you can also define the run mode in web.xml.
sling.properties file can be used to define the required run mode:
Edit the configuration file:
Add the following properties; the following example is for author:
A custom run mode can be activated by using the
-r option when launching the quickstart. For example, use the following command to launch a AEM instance with run mode set to dev. ``
java -jar cq-56-p4545.jar -r dev
A system property in the start script can be used to specify the run mode.
For example use the following to launch an instance as a production publish instance located in the US:
The following two installation run modes can be activated by renaming the installation jar file before installation:
The jar file must use the naming convention:
For example, set the
publish run mode by naming the jar file:
When you are using an application server you can also configure the property:
in the file:
This is in the AEM
war file and should be updated before deployment.
See Installing AEM with an Application Server for further details.