Enonic XP, system modules and 3rd party modules can easily be configured using the files in $XP_HOME/config/ directory.

When changing files ending with .cfg, their respective modules will automatically be restart with their new configuration. Files ending with .properties require a full restart of Enonic XP to be applied. In a clustered environment each node must be re-started.

System Configuration

The default are listed below.

# Installation settings
# = demo

# Configuration FileMonitor properties
felix.fileinstall.poll = 1000
felix.fileinstall.noInitialDelay = true

# Remote shell configuration
# = = 5555 = 2 = 0

# Initial http service properties
org.osgi.service.http.port = 8080
org.ops4j.pax.web.session.timeout = 1440
org.ops4j.pax.web.session.cookie = JSESSIONID

Virtual Host Configuration

Virtual hosts are configured in the file com.enonic.xp.web.vhost.cfg and is automatically updated on changes. A sample virtual host configuration is listed below.

enabled = true = localhost
mapping.a.source = /status/a = /full/path/status/a =
mapping.b.source = / = /portal/master/ =
mapping.admin.source = /admin = /admin

In this example file, three mappings are configured.

Host-name to match.
Requested path to match.
Path to which the request is sent.

In the second example, mapping b, a site is mapped to the root of the URL, which would be normal in production environments.

In the third example, the admin site is mapped to