CMDBuild version update
CMDBuild version update
To upgrade an existing CMDBuild installation to a newer version, follow the procedure described below.
Before updating
Before starting the upgrade, it is recommended to create a virtual machine snapshot, if available, to simplify rollback in case of unexpected issues.
Perform the following operations:
- Stop Apache Tomcat
- Create a backup of all required data, especially the CMDBuild database
- Save any custom configuration files stored in:
<tomcat_installation_folder>/webapps/<webapp_name>/WEB-INF/conf
Update procedure
- Delete the existing CMDBuild web application directory:
<tomcat_installation_folder>/webapps/<webapp_name>
- Extract the
.warfile of the new CMDBuild version into the same location - Clear the browser cache to ensure that all updated client-side resources are loaded correctly
After updating
When the application is started for the first time after the upgrade, a notification is displayed on the login page indicating that a new version has been installed.
If custom configuration files were saved before the upgrade:
- Stop Apache Tomcat
- Restore the saved configuration files to:
<tomcat_installation_folder>/webapps/<webapp_name>/WEB-INF/conf
- Start Apache Tomcat again
If database updates are required, CMDBuild will automatically detect them and display the appropriate update procedure during startup.