All settings and definitions are stored in the one repository and activated by setting the Run Mode.

Installation Run Modes

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:

author

publish

samplecontent

nosamplecontent

These are two pairs of mutually exclusive run modes; for example, you can:

define either author or publish, not both at the same time

combine author with either samplecontent or nosamplecontent (but not both)

Caution:

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.

Customized Run Modes

You can also create your own, customized, run modes. These can be combined to cover scenarios such as:

author + development

publish + test

publish + test + golive

publish + intranet

as required . . .

Customized run modes can also be selected at each startup.

Using samplecontent and nosamplecontent

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:

The samplecontent run mode will install this content (the default mode).

The nosamplecontent mode will not install the sample content.

The nosamplecontent run mode is designed for production installations.

Defining configuration properties for a run mode

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:

config
Applicable for all run modes

config.author
Used for author run mode

config.publish
Used for publish run mode

config.<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.

Note:

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.

Defining additional bundles to be installed for a run mode

Additional bundles that should be installed for a particular run mode can also be specified. For these definititions, install folders are used to hold the bundles. Again the run mode is indicated by a prefix:

install.author

install.publish

These folders are of type nt:folder and should contain the appropriate bundle.

Starting CQ with a specific run mode

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: