CMDB System Requirements¶
Hardware requirements for Backend Node¶
The Backend Node hosts the Java Vert.x application (packaged as a fat JAR).
With Medium & Large environments, it is recommended to spread the components on dedicated servers or scale horizontally using a load balancer.
| Environment | Configuration | CMDB Backend |
|---|---|---|
| Small | CPU |
|
| RAM |
|
|
| Storage |
|
|
| Medium | CPU |
|
| RAM |
|
|
| Storage |
|
|
| Large | CPU |
|
| RAM |
|
|
| Storage |
|
Note
The information above assumes the PostgreSQL database is deployed on a separate, dedicated server.
Hardware requirements for Frontend Node¶
The Frontend Node serves the compiled React Single Page Application (SPA) via an Nginx or Apache web server.
| Environment | Configuration | CMDB Frontend |
|---|---|---|
| All Sizes | CPU |
|
| RAM |
|
|
| Storage |
|
Operating system requirements¶
Microsoft Windows
| Component | Requirements |
|---|---|
| User Rights |
|
| Supported Versions |
|
Linux
| Component | Requirements |
|---|---|
| User Rights |
|
| Supported Versions |
|
Note
For installation on other Linux versions, please contact support. However, the backend should work on any system with JRE.
Supported PostgreSQL database¶
For local or external database connectivity.
| Platform | Version |
|---|---|
| All supported platforms |
|
Note
It is highly recommended that you deploy the PostgresSQL database and Backend Server on separate servers for Medium or Large environment in case of a disaster recovery setup. Please rely on PostgreSQL database administrator.
Third-party product requirements¶
The CMDB solution requires the following third-party software for bare-metal or VM deployments.
| Software | Version | Context |
|---|---|---|
| Nginx | 1.13.0 or above | Frontend Node |
| Apache (if not using nginx) | 2.4 or above | Frontend Node |
| Java JRE | openjdk version 17 or above | Backend Node |
Port availability¶
The following ports should be available and allowed through the system firewall:
| Component | Default port |
|---|---|
| Frontend Node (Nginx / Apache) | 80, 443 |
| Backend Node (Java Vert.x) | 8888 |
| PostgreSQL Database | 5432 |
Note
Use the following command to check the port availaibility: netstat -a | grep “LISTENING” | grep MY_PORT (Linux), netstat -na | findstr “LISTENING” | findstr MY_PORT (Windows). Ports can be configured after installation.
High Availability (HA) Clustering Ports¶
If you are deploying the Likpi CMDB in a multi-node, High Availability (HA) architecture, the Vert.x backend nodes must communicate with each other using the embedded Hazelcast in-memory data grid.
You must ensure the following internal TCP ports are open between the backend server nodes (these should not be exposed to the public internet):
| Component | Required Internal Ports |
|---|---|
| Hazelcast Cluster Mesh | TCP 5701 - 5705 |
Warning
Failing to open these internal ports in an HA deployment will result in a “split-brain” scenario. The nodes will fail to form a cluster, preventing them from synchronizing real-time data, sharing visibility caches, or coordinating background jobs.
Web consoles system requirements¶
| Component | Version |
|---|---|
| Supported browsers |
|