System Requirements
This chapter outlines the system requirements for operating the OMN components.
The following hardware, operating system, and software prerequisites must be fulfilled for successful deployment and operation of OMN.
Currently, only Red Hat Enterprise Linux 9 (RHEL 9) is officially supported.
OMN is executed on RHEL UBI 9 base images. Based on internal validation, OMN is known to function on both RHEL9 x86_64 and RHEL UBI9.
Linux distributions derived from RHEL9 are likely to be compatible as well; however, they are not part of the supported platform matrix.
| OMN is able to use a lot of integrations, like ChatGPT, but these are not included in OMN and have to be managed on your own. |
Software Requirements
Due to containerization, OMN components do not impose strict requirements on the underlying host distribution.
A Linux Kernel version >= 4 and a compatible container engine (Podman or Docker) are generally sufficient.
All necessary software and services are encapsulated within pre-built container images released by the OMN team.
This approach significantly simplifies deployment and ensures consistency across environments.
Hardware Requirements
The hardware specifications vary depending on the specific OMN component and desired performance level.
The following sections detail the minimal and recommended system requirements per component.
Minimal Hardware Requirements
| Component | CPU Cores | RAM | Disk Volume |
|---|---|---|---|
omn-web |
2 |
4 GB |
25 GB |
omn-sync |
2 |
2 GB |
25 GB |
omn-search |
2 |
4 GB |
25 GB |
wfl-component |
2 |
4 GB |
25 GB |
omn-ui |
2 |
2 GB |
25 GB |
Typical Hardware Setup*
| Component | CPU Cores | RAM | Disk Volume | Description |
|---|---|---|---|---|
omn-web |
8 |
16 GB |
25 GB |
Core application server handling business logic and API requests |
omn-sync |
8 |
8 GB |
25 GB |
Data synchronization service between OMN components |
omn-search |
4 |
16 GB |
25 GB |
Search engine powering product and content discovery |
wfl-component |
2 |
4 GB |
25 GB |
Workflow engine managing process automation and approvals |
omn-ui |
2 |
2 GB |
25 GB |
Frontend web server delivering the user interface |
*Hardware sizing varies by customer use case and must be defined prior to deployment.
Internet Access
Internet access is required to use OMN.
Bandwidth
| Requirements depend on the used OMN software modules, online services, system landscape and amount of processed data. The need can be higher than recommended. The concrete requirement is specified in the customer project. Therefore the values given are only a general guideline. |
-
min.6 Mbps (Megabit per second) -
recommended16 Mbps or better higher
Notes
-
RAM and disk sizes refer to minimum and recommended per container allocations.
-
Disk volumes must reside on performant storage systems, particularly for stateful services such as Elasticsearch and MinIO.
-
It is possible to use external hosted object storage, like S3 from AWS, instead of a self-hosted MinIO.
-
All OMN containers are expected to run in a container runtime environment with internet access for image pulls and optional integrations.