System Properties
The Content Engine will use the system properties described below if they are specified.
The general method of setting system properties depends on which
application server you use. Some application servers allow you to set them
as -D
options in the application server startup
command, some read configuration files, some let you set system properties
from an administration user interface. Consult the documentation for your
application server to find out the best way to set system properties.
Some system properties are set by the
Content Engine's
ece
start-up script, so if you use this script to
start the
Content Engine,
then you can also modify the settings of these properties by editing
/etc/escenic/engine/ece.conf
. You should avoid
setting system properties in both places, since which setting will take
precedence in such cases is application server-dependent.
The following descriptions indicate which system properties are set by
the ece
start-up script.
There are sensible defaults for all system properties, so they do not necessarily need to be explicitly set.
- java.security.policy
-
Overrides the default java security configuration. Value:
[some location of your choice]/java.policy
. The filejava.policy
should be copied to the file system of the application server fromECE_CONFIG/security/
- java.security.auth.login.config
-
Overrides the default java security configuration. Value:
[some location of your choice]/jaas.config
. The filejaas.config
should be copied to the file system of the application server fromECE_CONFIG/security/
For WebLogic installations, use
[some location of your choice]/jaas-weblogic.config
. The filejaas-weblogic.config
should be copied to the file system of the application server fromECE_CONFIG/security/
- com.escenic.instance
-
The property
com.escenic.instance
will automatically have the value of the name of the host that the instance runs on if bothescenic.server
andcom.escenic.instance
are left unspecified. Set this property if you want it to a have a different value than the host name. One scenario that requires this property to be set is when you are running two application server instances on the same host. Its value should only consist of only letters, numbers, dots and hyphens.The property
com.escenic.instance
used to be theescenic.server
property. The propertyescenic.server
still works but it is deprecated. Content Engine will ensure thatescenic.server
andcom.escenic.instance
have the same value. If both are set by your configuration, Content Engine will ignoreescenic.server
and assign your value ofcom.escenic.instance
to theescenic.server
property. - com.escenic.instance.class
-
The property
com.escenic.instance.class
defaults to the basename of the the EAR file at assembly time. Usually, this is "engine" since the EAR file name isengine.ear
. The name is taken from the server class of the EAR file.If you copy the
default.properties
(which describes the defaultengine.ear
) and have more than one server class it will be possible to use the name of your server class in your configuration files using the${com.escenic.server.class}
syntax.Assembly tool will create one ear file for every property file that it finds in the
serverclasses
directory. Each of these will run withcom.escenic.instance.class
property set to the ear file name.Only set up this property if you want it to a have a different value than the ear filename (the server class name). It should only consist of letters, numbers, dots and hyphens.