Page History
Using the installer
| Note | ||
|---|---|---|
| ||
When upgrading from 1011.X to a newer version, it is advised to make a backup of your property files. The property files will be overridden by the installer with the new version. This new version will not have the previously used values. After upgrading there are two ways to adjust the properties so they fit the previous configuration:
|
| Note | ||
|---|---|---|
| ||
When the external H2 database is used on your local installation and preservation of the data is required after updating to a newer Blueriq version (starting from 10.0), a backup of the H2 database should be made before upgrading and put back after the installation. If the upgrade instructions of the release contain any upgrade scripts, these should be executed manually after the backup is put back. |
Upgrade for every type of release
If you as a customer are building a custom war, you should merge the files from the projectstarters of the new Blueriq release with your local equivalent files. The projectstarters are located in "\Runtime\Java\Webapp\Development\" of the Blueriq release zip. Please choose the the projectstater.zip for your application platform.
Upgrade to a release within a major release
| UI Text Box | ||
|---|---|---|
| ||
Example: upgrade from 9.0 to the latest 9 release |
Within a major release you can upgrade by running the installer. This ensures that your Blueriq installation including your repository and configuration are automatically upgraded to the new release.
Please note that there can be release specific upgrade instructions that you have to take into account, also for intermediate releases between the release you are using and the one you are upgrading to.
Upgrade to a major release
| UI Text Box | ||
|---|---|---|
| ||
Example: upgrade from 9.5 to the latest 10 release |
When you upgrade to a major release, you must upgrade to every intermediate major release as well. This does not mean that you have to install every intermediate version. You can install the latest 10 and migrate directly to that version. You are however obliged to execute the upgrade instructions of each release that you have missed in the mean time. So in the case of the example, you first upgrade to the latest 10 release and then the upgrade instructions for. 9.6, 9.7, 9.8, 9.9 and 10.0 and all other minors in between. Also check the bufix releases that you have missed for relevant information.
Before you start
Check your license: make sure you have a license for the major release you are upgrading to
- Check your platform: check our platform support to see whether the platform you are using is still supported by the major release you are upgrading to
- Read the release notes: read up on the new functionality that is available in the major release and intermediate releases by studying the release notes
- Read release specific upgrade instructions: Some releases require specific steps when you upgrade to that release. These are documented in the upgrade instructions per release. Do not forget the upgrade instructions from intermediate releases.
- When using deprecated features, it is highly recommended that you upgrade to the latest patch release available in the major release before upgrading to the next.Then you can refactor your model and code to remove the use of deprecated features before upgrading to the major where these features are removed from the software.
Performing the upgrade
A major release of Blueriq is always a new installation. This allows to install different majors next to each other. An upgrade to a major therefore consists of a fresh installation of that major and then copying the repository and configuration from the old major to that new installation.
Please note that there can be release specific upgrade instructions that you have to take into account during the upgrade.
Installation of the new major
For the installation of Blueriq please read our installation guide.
Copying repository and configuration
Copy the repository to the new installation. The repository can be found here: [Blueriq installation directory]\Studio\Repository. Once Studio is started, the repository will automatically be upgraded to work with the new release.
- Copy the Studio users & roles. This can be accomplished by copying the [Blueriq installation directory]\Studio\Configuration\Security directory and sub directories to the new installation.
- Copy the Runtime configuration. This can be accomplished by specifying your Spring Config Location, and converting your R9 properties to R10 properties.
Runtime Plugins
Version 9.X: Runtime plugins need to be upgraded manually as they are not automatically upgraded during the installer upgrade.
Version 10.X: The runtime plugins are packaged together with the runtime as components, and no manual action is required.
Upgrade instructions per release
When you upgrade to a new release of Blueriq, some things might have changed due to new or changed functionality. This may require you to take action when upgrading to this new release.
If a release contains specific upgrade instructions they are listed below.
| Children Display | ||||||
|---|---|---|---|---|---|---|
|
Overview
Content Tools