4.1. CoreMedia CMS Directory Structure

CoreMedia applications come as simple applications or as web applications. Both have a standard directory structure that will be described in the following. Other - application specific - directories, are described in the corresponding application manual.

CoreMedia applications

A CoreMedia application, the Server Utilities for example, has the following directories:

  • ./bin: Start scripts (see Section 4.3, “Starting the Applications”) for Unix (cm) and Windows (cm.exe, cmw.exe) as well as the start scripts of the individual CoreMedia utility programs and the Site Manager.

  • ./lib: Runtime resources like Java JAR files and DLLs.

  • ./classes: Optional local classes. Note: The directory does not exist in the standard installation. It can contain customer-specific extensions.

  • ./config/<component>: XML configuration files of the application.

  • ./properties/corem: CoreMedia CMS configuration files in Java properties format.

  • ./var/log: log files of the CoreMedia applications (see Section 4.7, “Logging”).

  • ./var/run: runtime data (such as Process ID).

  • ./var/tmp: temporary data.

CoreMedia web application

A CoreMedia web application, the Content Application Engine or the Content Server for example, is deployed in a servlet container. The web applications have some of the following sub directories in its WEB-INF directory:

  • ./config/<application>: XML configuration files of the application.

  • ./properties/corem: CoreMedia CMS configuration files in Java properties format.

  • ./lib: Runtime resources like Java JAR files and DLLs.

  • ./spring: Spring configuration files of the web application.

Prev Up Next
 Home