What’s New in Cadenza 2024 Summer (10.0)

Installing

  • Installation from an archive file has been simplified: It is no longer necessary to run an installer. After unpacking, the Cadenza server can be started directly by executing the start script. Further information can be read at Installation From an Archive

Supported Data Sources

Vector Tile Services are supported as a new data source. Layers from Vector Tile Services can be integrated into map views. Vector Tile Services can be added as a data source in the Management Center.

Configuring Cadenza

  • From version 10.0.185: There is a new element <credentials> in repositorydatasourcetemplates-config.xml configuration file. For more information see Data Source Templates for Using in Management Center.

  • There is a new runtime configuration option called CADENZA_EXIT_ON_STARTUP_ERROR which controls whether Cadenza should terminate the Java process when a startup check fails or whether it should throw an exception. The former makes for a much more pleasant user experience as the log file will contain exactly the failing tests and what you need to fix at the end, the latter option is the old behaviour and should be used when deploying Cadenza alongside other applications in an application server. The new option is disabled by default. We have explicitly enabled it for our distribution and our docker image. For more information see Environment Variables, System Properties and Other Runtime Configuration Options.

  • There is a new runtime configuration called net.disy.cadenza.web.contextpath that is used in our default Tomcat configuration with which you can change the context path under which Cadenza will be available. For more information see Environment Variables, System Properties and Other Runtime Configuration Options.

  • There is a new cache UserDataCache which caches user data like mail and real name that are received from services such as LDAP and Keycloak. For more information see Caching.

Branding and Customizing

Operating Cadenza

  • We now support monitoring for all database connections. We added a new tag connectiontype to distinguish between them. In addition, database connection metrics will no longer contain the '_datasource' but an '_dbpool' infix. Further information can be read at Monitoring Metrics

  • We now document our Status endpoint that can be used to monitor the health of a Cadenza instance. For more information see Status Endpoint.