mat/materialmanagement-backendservice
Required quota at host system
CPU Clock Rate in GHz |
2.5 |
|---|---|
CPU Cores |
4 |
RAM in MB |
minimum 2048 / recommended 4096 |
Local File Storage (MB) |
500 |
Required software at host system
Operating System |
Linux, 64-bit (Red Hat Enterprise Linux 7 recommended) |
|---|---|
Docker Version |
19.03+ |
Further Software |
bash/shell |
Required infrastructure services
Helmchart
Default configuration
The securityContext section for the service deployments and jobs should be configured the following way:
values.yaml
deployments:
<ServiceName>:
[...]
securityContext:
runAsNonRoot: true
allowPrivilegeEscalation: false
[...]
jobs:
<JobName>:
[...]
securityContext:
runAsNonRoot: true
allowPrivilegeEscalation: false
[...]
Databases
Oracle database
-
Supported Versions: Oracle 19c Enterprise
-
Extensions: Character set (strongly recommended) (AL32UTF8), National Character set (required) (AL16UTF16)
-
Schemas / Users: Schema and user are configurable (schema needs to be default for user)
-
Required Privileges: An oracle user with the privileges "NEXEED_BASIC_ROLE" and "NEXEED_EXTENDED_ROLE" as described in the Nexeed IAS Operations Manual is required.
-
Relative Capacity: Depending on amount of tenants, users, applications, resources, size of the factory and materials managed, minimum 2 GB
MSSQL (Microsoft SQL) Database
Currently not supported
Messaging middleware
RabbitMQ as AMQP 0.9.1 broker
-
Supported Versions: The same version is supported as configured with the 2023.01 IAS distribution
-
Queues / Topics / Exchanges: IAS standard queues and exchanges
-
Required Privileges: IAS standard
-
Relative Capacity: Depending on the size of the factory
| mTLS is currently not supported for RabbitMQ connections. For further details about mTLS, see here |
Service mesh
The communication between the reverse proxy and the Material Management microservice instances should be secured by a service mesh. The service mesh must be provided by the operator of the environment.
Required resources
| Resources | Comments |
|---|---|
key store and trust store |
keys and certificates required for TLS, can be configured via environment variables NEXEED_SERVER_TLS_ENABLED (see application_security for more information) |