In eXo Platform, a lot of configuration options are customizable via properties. If you want to change the default configurations of eXo Platform, simply do as follows:
Create your own
.properties file that must be named
This file contains all configurations to be customized.
.properties file has no header, so you do not need to preserve the header.
You can refer to
exo-sample.properties that is provided by default but has no effect on the eXo Platform configuration.
This default file exposes all properties you can override or extend, but in comments (#).
Instead of creating new, you can rename
then make changes on your needed properties and remove their comments.
Add configurations to be customized in
exo.properties. Pay attention to the followings:
Each property is defined on one line that conforms to the syntax: property_name=property_value.
Order of the property lines does not take any effect, but it is important that you use the exact key of each property in
that is already exposed in
exo-sample.properties or listed in this chapter.
The usage of properties and their keys are detailed in the later sections.
The text before the equal sign is the key that you should not change and the text after the equal sign is the property's value that you can edit.
Save and restart the eXo Platform server for your changes to take effect.
Besides the capability of customizing configurations in
you can follow in another way by adding a system property, either in
bin/standalone-customize.sample.conf(.bat), or in any your custom scripts.
See Customizing environment variables for detailed instructions.
There are some configuration properties that will not be configurable by the system property but in
exo.properties only, including: