Skip to main content

Red Hat A-MQ - Create cluster of brokers support AMQP in Fabric


In this tutorial, I am going to show you how to create a cluster of message broker using the built-in management platform Fabric. This make life much much easier to either config and manage brokers.

Please obtain a copy of JBoss A-MQ by going to
http://www.jboss.org/products/amq.html
and download JBoss A-MQ from Red Hat.

Here are the summary steps to create.

1. Unzip to install
2. Create User
3. Startup A-MQ server
4. Create Fabric
5. Create A-MQ broker profile
6. Create the container
7. Create a new version and apply AMQP Setting
8. Container version rolling upgrade
9. Test it.



To install simply unzip the jboss-a-mq-version.redhat-x.zip file to a directory.

Before starting up JBoss A-MQ, we need to set a default user.
Open up  $A-MQ_INSTALLATION_PATH/etc/users.properties 
Remove the # before admin=admin,admin


or you can add your own prefer user id,  password and role.
(USER=PASSWORD,ROLE1,ROLE2,...)


Go to $A-MQ_INSTALLATION_PATH/bin , startup A-MQ by executing

Unix/Linux,
                    ./amq

Windows, 
                     amq.bat



Because we are going to manage brokers from Fabric,
create the fabric with this command

fabric:create --wait-for-provisioning

There are two different ways to create MQ broker, we can create one using Hawtio GUI or by command. I am going to show you the command part first in the tutorial.

type in

mq-create --group demo mybroker

This creates a A-MQ profile called mybroker, that belongs to a group called demo

Type profile-list or profile-list | grep mybroker to see if the profile has been successfully created.

Add broker settings to mq-broker-demo.mybroker profile by typing

profile-edit --resource broker.xml mq-broker-demo.mybroker 

and paste the following content into the file, save. 




    
    
        
            
              
    

    

        
            
              
                
                  
                    
                  
                
                
                
              
            
        
 
        
            
        

        
            
        

        
            
        

        
            
                
                    
                
                
                    
                
                
                    
                
            
        
        
        
            
        
    






you should be able to see the new resource added by checking with 

profile-display mq-broker-demo.mybroker 


Now the profile is ready, we are going to create 3 containers (instances) that will run this messaging profile. 

container-create-child --profile mq-broker-demo.mybroker root demoContainer1
container-create-child --profile mq-broker-demo.mybroker root demoContainer2
container-create-child --profile mq-broker-demo.mybroker root demoContainer3




All 3 container should startup automatically, you can check if it correctly install by listing all the containers:

container-list 

Now, you have successfully create a clusters of A-MQ broker with Master-Slave topology. But it still doesn't run AMQP yet. 

I want to show you how to do version upgrades,

Create version 1.1
fabric:version-create 1.1

Add AMQP connector to the 1.1 version of our profile mq-broker-demo.mybroker
profile-edit --resource broker.xml mq-broker-demo.mybroker 1.1

add the amqp connect in the transportConnectors section of xml.
<transportConnector name="amqp" uri="amqp://0.0.0.0:5672"/>
SAVE. 

Last part of setting, we need to upgrade the containers to our updated version 1.1
fabric:container-upgrade 1.1 demoContainer1
container-list 

And do the rest, 
fabric:container-upgrade 1.1 demoContainer2
fabric:container-upgrade 1.1 demoContainer3

Now, testing 

git clone https://github.com/FuseByExample/activemq-amqp-example.git

Goto 
activemq-amqp-example/src/main/resources/jndi.properties change the connectionfactory.myJmsFactory setting to 

amqp://admin:admin@localhost/test?brokerlist='tcp://0.0.0.0:5672




Test  AMQP by running consumer, under activemq-amqp-example/ directory, 

mvn -P consumer

And startup Producer to test 

mvn -P producer

You should see the consumer picking up the message created by the producer. 







Comments

Chisoon Chang said…
Tried this demo, so I can understand and traced what went wrong with your bio-sensor demo. However, I ran into a problem at your slide 7 where profile-display to show the new configuration of mybroker. The mybroker does not have the new PID as org.fusesource.mq.fabric.., I even did a profile-refresh, it still carried the io.fabric.mq.. as that of the original activemq.xml from the jboss-am-q source. I followed your steps twice (profile-delete mybroker and mq-create mybroker again) and came out the same result. Something seems wrong with my local set-up. Suggestion?
Chisoon Chang said…
Although I could not repeat this demo on my local RHEL 6.x box, I have fundamental question about the purpose of setting cluster of brokers. Under what condition or program reqirements, we need to set up such cluster of brokers?

Popular posts from this blog

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

jboss-devstudio-9.0.0.GA-installer-eap.jar
double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.


And select JBoss Fuse Development for the plugin,


Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …

RHTE - Supercharge your integration services

Red Hat Tech Exchange has taken place in Vietnam, Ho Chi Minh city two weeks ago, it is a great event held by Red Hat in Asia Pacific Region. It is open to all Red Hat partners who are interested in learning what Red Hat is doing recently, see what the trend of the open source world, basically it is a great event to share your knowledge and experience, to meet other enthusiastic people.

I am very fortunate to talk in this great event, to talk about the things I have been working on and even discuss it with many. Also got lots of great ideas too. So here are the slide.

My first talk was with Thomas Qvarnström about how to handle large size data in JBoss Fuse and how JBoss Data Grid can help in the situation.

Here is the agenda of the talk, we will be talk about this in the up coming webinar on 24th Sept.

Integration often involves storing, retrieving, and transforming data. Using a traditional database in your integration is likely to becomes a bottleneck that is expensive and hard to …

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.



And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …