Everything within this section is only visible while editing. Use Page Properties ID "STUB", "REFACTURE", "PROGRESS", "rDEV", "rDOC", "rLANG" and "DONE". Everything contained within the table is displayed in the (INTERNAL) Reports page.
Resources & Remarks Modification History Add a new line to this table and fill it whenever you edit the page.
|
Follow the guideline using Helm charts for yuuvis® Momentum version updates:
>> Version Updates
When updating your yuuvis® Momentum installation from version 2021 Winter LTS to version 2022 Winter LTS, manual configuration changes are required for some services.
|
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.
InfrastructureSupport of Keycloak Version 19To use Keycloak version 19, it is required to manually adjust the
CorePerformance Optimization for CONFIGSERVICEThis feature is a subsequent change applied to version 2022 Spring as well as 2021 Winter (LTS). Please find details in the release information and in the breaking change description for version 2021 Winter. Validation of Internal JSON Web TokensThe internal endpoint of the AUTHENTICATION service for the validation of internal JSON Web Tokens (JWTs) is now available via a different URL. Action: Custom microservices that called the endpoint Tenant-specific Database ConfigurationIt is now possible to configure different databases to be used for storing metadata of individual tenants. Configurations for previous product versions are not supported anymore. The Action: If you use the TENANT-MANAGEMENT service in your installation, apply the breaking change for the METRICS service configuration first. Afterwards, apply the new configuration to the core services as described here. To continue using the same database for all tenants, replace the
To use different databases for individual tenants, please read the documentation of the application-dbs.yml configuration file. Client Services & Client DevelopmentUSERSERVICEMigration of User Information Endpoints.The user information endpoints GET /userservice/api/users and GET /userservice/api/users/{userId} are not available anymore. Action: Use the endpoints GET /api-web/api/users/users and GET /api-web/api/users/{userId} instead. Service-specific ConfigurationThe USERSERVICE does not call the identity provider itself anymore. Thus, the USERSERVICE does not require the New Microsoft JDBC Diver for SQL ServerIf you use Microsoft SQL Server as database for the USERSERVICE, the corresponding JDBC driver requires an SSL connection. Action: To continue working without SSL, append
Developer LibrariesAngular Version UpdateThe client libraries use Angular 14 now. In case you extended your client with further (third party) libraries, please ensure that they are compatible with Angular 14. Task Properties in InboxThe inbox provided by the @yuuvis/core library uses the Web-API GatewayNew Swagger UI VersionThe new Swagger version is available under a new URL. Action: Adjust the endpoint URL pattern in authentication-prod.yml configuration file has follows:
bpm-controller EndpointsThe optional query parameter Business Process ManagagementBPM EngineNew Microsoft JDBC Diver for SQL ServerIf you use Microsoft SQL Server as database for the BPM-ENGINE service, the corresponding JDBC driver requires an SSL connection. Action: To continue working without SSL, append
Tenant ManagementTenant Management APINew Swagger UI VersionThe new Swagger version is available under a new URL. Action: Adjust the endpoint URL pattern in authentication-prod.yml configuration file has follows:
idm-controller EndpointsThe optional query parameter METRICS ServiceAs the METRICS service still uses only one database for the data of all tenants, it uses an own configuration file with its own database connection parameters now. Actions:
|
Some new features require manual configuration in order to operate properly after the update to the new yuuvis® Momentum version.
In order to enable the shared usage of the session state for multiple instances of the AUTHENTICATION service, the session state has to be stored in a Redis database. In the default configuration of yuuvis® Momentum, the session state is stored by the individual AUTHENTICATION service instances. Thus, in order to enable the central storage of the session state in Redis, manual configuration steps are required.
Extend the authentication-prod.yml configuration file by the following lines:
spring.session.store-type: redis management.health.redis.enabled: true |
redis
profile to the AUTHENTICATION service:Run the command:
kubectl -n yuuvis edit deploy authentication |
SPRING_PROFILES_ACTIVE
environment variable with redis
.For example, instance 2 can be restarted using the following command:
kubectl -n yuuvis scale deploy authentication --replicas=2 |
The service uses the webhook type dms.request.objects.upsert.database-before instead of dms.request.objects.upsert.storage-before. With this improvement, the service can handle old objects with metadata properties that are no longer defined in the current schema. Furthermore, the SOTHOOK configuration is now part of the app-specific system hook configuration for the clientsystem
app.
In your global system hook configuration, remove or disable the two webhooks with a value "http://sothook/*"
for the "url"
parameter. Add the following two webhooks to the app-specific system hook configuration, via the endpoint POST /api/system/apps/{app}/systemhooks for the clientsystem
app.
{ "enable": true, "predicate": "spel:T(java.util.List).of(100,101).contains(options['action']) && properties['system:secondaryObjectTypeIds'] != null && properties['system:secondaryObjectTypeIds']['value'].contains('appClientsystem:leadingType')", "type": "dms.request.objects.upsert.database-before", "url": "http://sothook/api/dms/request/import/databasebefore", "useDiscovery": true }, { "enable": true, "predicate": "spel:T(java.util.List).of(300).contains(options['action']) && properties['system:secondaryObjectTypeIds'] != null && properties['system:secondaryObjectTypeIds']['value'].contains('appClientsystem:leadingType')", "type": "dms.request.objects.upsert.database-before", "url": "http://sothook/api/dms/request/updatemetadata/databasebefore", "useDiscovery": true } |
>> SOTHOOK
The ML Training Pipeline uses MLflow 2.0 now. Thus, the response format is not compatible with models of the beta version that was available for previous yuuvis® Momentum versions. If you already trained some beta version models, you need to