Enonic XP, system modules and 3rd party modules can easily be configured using the files
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.properties are listed below.
# # Installation settings # xp.name = demo # # Configuration FileMonitor properties # felix.fileinstall.poll = 1000 felix.fileinstall.noInitialDelay = true # # Remote shell configuration # osgi.shell.telnet.ip = 127.0.0.1 osgi.shell.telnet.port = 5555 osgi.shell.telnet.maxconn = 2 osgi.shell.telnet.socketTimeout = 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
is automatically updated on changes. A sample virtual host configuration
is listed below.
enabled = true mapping.a.host = localhost mapping.a.source = /status/a mapping.a.target = /full/path/status/a mapping.b.host = enonic.com mapping.b.source = / mapping.b.target = /portal/master/enonic.com mapping.admin.host = enonic.com mapping.admin.source = /admin mapping.admin.target = /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