To access the dicom configuration, inject a DicomConfiguration bean with CDI like

@Inject
DicomConfiguration config;

DicomConfiguration is the primary interface for configuration access. It is type-safe and its implementation is supposed to perform thorough validation when persisting changes. Always give this interface the preference over other access methods.

Build dedicated APIs on top of DicomConfiguration to wrap up some special configuration functionality.

For special cases, one can inject DicomConfigurationManager and call .getConfigurationStorage() on it to obtain an instance of Configuration. This will allow a not-so-safe low-level access to the configuration. Although the validation of changes will still be enforced, it is more probable to introduce inconsistencies while using this layer. The usage of Configuration interface for making configuration changes is therefore discouraged.

The valid direct use-case of Configuration is issuing custom queries (i.e. that rely on some AE/Device/HL7 extensions)

Migration allows to use both high-level type-safe API (DicomConfiguration) and low-level unsafe API (Configuration). Migration runner (to be introduced) will call all the migration scripts in proper order and provide the instances of DicomConfiguration and Configuration for them.

• How to create a custom AE extension and use it in a StoreService decorator