General notes
RabbitMQ
This applies to all services using RabbitMQ
- Supported Versions
-
RabbitMQ Version 3.9.13+
- Extensions
-
It is recommended to install the RabbitMQ management plugin.
- Queues / Topics / Exchanges
- Required Privileges
-
-
Configure: ^(q|x){1}\.(ai|connectivity|rm|cm)\..+$
-
Write: ^(q|x){1}\.(ai|connectivity|rm|cm|nexeed)\..+$
-
Read: ^((q|x){1}\.(ai|connectivity|rm|cm|nexeed)\..+)
-
- Relative Capacity
-
-
Kafka
This applies to all services using Kafka.
- System Requirements
-
It is recommended to install a Kafka cluster with 3 nodes:
Each node in this context needs to have the following minimal specifications:
* RAM: 16 GB
* Storage: 1TB
* CPU: 4 Core
- Supported Versions
-
Kafka 2.5+
- Extensions
-
-
- Queues / Topics / Exchanges
- Required Privileges
| Topic Name | Permissions "Rules Management"-Kafka-user | kafka-acls.sh option |
|---|---|---|
bci.cpm.* |
READ + WRITE |
"-producer" + "--consumer" |
This means that the Kafka user has read and write access to all topics starting with "bci.cpm.".
(warning) See also Kafka documentation how to secure topics through prefixed ACLs (--resource-pattern-type prefixed).-
Supported databases
Oracle DB / 19c / Enterprise Edition
- Supported Versions
-
19c
- Extensions
-
Character set (strongly recommended) (AL32UTF8)
National Character set (required) AL16UTF16) - Database Collation
-
GENERIC_M_CI_AS
- DBs / Schemas / Users
-
Schema and user are configurable. Condition monitoring needs two database user/schema, one for condition-monitoring-core and the other is for rule-service-app.
- Required Privileges
-
-
An oracle user with the privileges "NEXEED_BASIC_ROLE" as described in the Nexeed IAS Operations Manual is required
-
- Relative Capacity
-
Depending on amount of tenants, users, applications and resources managed.
Microsoft SQL Server 2019, Azure SQL
(only with MS jdbc driver, not jtds)
- Supported Versions
-
-
2019, Azure SQL
-
- Database Collation
-
Latin1_General_CI_AS
- DBs / Schemas / Users
-
Schema and user are configurable. Condition monitoring needs two database user/schema, one for condition-monitoring-core and the other is for rule-service-app.
- Required Privileges
-
Full access to manage objects and data within the schema DDL + DML.
- Relative Capacity
-
Depending on amount of tenants, users, applications and resources managed.
General notes: time series database
This applies to all services requiring a 'Time Series Database':
InfluxDB
- System Requirements
-
The InfluxDB can be a bottleneck in the system. Connection loss or slow throughput can lead to loss of data, when given for a longer period of time.
-
50% of the CM Quality Scenarios can be achieved with a single node instance.
-
100% of the CM Quality Scenarios can be achieved with a Influx cluster, consisting of two nodes.
-
Each node in this context needs to have the following minimal specifications:
RAM: 15.5 GB
Disk: 6TB (data,wal,hh) 12 GB root-partition, High IOPS equally to SSD.
CPU: 6 cores - Intel® Xeon® CPU E5-2680 v3 @ 2.50GHz
- Requirements - Important
-
To ensure data integrity an official release/docker container with security hardening is required.
- Supported Versions
-
-
InfluxDB v1.9.3 to v1.11.x
-
- DB Name - Important
-
-
The database name should not have special characters. Queries are not working if database name has for example hyphens (e.g prep11-cm), but underscore is working (prep11_cm)
-
- Extensions
-
-
- DBs / Schemas / Users
- Required Privileges
- Relative Capacity
-
-
MemTotal: 15.5 GB
-
Disk: 6TB (data,wal,hh) 12 GB root-partition
-
High IOPS equally to SSD.
-
CPU: 6 cores - Intel® Xeon® CPU E5-2680 v3 @ 2.50GHz
-