All files that sfCRM needs are created and maintained under this directory. sfCRM does not create any files or directories outside this structure.

This directory and its sub-directories contain auxiliary (non-database) data created by the application.

This directory contains files used by the entire organization, such as file attachments and email templates.

This directory includes one sub-directory for each user. The sub-directories maintain files for each individual user, such as email messages (in their full SMTP format) and email attachments.

The sfCRM backup manager creates daily backups. Each backup is created as a few zip files in a separate directory under the backups directory. This example shows one such backup.

The bin directory contains applications used for starting and stopping sfCRM, and for upgrading the database to new versions as they become available.

The config directory contains a few configuration files. The file config.txt maintains application-specific configuration. The file jettyConf.xml configures the built-in web server, Jetty. The file serverParams.txt (currently used only under Windows) configures the application's port number, memory requirement and SSL enablement.

The data directory and its sub-directories contain the application's databases. If the application is configured to use the Mckoi database engine (as is most often the case), this directory's contents include all of the critical transactional data.

This directory contains the Mckoi database files.

The doc directory contains third-party license files, support documentation, release notes, etc.

The web server request logs are stored in the logs directory. Here you will also find the file event-log.txt that contains entries for application-level events.

Here you will find the app.jar file, containing the entire sfCRM application. The file appLicense.jar contains license information for the application. Other Java jar files for JDBC and web-server support are also included here.