Skip to main content
Version: 4.3

System configuration

In the following sections, the software requirements for the CMDBuild system and the installation and configuration of its components are described.

When planning the system configuration, information security must be taken into account. Deploying a web application such as CMDBuild requires hardware and network components with appropriate security measures to prevent unauthorized external access (firewall, DMZ) and to ensure adequate availability and response times.

Hardware requirements​

CMDBuild requires a physical or virtual server with the following minimum specifications:

  • Recent generation CPU with model x86-64-v2
  • At least 24 GB of RAM — 32 GB recommended for intensive use of additional features such as DMS, map server, or BIM server
  • At least 150 GB of disk storage — significantly more if extensive document archives are expected
  • The disk has recommended as SSD or NVMe SSD for optimal performance

Software requirements​

CMDBuild installation and use require the following software components.

Operating system​

CMDBuild supports any operating system that runs a JVM and the required software dependencies. Linux is recommended, as CMDBuild is more extensively tested on it.

Database​

PostgreSQL version 17.x is supported.

Ensure that the CMDBuild database uses UTF-8 encoding and that the plpgsql procedural language is available. plpgsql is installed by default in PostgreSQL.

CMDBuild uses the tomcat-dbcp library for database connection pooling. The library is included with the Tomcat distribution. If it is missing from the installed Tomcat 11 instance, use the version matching the installed Tomcat release and place the JAR file in Tomcat's lib directory.

Note: CMDBuild requires PostgreSQL because its data model relies on PostgreSQL table inheritance, including for subclass management and card history.

If GIS features are required, install PostGIS 3.6.x and enable the PostGIS extension in the CMDBuild database. For installation and configuration details, refer to the official PostGIS documentation.

Servlet container / web server​

CMDBuild requires Apache Tomcat 11.x or later (recommended: Tomcat 11.0.26). When installing via GUI, a fresh Tomcat instance is provided automatically.

To ensure correct UTF-8 encoding when using attachments, edit server.xml and add the URIEncoding="UTF-8" attribute to the main Connector element.

A web server or reverse proxy can optionally be used as a front-end to expose multiple CMDBuild instances, for example by routing requests to different Tomcat instances based on the requested domain.

The specific configuration depends on the web server or reverse proxy being used.

Document Management System (DMS)​

CMDBuild supports integration with external Document Management Systems (DMS) for document management (this feature is optional).

Both Alfresco and Microsoft SharePoint are supported as DMS platforms. Other DMS solutions may also be used.

Java​

CMDBuild requires Java 25. The Java libraries are required by Apache Tomcat.

See the Java runtime environment section in the installation guide.

Client requirements​

All user interactions with CMDBuild are performed through a web interface. This includes access to the application, data management, administration, and system configuration.

Users only need a modern web browser to access CMDBuild. Supported browsers include Mozilla Firefox, Google Chrome, Microsoft Edge, and Apple Safari.

No specific client-side software is required to use CMDBuild. The web-based architecture allows authorized users to access the system from different locations using a standard web browser, provided that the required network access to the CMDBuild server is available.