Red Hat Summit Red Hat Summitサポートコンソール開発者トライアルの開始お問い合わせ

このコンテンツは選択した言語では利用できません。

Chapter 1. Summary of Migration to Red Hat JBoss A-MQ 6.0

1.1. Migration Procedure
リンクのコピー

Overview
リンクのコピー

This section summarizes the issues you need to consider when migrating from Fuse MQ Enterprise 7.1 to Red Hat JBoss A-MQ 6.0.

Product dependencies
リンクのコピー

Red Hat JBoss A-MQ 6.0 has upgraded the following dependencies:
  • Apache ActiveMQ is upgraded to version 5.8.0.
  • Spring library is upgraded to version 3.1.3.
  • The MQTT client library is upgraded to version 1.4

Migration procedure
リンクのコピー

To migrate an existing broker to Red Hat JBoss A-MQ 6.0, 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: 
    MQInstallDir/etc/org.fusesource.mq.fabric.server-default.cfg
    Copy to Clipboard Toggle word wrap
    By default, the preceding configuration file contains the following property settings: 
    broker-name=amq
openwire-port=${activemq.port}
standalone=true
data=${karaf.data}/amq
config=${karaf.base}/etc/activemq.xml

# Defaults for when joining fabric registry
...
    Copy to Clipboard Toggle word wrap
    The broker-name and data properties are not so 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.
  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 Red Hat JBoss A-MQ 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.8—when you start the 5.8 broker instance for the first time, the KahaDB auto-upgrade feature automatically upgrades the KahaDB data files.
    • Upgrading from 5.3.x to 5.8—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.8 broker. Now, when you start the 5.8 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).
  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 the Installation Guide for directions on installing JBoss Operational Network and the required plug-ins.
    2. See Chapter 4, 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: 
    bin/amq
    Copy to Clipboard Toggle word wrap
トップに戻る
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2025 Red Hat