Migrating Guide

Version 7.1

December 2012
Trademark Disclaimer
Third Party Acknowledgements

Updated: 07 Jan 2014

Table of Contents

1. Summary of Migration to Fuse MQ Enterprise 7.1
2. Persistence Layer
3. API Changes
4. Migrating Clients
5. Migrating from Fuse HQ to JBoss Operations Network

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

  1. To use your existing activemq.xml file with the new MQ console, edit the settings in the following file:


    By default, the preceding configuration file contains the following property settings:


    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:

  2. Ensure that any directories referenced in your existing activemq.xml file are specified as absolute pathnames.

  3. To migrate KahaDB data files from earlier Fuse MQ Enterprise versions, please observe the following points:

  4. Study the rest of this guide, to check whether there are any other issues that could affect your system.

  5. 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.

  6. To start up the MQ console—which automatically launches your broker—enter the following command:


The following methods are deprecated in Fuse MQ Enterprise 7.1:

Apache ActiveMQ clients are compatible with later versions of the broker, as long as the client version and the broker version have the same major version number. For example, if you update an Apache ActiveMQ broker to version 5.5.1, it will be compatible with clients on version 5.4.2.

Fuse MQ Enterprise is compatible with clients built using the following:

If your clients are built using older libraries, they will, at a minimum, need to be recompiled.

To install JBoss ON, download the server from the Red Hat Customer Portal and follow the instructions for installing on your platform. See the Installation Guide.

JBoss ON agents and monitoring plug-ins are installed from the JBoss ON Web UI.