Summary of Migration to Fuse MQ Enterprise 7.1

Overview

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

Product dependencies

Fuse MQ Enterprise 7.1 has upgraded the following dependencies:

Jetty library is upgraded to version 7.6.7.

Migration procedure

To migrate an existing broker to Fuse MQ Enterprise 7.1, it is recommended that you follow these steps:

To use your existing activemq.xml file with the new MQ console, edit the settings in the following file:
```
MQInstallDir/etc/org.fusesource.mq.fabric.server-default.cfg
```
By default, the preceding configuration file contains the following property settings:
```
broker-name=default
openwire-port=${activemq.port}
standalone=true
data=${karaf.data}/activemq
config=${karaf.base}/etc/activemq.xml
```
The broker-name and data properties are not important: they define substitutable properties that are used by the default activemq.xml file (located in MQInstallDir/etc/activemq.xml). The important properties are as follows:
config
Set this property to the absolute pathname of your existing activemq.xml file. (If you are working on a Windows platform, remember to use the forward slash character, /, for the path separater, as is customary in Java property files.)
standalone
This property must be set to true. Do not change it.
openwire-port
Overrides the Openwire IP port value specified in your existing activemq.xml file. Delete this property setting, if you want to keep the port value specified in your activemq.xml file.
Ensure that any directories referenced in your existing activemq.xml file are specified as absolute pathnames.
To migrate KahaDB data files from earlier Fuse MQ Enterprise 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.7—when you start the 5.7 broker instance for the first time, the KahaDB auto-upgrade feature automatically upgrades the KahaDB data files.
- Upgrading from 5.3.x to 5.7—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.7 broker. Now, when you start the 5.7 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 guide, to check whether there are any other issues that could affect your system.
If you are using Fuse HQ to monitor your systems:
1. See ???? for directions on installing JBoss Operational Network and the required plug-ins.
2. See Migrating from Fuse HQ to JBoss Operations Network for information about migrating alerts and other custom setting from Fuse HQ to JBoss Operational Network.
To start up the MQ console—which automatically launches your broker—enter the following command:
```
bin/fusemq
```

Comments powered by Disqus