Configuration changes
When you change configuration objects, take the following points into account:
-
IDM’s authoritative configuration source is its repository. Although the JSON files provide a view of the configuration objects, they do not represent the authoritative source.
Unless you have disabled file writes, IDM updates JSON files after you make configuration changes over REST. You can also edit those JSON files directly. For information on disabling file writes, refer to Disable automatic configuration updates.
-
While running, IDM recognizes changes to JSON files. The server must be running when you delete configuration objects, even if you do so by editing the JSON files.
-
The
openidm.config.file.encodingproperty sets the encoding to be used when reading from, or writing to configuration files. The default encoding is UTF-8. Acceptable values include:-
US-ASCII
-
ISO-8859-1
-
UTF-8
-
UTF-16BE
-
UTF-16LE
-
UTF-16
All configuration files are encoded using UTF-8 by default. If you change the encoding to a different character set, you must re-encode the files before you restart IDM with the new encoding. Failure to do so will result in errors on IDM startup. -
-
Avoid editing configuration objects directly in the repository. Rather, edit the configuration over the REST API, or in the configuration JSON files to ensure consistent behavior and that operations are logged.
-
By default, IDM stores its configuration in the repository. If you remove an IDM instance and do not specifically drop the repository, the configuration remains in effect for a new instance that uses that repository. You can disable this persistent configuration in your project’s
conf/system.propertiesfile by setting the following property:openidm.config.repo.enabled=falseDisabling persistent configuration means that IDM stores its configuration in memory only.