System requirements
Required quota on host system
CPU Clock Rate in GHz |
1 |
|---|---|
CPU Cores |
2 |
RAM in MB |
1024 |
Local File Storage |
256 |
Required software on host system
Operating System |
Linux with an OCI-compatible runtime |
|---|---|
Docker Version |
No specific version required |
Further Software |
N/A |
Required infrastructure services
IAS Portal, MACMA, RabbitMQ
| If you plan to use a file system or production archive adapter for data archiving, ensure that the SMB share is mounted beforehand. For more details, refer to the section "Add SMB Share Usage in HELM Chart File." |
Required resources
Databases
| Only one instance should be connected to one database set (Archiving Bridge). |
| When using Archiving functionality, it is necessary to have the partitioning licence for the Oracle databases. |
Oracle databases
Supported Versions |
Oracle 19c Enterprise Edition |
|---|---|
Supported Character Sets |
AL32UTF8 and WE8MSWIN1252 which is needed for the downward compatibility of existing MES databases |
DBs / Schemas / Users |
Configurable |
Required Licences |
For compression and partitioning functionality a licence is needed depending on the current licencing model of Oracle |
Required Privileges |
NEXEED_BASIC_ROLE |
For details about requirements (capacity, schemas, install scripts) regarding database installation please see section "Setup and Configuration"
Messaging middleware
RabbitMQ
messages are sent from other module and archiving bridge subscribe the message and persist data from other module.
- Supported Versions
-
Any version supporting AMQP 0.9.1
- Extensions
-
High Availability and persistence of data since no data must be lost because of product liability requirement
- Queues / Topics / Exchanges
-
Standard values used for messaging in IAS. Please see also "Setup and Configuration"
Setup of archive smb share usage
Setup Archive SMB share
Request firewall clearance
Before the actual smb share can mounted, you need to request the firewall clearance for SMB port 445. For that you can create an IT Service Portal ticket and then configure the smb share in the server.
Add SMB share usage in HELM chart file
Step 1 :
we need to add the following smb shares to the values.yaml file of the archiving bridge helm chart.
archivingbridge:
deployments:
archivingbridge-service:
volume:
- name: pvc-smb-ab
size: 1Gi
mountPath: /smb_mount
performance: high
- name: pvc-smb-ab-arc
size: 1Gi
mountPath: /smb_mount_arc
performance: highIn the above configuration, the pvc-smb-ab and pvc-smb-ab-arc are the names of the persistent volume claims (PVCs) that will be created for the SMB shares. The mountPath specifies where these shares will be mounted inside the container.
Here pvc-smb-ab is for file system adaptor and pvc-smb-ab-arc is for production archive adaptor.
Step 2 :
After adding the above configuration, you must set the appropriate permissions for the respective share paths on the server. To do this, create a technical user and a security group on the server, then grant the necessary permissions on the share paths to both the technical user and the security group. For assistance, please contact the BD team. (Judith.Kopf@de.bosch.com)