Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When updating your yuuvis® Momentum installation to version 2023 Autumn, manual configuration changes are required for some services. 

Section
bordertrue


Column

Table of Contents

Table of Contents
maxLevel3
exclude(Table of Contents|Read on|Another Tutorial|Another Concept Article|Another interesting Tutorial|Ressources|Remarks|Authentication against the Core API|Graphical Overview \/ Use Cases \(Flows\)|Login to the Core API \(Java\)|yuuvis® Momentum Services|Basic Use Case Flows)


Breaking Changes

The following Breaking Changes are incompatible changes we had to deploy into operation, and therefore you—as a yuuvis® user—need to be aware of them and take action accordingly.


Excerpt

Infrastructure

Support of Keycloak Version 22

Keycloak version 22 requires the scope configuration parameter. The Keycloak update is optional for the core system, but MANDATORY for

  • Tenant Management API and
  • KEYCLOAK-PROXY Service.

>> yuuvis® Momentum Requirements

Action: Configure the scope parameter in the application-oauth2.yml configuration file.

Core

Support of multiple Elasticsearch Instances

To realize high performance while the workload increases, it is now possible to configure multiple Elasticsearch instances. Furthermore, the connection to Elasticsearch can now be secured by username and password.

Action: To continue using the same Elasticsearch instance for all tenants, replace the spring.data.elasticsearch parameters as shown in the example below in your application-es.yml configuration in the Git root directory.

  • The spring.datasource parameters used up to product version 2023 Summer:

    Code Block
    spring.data.elasticsearch.cluster-name: 'my-es-cluster'
    spring.data.elasticsearch.cluster-nodes: '12.23.5.678:9012'
    spring.data.elasticsearch.repositories.enabled: true


  • The new configuration structure used as of product version 2023 Autumn:

    Code Block
    storage:
        searchdatabases:
          database1:
            datasource: dbsource1
            predicate: 'spel:true'
            default: true
            
        searchdatasources:
          dbsource1:
            urls: '12.23.5.678:9012'
            index: 'exampleindex'
    


To use different Elasticsearch instances for individual tenants, please read the documentation of the application-es.yml configuration file.


...