Changes between Version 1 and Version 2 of ConfigOverride
- Timestamp:
- May 25, 2011, 2:07:32 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ConfigOverride
v1 v2 11 11 == Overview == 12 12 13 In order to permit deployment of a Geonetwork instance to multiple environments and assist in development this proposal adds the ability to configure geonetwork for multiple target deployment platforms (for example, test and production) with a minimum of duplication and allow configuration selection to be chosen via System properties or ServletConfig/Context parameters.13 In order to permit deployment of a Geonetwork instance to multiple environments and assist in development this proposal adds the ability to configure geonetwork for multiple target deployment platforms (for example, test and production) with a minimum of duplication and allow configuration selection to be chosen via System properties or !ServletConfig/Context parameters. 14 14 15 15 === Proposal Type === … … 34 34 35 35 == Proposal == 36 As such I propose a new method for handling multiple deployment platforms. The standard configuration files contain the default settings and multiple override configurations can be defined to override certain parts of those defaults. The override that is applied can be selected via one of System properties, ServletConfig initial parameters orServletContext initial parameters. So depending on the server/environment where the geonetwork is deployed a different configuration can be selected with minimal duplication of configuration.36 As such I propose a new method for handling multiple deployment platforms. The standard configuration files contain the default settings and multiple override configurations can be defined to override certain parts of those defaults. The override that is applied can be selected via one of System properties, !ServletConfig initial parameters or !ServletContext initial parameters. So depending on the server/environment where the geonetwork is deployed a different configuration can be selected with minimal duplication of configuration. 37 37 38 The parameter/property that is checked for the definition of the override file is jeeves.configuration.overrides.file. If the property is not found then the no overrides are applied to the default configuration.38 The parameter/property that is checked for the definition of the override file is '''jeeves.configuration.overrides.file'''. If the property is not found then the no overrides are applied to the default configuration. 39 39 40 40 41 41 The following is an example of a override file: 42 42 {{{ 43 #!xml 43 44 <overrides> 44 45 <!-- properties allow some properties to be defined that will be substituted --> … … 96 97 </file> 97 98 </overrides> 99 }}} 98 100 99 101 As this example indicates the primary tags of interest are:
