REM system properties

REM supports the following system properties that affect its runtime behaviour:

Property Valid values (default in bold) Description

rem.nosessionlogin

true, false

If set to true, disables login from a cookie. Normally authentication tokens in a cookie will be checked when the app is reloaded and can continue to be used. Disabling this feature increases security but forces users to re-login when the app is restarted (with F5 for example.)

rem.norestart

true, false

If set to true, disables the feature that allows the administrator to restart the REM server (if started by rem.sh) from the upload certificate dialog box.

rem.home

${JETTY_HOME}

Path to the directory where REM should store its working files (Derby database, keystore, etc.)

rem.plugins.dir

${rem.home}/plugins

Path to the directory where REM should search for plugins.

rem.plugins.work.dir

${rem.plugins.dir}

Path to the directory where REM should expand plugins to.

rem.schema.update.enabled

true, false

If set to true, enables automatic database schema updates to rem_data (if required) during REM startup.

REM servlet parameters

In addition to the system properties above, REM uses the following servlet parameters to control the loading of additional configuration:

Parameter name Valid values (default in bold) Description

rem.config-file

${rem.home}/rem.properties

Path to the REM configuration file. Stores sensitive configuration properties such as the truststore configuration.

rem.config-file.password

Any sequence of printable ASCII characters i.e. characters from the range from ' ' to '~'

Password used to encrypt sensitive properties in the REM configuration file such as the truststore password.
Previous page Next page