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:
| Component | Version for 6.0 | Version for 6.1 |
|---|---|---|
| Apache ActiveMQ | 5.8.0 | 5.9.x |
| Apache Karaf | 2.3.0 | 2.3.x |
| Fabric8 (was Fuse Fabric) | 7.2.0 | 1.0.0 |
| Spring framework | 3.1.3 | 3.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
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".
ActiveMQ resource adapter on JBoss EWS, JBoss EAP, and JBoss Fuse Service Works
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.
