Upgrade your development project

If you developed components on top of LuciadFusion, such as custom data connectors or web services, you must integrate new versions of LuciadFusion into your development project. To do so, you can follow the steps described in the LuciadLightspeed upgrade article, which equally applies to LuciadFusion.

Upgrade your deployed server

LuciadFusion has been designed to automatically migrate the database of an older LuciadFusion server, but for servers in production, we recommend that you back up your existing deployment setup before upgrading.

The configuration of a LuciadFusion server is defined in a set of YAML configuration files in the config folder. These define the location of the database, data locations, security settings, and more. See Configuring LuciadFusion Studio for more information.

To make your new server re-use all data and configuration from an existing server, you must migrate your settings in these files from the existing server to the new server. That migration of settings includes:

  • fusion.studio.db.url: the database in which a LuciadFusion server stores its configuration. To deploy a new server, you can refer to the existing database: the new server automatically migrates the database to the new version, keeping all data intact.

  • fusion.engine.tilestoreHome: the location that stores tiled data, generated by the LTS service. If you have any LTS services up and running, it’s important that this location remains the same in the new server.

  • fusion.studio.configuration.datastore: the location storing:

    • A copy of the Lucene index and any uploaded data

    • Pre-processed data

    • The H2 development database, if you’re using it

  • Any other settings, such as security-specific or service-specific settings: when you receive a new LuciadFusion version, you can rely on a file comparison tool to find the differences between the YAML configuration files of your deployed server and the new server.