Versions Compared

Key

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


Page Properties
hiddentrue
idREFACTURE

Product Version2020 Winter
Report Note
AssigneeAntje

Resources & Remarks

Modification History

NameDateProduct VersionAction
Antje08 FEB 20212.4New page properties macro.
Antje17 FEB 20212020 WinterOutline & Placeholders
Antje&Mario18 FEB 20212020 WinterRequirements for Core Services
Antje22 FEB 20212020 WinterRequirements for Client Services
Agnieszka05 MAR 20212020 WinterrLANG


INGAs originial introduction:


The following overview lists the system requirements for the operation of yuuvis®.

The systems listed have been tested in the listed versions together with this release in the OPTIMAL SYSTEMS release tests and their compatibility has been ensured.

yuuvis® uses standardized interfaces and integration technologies, meaning that yuuvis® also works with a wide range of older or more recent versions of the systems listed and with other unlisted systems. OPTIMAL SYSTEMS does not guarantee compatibility for systems not listed in the system requirements and performs its services subject to restrictions (in particular, no damage repair) in accordance with the prevailing maintenance contracts. In addition, OPTIMAL SYSTEMS guarantees compatibility with a listed system up until the date that the manufacturer guarantees regular (for example, not extended, expanded, individually agreed) support.

Moreover, the minimum system requirements describe the system equipment needed for a productive yuuvis® system to provide adequate operational performance. This information is a set of non-binding guidelines. OPTIMAL SYSTEMS can only give a guarantee for a specific system environment on the basis of a customized hardware constellation. Likewise, it can be possible to still have full operational capability of the test systems, demo systems, or systems with only partially used functionality if the minimum system requirements are not reached.

...

Kubernetes is required for installation and operation of yuuvis® Momentum instances. The versions listed below are supported.

131215719.2
Kubernetes Versions
1.19
1.20
1.21
1.22
1.17.623
1.24
1.19.725

Helm

Deployments for yuuvis® Momentum are offered via Helm Charts and thus require the installation of Helm. The supported versions are listed below.

...

Elasticsearch Versions
7.9.x
7.3.x

In order to operate Elasticsearch together with yuuvis® Momentum, the following plugins are additionally required. Please install a version that is supported by your Elasticsearch version.

  • Intrafind Linguistic Plugin
  • ICU Analysis Plugin

Redis

In order to ensure synchrony in internal processes of yuuvis® Momentum, an in-memory data structure store is required. Our tested recommendation is Redis.

Redis Versions
6.0.9

Messaging Systems

yuuvis® Momentum uses the OASIS Advanced Message Queuing Protocoll (AMQP) Version 1.0 for internal messaging. The messaging systems of the corresponding versions listed below are tested with yuuvis® Momentum. Since RabbitMQ does not support AMQP Version 1.0, an additional plugin is required.

Messaging SystemVersionAdditionally Required Plugin
ActiveMQ5.15.4-
RabbitMQ3.8.9rabbitmq_amqp1_0

Git

We strongly recommend to use Git as config store for yuuvis® Momentum, that acts as a version control system at the same time. In general, any git server should be sufficient. However, we tested the git servers listed below with the corresponding versions.

Git ServerMinimum  Required Version
Gogs0.11.91
Gitea1.12.0
GitLab

11.10.8

S3 Store

yuuvis® Momentum is working with an S3 directory that has to be connected via a service supporting the S3 protocol. All our tests are performed with MinIO, that can operate as store and as protocol service at the same time. It can also be used to connect an S3 store of a different provider to yuuvis® Momentum.

MinIO Versions
RELEASE.2020-10-18T21-54-12Z

Anchor
Auth
Auth

Authentication Provider

For operation of yuuvis® Momentum, an authentication provider is required. In general, any authentication provider supporting the OAuth 2.0 protocol can be combined with yuuvis® Momentum. However, we perform all our tests with Keycloak. The supported versions are listed below.

Keycloak Versions
7.0.0
10.0.2
11.0.2

Additional Services

If client services of yuuvis® Momentum are planned to be installed, Keycloak is required as authentication provider.

Anchor
userservice
userservice

USERSERVICE

Database

For operation of the USERSERVICE, an own database instance is required. The same database systems as for the core services are supported.
>> Supported Providers and Versions

Keycloak

The USERSERVICE supports only Keycloak as authentication provider.
>> Supported Versions

Anchor
metrics
metrics

METRICS Service

...

For operation of the METRICS service, an own database instance is required. The same database systems as for the core services are supported.
>> Database

Anchor
bpm-engine
bpm-engine

BPM Engine

Database

For operation of the BPM Engine, an own database instance is required. The same database systems as for the core services are supported.
>> Supported Providers and Versions

Keycloak

The BPM Engine supports only Keycloak as authentication provider. The same versions as for the core services are supported.
>> Supported Versions

Anchor
client
client

yuuvis® client as reference implementation

...

The reference client supports only Keycloak as authentication provider. The same versions as for the core services are supported.
>> Supported Versions

Anchor
TenantManagementAPI
TenantManagementAPI

...

yuuvis® architect supports only Keycloak as authentication provider. The version has to be supported by the Tenant Management API since endpoints are used by yuuvis® architect.
>> Supported Versions

yuuvis® management console

...

yuuvis® management console supports only Keycloak as authentication provider. The supported versions are listed below. The version has to be supported by the Tenant Management API since endpoints are used by yuuvis® management console.
>> Supported Versions

Libraries for Custom Clients

...

The framework library supports only Keycloak as authentication provider. The same versions as for the core services are supported.
>> Supported Versions

Further Requirements

You can find information on the required third-party building software in the libraries documentation.
>> Custom Client Build with Libraries

...