Este contenido no está disponible en el idioma seleccionado.

Chapter 1. Migration Overview


Abstract

This chapter highlights some of the key points that might affect your applications, when migrating from JBoss A-MQ 6.0 to JBoss A-MQ 6.1. For a detailed description of the changes made to each of the components, see the relevant chapters for Apache ActiveMQ, Apache Camel, and Apache CXF.

1.1. Upgraded Components

Version upgrades

Many of the major components in JBoss Fuse and JBoss A-MQ 6.1 have been upgraded. The following versions are used in JBoss A-MQ:
Expand
Table 1.1. Component Versions
ComponentVersion for 6.0Version for 6.1
Apache ActiveMQ5.8.05.9.x
Apache Karaf2.3.02.3.x
Fabric8 (was Fuse Fabric)7.2.01.0.0
Spring framework3.1.33.2.x

Fuse Management Console

In JBoss A-MQ 6.1, the implementation of the Fuse Management Console has changed and it is now based on the open source Hawt.io project. The new Fuse Management Console has a radically different look-and-feel from the old version, with greatly expanded functionality and many new features.
When you start up the JBoss A-MQ container (for example, by running the command, bin/amq), the new Fuse Management Console is installed by default. You can access it by navigating to the following URL in your browser:
http://localhost:8181
Copy to Clipboard Toggle word wrap
For more details, see "Management Console User Guide".
Note
The ActiveMQ Web console has also been removed from the JBoss A-MQ 6.1 product. Equivalent functionality for Apache ActiveMQ is now provided by the Fuse Management Console.

Fuse IDE

The Fuse Integrated Development Environment (IDE) is no longer provided as a standalone Eclipse executable. Fuse IDE has been renamed to Fuse Plugins for JBoss Developer Studio. To install Fuse Plugins, first download and install JBoss Developer Studio and then install the relevant Eclipse plug-ins. For detailed instructions, see "Installation Guide".
The ActiveMQ resource adapter has been certified to function correctly on the JBoss Enterprise Web Services container, the JBoss Enterprise Application Platform container, and on JBoss Fuse Service Works, enabling you integrate JMS applications running on those containers with JBoss A-MQ.

Apache Camel deployed on JBoss EWS and JBoss EAP

The Apache Camel core library has been certified to function correctly on the JBoss Enterprise Web Services container and on the JBoss Enterprise Application Platform container.

Apache ActiveMQ changes

The changes resulting from the upgrade to version 5.9.0 are detailed in Chapter 2, Apache ActiveMQ Issues.
The most important changes are:
  • The ActiveMQ Web console is no longer supported.
  • If you are using a JDBC store with a broker that uses XA transactions, you will need to make some changes to the database schema, when migrating the database store.
  • Dynamic configuration updates are now supported on a standalone broker.
  • A generic JMS XA connection pool library is now available, which makes it possible to deploy third-party JMS providers.

Apache Karaf Web console

The Karaf Web console is no longer supported in JBoss A-MQ 6.1. You can use the new Hawtio-based Fuse Management Console instead, which has the same functionality (and more) as the Karaf Web console.
Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat