Skip to main content
Version: 7.2405.x.x LTS

Migration guide from LTS-2021 to LTS-2024

If you have not done so already, upgrade to the latest available version of nevisMeta for LTS 2021.

Then you can switch to the latest RR version or the new LTS 2024 version. Read the release notes of all in-between nevisMeta releases.

As part of the migration, read through the following document carefully as your setup is affected and will require action from your side. Your migration is mainly based on following documents:

Breaking Changes​

  • CHANGED: The previous bc and jcan-log logging using log4j1 is replaced by slf4j using log4j2. jcan-log is now only used by the jcan-optrace, which relies on the slf4j implementation of jcan-log (NEVISMETA-1702).

Log4j2 uses a different configuration structure than log4j1, and they are not compatible. If you are not using nevisMeta, you have to migrate the logging configuration manually. Check the default template supplied in the RPM.

nevisMeta requires a logging.yml file in the instance config directory. If it is missing, or the file is incorrectly formatted, a default configuration will log into the stdout which can be viewed in the systemd journal.

  • REMOVED: NevisSyslogAppender is no longer available. As a replacement we suggest SocketAppender. Reasons and example can be found in the Logging configuration / Syslog section in the reference guide. (NEVISMETA-1702).- NEW: The automatic reload of logging configuration is supported by using the monitorInterval property of(https://logging.apache.org/log4j/2.x/manual/configuration.html#ConfigurationSyntax). (NEVISMETA-1702).
  • EXPERIMENTAL: Response for client creation via REST service is changed for RFC 7591.
  • CHANGED: Response for client creation via REST V2 service is changed. The response now only contains the clientId.
  • REMOVED: Property client.rest.creation.response.rfc has been removed.
  • REMOVED: We removed some database configuration properties:
    • database.connection.host
    • database.connection.port
    • database.type
  • NEW: We automatically guess database type from database.connection.url instead of database.type
  • NEW: We unified the responses for every endpoint, now they will always return empty array instead of undefined for array type fields that have no data. (NEVISMETA-1853)
  • DEPRECATED: XML response type is deprecated on the REST services and will be removed soon.
  • REMOVED: We removed the jcan-log and jcan-optrace third-party dependencies. OpTrace logging is replaced by OpenTelemetry. (NEVISMETA-1941)