PK
lnLAoa, mimetypeapplication/epub+zipPK
mnLA META-INF/PK
mnLA OEBPS/PK
lnLA
OEBPS/images/PK
lnLA OEBPS/imagesdb/PK
knLAh h META-INF/container.xml
Since version 5.4.0, the KahaDB message store is the default persistence layer used by Fuse MQ Enterprise. The KahaDB message store is the latest evolution of Fuse MQ Enterprise's native message store and it supersedes both the AMQ message store and the (original) Kaha message store.
If no configuration is specified for the KahaDB message store, an instance with default settings is automatically created for you.
The KahaDB message store can be configured explicitly using the kahaDB
element inside the persistenceAdapter element, as follows:
<broker brokerName="broker" persistent="true" useShutdownHook="false"> ... <persistenceAdapter> <kahaDB directory="activemq-data"/> </persistenceAdapter> </broker>
This section summarizes the issues you need to consider when migrating from Fuse Message Broker 5.5 to Fuse MQ Enterprise 7.0.
Fuse MQ Enterprise 7.0 has upgraded the following dependencies:
Jetty library is upgraded to version 7.3.1.
HttpClient library is upgraded to version 4.1.2.
To migrate an existing broker to Fuse MQ Enterprise 7.0, it is recommended that you follow these steps:
To use your existing activemq.xml file with the new MQ console, edit the
the settings in the following file:
MQInstallDir/etc/org.fusesource.mq.fabric.server-default.cfgBy 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.xmlThe broker-name and data properties are not important: they
define substitutable properties that are used by the default activemq.xml
file (located in ).
The important properties are as follows:MQInstallDir/etc/activemq.xml
configSet 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.)
standaloneThis property must be set to true. Do not
change it.
openwire-portOverrides 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.5.1—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.1—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.
To start up the MQ console—which automatically launches your broker—enter the following command:
bin/fusemq
Table of Contents
