Note

This documentation is for OMERO 5.2. This version is now in maintenance mode and will only be updated in the event of critical bugs or security concerns. OMERO 5.3 is expected in the first quarter of 2017.

Properties

Under the etc/ directory in both the source and the binary distributions, several files are provided which help to configure OMERO.server:

etc/omero.properties

Our central configuration file with all defaults

etc/hibernate.properties

Required by Hibernate since some properties are only configurable via a classpath:hibernate.properties file

etc/logback.xml

Logging configuration

etc/build.properties

The properties that you will most likely want to change

etc/local.properties

Local file overriding etc/build.properties (used by build only)

The most useful of the properties are listed in a glossary.

During the build, these files get stored in the blitz.jar and are read-only. On creation of an OmeroContext, the lookup for properties is (first wins):

• Properties passed into the constructor (if none, then the default properties in config.xml)
• System.properties set via “java -Dproperty=value”
• Configuration files in order listed.

This ordering is defined for the various components via “placeholder configurers” in:

• components/server/resources/ome/services/services.xml

Once configured at start, all values declared in one of the mentioned ways can be used in Spring configurations via the syntax:

<bean id=…>
  <property name="mySetter" value="${property.name}"/>
</bean>