CoreMedia Operations Basics, Version 7.5.45-10
Chapter 4. Basics of Operation | 4.4. Configuration of CoreMedia Applications

CoreMedia applications are configured with Java properties files with the ending .properties. The encoding is ISO-8859-1. Each line stores a single property with the format key=value. The hash sign (#) is used for labeling comments, and the backslash (\) is used as escape character.

Each application of the CoreMedia system has one or more relevant property files where the operation of the application can be configured.

The locations of properties files for CoreMedia applications are (depending on the particular application):

Web applications:

Command-line tools:

The manuals of the applications contain descriptions of how to use the relevant property file(s) to configure each CM application.

Most web applications also offer the possibility to configure properties via JNDI, so that you can leave the WAR files untouched and for example define properties in the context.xml of the Tomcat installation. For details see the CoreMedia Digital Experience Platform 8 Developer Manual.

Besides directly editing the property files configuration might also be done at Runtime via JMX. For details about what can be configured please consult the manuals of the applications. For more general details about JMX see Section 4.9, “JMX Management”.

	Note
	Windows Paths in Java Properties Files When you configure a Windows paths in a property file, you have to escape a backslash with a second backslash in the path. This applies especially to paths for an importer inbox path. For more details about writing property values, see the Javadoc for the load() method in the java.util.Properties Java class.