Properties

The AEM Demo Machine is delivered as an ANT project. As with all ANT scripts, there's a set of default properties delivered within the build.properties file.

These default properties can be overridden at runtime, or persisted in a personal configuration file (/conf/build-personal.properties).

When using the Graphical User Interface, navigate to New > Demo Options to view and to override the default properties.

• The "Save" option persists your personal overrides into the /conf/build-personal.properties file
• The "Load" option allows to load up a set of properties as your personal overrides (e.g. for integrations
• The "Apply" option allows to set the overrides in memory only, without persisting them permanently

When using ANT via the Command Line Interface (CLI), the standard -D Java argument allows to set the properties at runtime. Please refer to the [examples](Command Line Samples).

There's plenty of properties, the following ones are the most important. Some properties come with a .help property to describe what they intend to provide. These descriptions can be found in the last column of the Demo Properties screen in the GUI.

Property	Default Value	Description
demo.build	snapshot	The name of your demo, which results in a folder created under ./dist/demos for your demo environment. You can setup multiple demo environments, all with their own name. Although you can setup multiple demo configurations, only one can be running at the same time.
demo.type	publish	This property determines the number of AEM instances that will be installed for your demo configuration. There are 3 supported values, resulting in one, two or three AEM instances being setup (author, publish, farm). For AEM Communities demo scenarios, the default "publish" configuration is highly recommended.
demo.jar	snapshot	This property determines the name of the AEM .jar file to be used, with a matching file in the /dist/bin folder of the demo machine. Do not add the .jar suffix to this property (e.g. snapshot, aem61, aem60...)
demo.servicepack	true	This property determines if a service pack needs to be installed when running the install target. In order to get a service pack installed (e.g. AEM 6.0 SP1), just place the service pack .zip file in the same directory as the main AEM jar file, with the same name and the -sp suffix. For instance, if your AEM jar file is name aem60.jar, just rename the service pack to aem60-sp.zip. install Service pack are installed before the first server startup, hence no server restart is needed.
demo.store	crx3	This property determines the Micro Kernel to be used for AEM6.x demo configurations. There are 3 supported values: crx3, crx3mongo, crx3rdb
demo.srp	JSRP	This property determines where to store the User Generated Content. There are 3 supported values: JSRP for JCR storage, MSRP for MongoDB storage and indexing in SOLR, ASRP for cloud based storage (SaaS) - aka the AEM Communities Extension
demo.emailserver	false	This property determines whether to automatically start the James SMTP/POP email server with your demo machine
demo.communities.enablement	false	This property determines whether the "enablement" features should be fully enabled, which requires the underlying infrastructure to be in place first (MySQL specifically) install Requires MySQL to be setup (see infrastructure and download_scorm targets)
demo.addons.*	none	These properties allow to configure which add-ons are automatically selected when creating a new demo environment
demo.admin.*	none	This property allows to configure the first name, last name, short bio, password and profile for the admin user when you build a new environment