Summary of Fuse Message Broker 5.4 to Fuse Message Broker 5.5 Migration

Overview

This section summarizes the issues you need to consider when migrating from Fuse Message Broker 5.4 to Fuse Message Broker 5.5.

Product dependencies

Fuse Message Broker 5.5 has the following notable product dependencies:

JDK 1.6.0_18 (or later) is now required.
Spring 3.0.x is now required (if using Spring).
Both Maven 2.2.1 and Maven 3.0 are now supported (for building the source).
Camel is upgraded to version 2.7.1.

Migration procedure

When migrating to Fuse Message Broker 5.5, it is recommended that you follow these steps:

Update your environment variables to point at the new installation of Fuse Message Broker, as follows:
Windows O/S
Update your environment variables as described in ????.
*NIX O/S
Run the activemq setup administration tool to generate a new startup script, as follows:
```
./activemq setup StartupScript
```
Where StartupScript is the path to either of the standard startup script locations, /etc/default/activemq and /home/User/.activemqrc. After generating the startup script, edit and customize it as necessary. For more details, see ????.
You can re-use your existing Fuse Message Broker XML configuration files. If you are migrating from a Fuse Message Broker version 5.3 or earlier, however, you might need to change the order of elements appearing inside the broker element, which are now required to appear in alphabetical order (as defined in the XML schema). The alphabetical ordering requirement applies to elements at all nesting depths.
For more details, see ????.
To migrate KahaDB data files from earlier Fuse Message Broker versions, please observe the following points:
- Always make backup copies of your existing KahaDB data files, before upgrading the broker.
- Upgrading from 5.4.x to 5.5.0—when you start the 5.5 broker instance for the first time, the KahaDB auto-upgrade feature automatically upgrades the KahaDB data files.
- Upgrading from 5.3.x to 5.5.0—due to a recent change in the format of the KahaDB index file, db.data, the KahaDB auto-upgrade feature cannot upgrade 5.3 index files. To upgrade from 5.3, therefore, delete the index and redo files, db.data and db.redo, before starting the 5.5 broker. Now, when you start the 5.5 broker, it recreates the index file as it starts up (if your database is large, this could take a long time, for example 20 to 30 minutes).
Study the rest of this Migration Guide, to check whether there are any other issues that could affect your system.

Comments powered by Disqus