Some Grouper properties files can have overlays so that only the changes from the defaults of the config files need to be tracked in the institution specific config file. Also, configs can be centrally stored on a server across multiple webapps or standalone Grouper applications. This is available in v2.2+ for the following config files:
- grouper.properties
- grouper.hibernate.properties
- grouper-loader.properties
- grouper-ui.properties
- grouper-ws.properties
- grouper.client.properties
In the future we can add this feature to other config files as well.
How it works
Each of the properties files has an example file, and a config file. For example, there is a grouper.example.properties, and a grouper.properties. Both of these are located on the classpath in the default package. e.g. WEB-INF/classes/grouper.example.properties and WEB-INF/classes/grouper.properties. Generally all the default settings will be located in the example config file, and only the things that are overridden are in the grouper.properties. This is a change in v2.2+ since before that all properties are in the grouper.properties, and the example file is not really used.
sdf