# Configuration management

The Deployment Template implements a configuration management approach based on a simple business process.

The template requires that all configuration files be managed in a single location. That is, files are either maintained by Oracle Endeca Workbench or by Developer Studio, but multiple sources of configuration for the same file are not allowed. Given this rule, the template assumes that all files are maintained in Developer Studio with the exception of those explicitly identified (in the `ConfigManager` component definition) as being maintained in Oracle Endeca Workbench. When creating the complete configuration of the application, the Deployment Template takes the Developer Studio copy of each configuration file, overwriting those that are to be maintained in Oracle Endeca Workbench with the copies downloaded from the Workbench.