Upgrading 10.2 to 10.3

Database schemas for the infrastructure features must be checked with each new Cadenza version and updated if necessary. The Database Migration Tool is available for this purpose.
It is strongly recommended to make a backup before using this tool, as the structures of the schemas may change!

Branding and Customizing

Configuration File Changes

Removal of allow and deny export settings in core config

The settings of export type-specific restrictions, defined in the elements exportAllowList and exportDenyList, have been removed as they are no longer supported.

New default language in openrouteservice config

The service > tuning > language setting now uses the Cadenza language by default instead of "de" to support a more consistent user experience.

In practice, this change will probably not require any action, but you might want to check that the routing results are displayed correctly: If not, you can revert to "de".

Breaking Changes in temporaldataanimation config

If the Gis_Temporal_Data_Animation plugin is activated, the maximumDisplayPointCount > default setting must be redefined, if present. To migrate, the maximum number of data points displayed as tail behind a moving object must be configured with the new maximumPointCountInTail setting. The maximumDisplayPointCount has to be removed (otherwise Cadenza will not start).

GPX-import in plugins.xml config

To re-enable the GPX-import you need to activate the plugin GPX because it is not longer included in the plugin Import_Temporal_Data.

Removal of per-Secret Encoding Settings

After the introduction of a global option whether secrets are encoded, per-setting options are now removed. All of these now use the global setting secretHandling in core settings instead. If that is not configured, all secrets are considered encoded. This affects:

auditlogging config

When configuring an appender with class HibernateAuditLogAppender, a param with name value passwordEncrypted is no longer supported.

mailclient config

The settings outgoingServer > authorization > login > password > encrypted and outgoingServer > authorization > plain > password > encrypted have been removed.

monitoring-publishers config

The setting authentication > password > encrypted has been removed.

userpreferences config

The setting database > password > encrypted has been removed. At this opportunity, the already-deprecated setting database > connectionIdleTimeout has been removed, too.

what3wordsweb config

The settings services > service > apiKey > encrypted and services > service > authentication > password > encrypted have been removed.

repository list

The setting databaseRepository > password > encrypted has been removed. At this opportunity, the already-deprecated settings databaseRepository > connectionIdleTimeout and databaseRepository > polling have been removed, too.

If, so far, your configuration varied so that some secrets were specified in their encoded form, while others were present verbatim, you will have to standardize on one approach.

In case all secrets were present in their encoded form already, and you are using the XML configuration approach, you should only have to remove the encrypted="true" attributes where they are present.

When using configuration using YAML or environment variables, leaf value fields must be merged on their parent. For example,

cadenzaconfig:
  userpreferences:
    database:
      password:
        encrypted: true
        value: "aabbccdd"

becomes

cadenzaconfig:
  userpreferences:
    database:
      password: "aabbccdd"