Skip to main content

Red Hat OpenShift xPaaS - Simple MQTT with OpenShift, Part One, Create A-MQ broker with MQTT protocol on Openshift

This demo will be divided into 2 parts, first is to setup the Messaging broker on OpenShift with MQTT Connector. Then we are going to write a simple demo trying to connect to the broker via MQTT

Openshift is the open and unified Platform-as-a-Service (PaaS) offering for enterprises from Red Hat. So developers like me don't have to go through all the hassle about setting up the environments or managing the networks.

And as I mentioned in the previous blogs, MQTT is a very "lightweight " protocol. It is design for remote client with limited bandwidth to deliver messages. MQTT has small footprint, consumes less power, small data packets. It's goal is simply deliver messages to the message broker, the broker is then responsible to pass on the messages to other endpoints

In this blog, I will show you how to create a A-MQ Broker running MQTT connector in OpenShift.

Before you start, please make sure you have successfully create a account on OpenShift.

First of all, create a Fuse 6.1 Application,



After successfully created the Application you will see this information page. Please note the generated password for the Fuse Console.


Go to the Console URL and Login.
Under Runtime, MQ, click on the +broker, to create A-MQ Broker.






Enter the name of the broker, (we will use standalone this time), note, please do not use camel case, stick to all lowercase. (sometimes openshift will go crazy if you do.. )


Now we have created an A-MQ configuration profile. it's showing red error because there are no running container assign to the profile. Click on the red triangle to create a container.

Give a name for container, and remember don't use camel case. With Standalone broker, we only need one container. 


The you will automatically see the container starts automatically. Click on the right arrow to see the detail.
 You will see the A-MQ starts up an openwire connector. But we want MQTT.





But we still need to add the MQTT connector setting to the configuration. Go back to the Fuse console for mqttdemo gear, Click Wiki, drill down left menu, from root/fabric/profiles/mq/broker/default.broker, Set org.fusesource.mq.fabric.server-broker.properties by clicking on the file name


Point the config to broker4mqtt.xml, (we will create this file later)

Create by click on the +Create on the upper right corner.

create the config file called broker4mqtt.xml

Add the following content to the xml.



    
    
        
            
        
        
    

    
        
          
            
          
        
    

    

        
            
              
                
                  
                    
                  
                
                
                
              
            
        

        
            
        

        
            
        

        
            
        

        
            
                
                    
                
                
                    
                
                
                    
                
            
        

        
            
     
        
    

 
Note we add the mqtt connector to port 1883.




Save, and restart the container by going to Runtime->Containers. Select the A-MQ container and restart.

After restart, go back to the broker console

You will find in the log, that it starts mqtt connector in $IP:1883.




Go to ActiveMQ and it will have 2 connectors, openwire and mqtt.














That's it. We have complete to install A-MQ with MQTT on Openshift. Next time we will run a simple program with MQTT. Thanks!

/////VIDEO COMING SOON////

Comments

dac said…
Hi Cristina, thanks for your tutorial, I was very helpful.
There is just a little problem with the broker properties, the XML posted is missing the camel case on the properties and the closing tag are a bit messy.

I posted here the correct working version: http://pastebin.com/R9Sk99YQ

Bye!
Dan Cristian said…
I followed your instructions and got the following error in logs at the last step, after trying to restart the demo container:

Exception on start: org.springframework.beans.factory.BeanDefinitionStoreException: Unrecognized xbean element mapping: policymap in namespace http://activemq.apache.org/schema/core
Dan Cristian said…
I used dac's xml conf file and it worked this way. Thanks dac.

Popular posts from this blog

Red Hat JBoss Fuse - Getting Started with Fuse Integration Service 2.0 Tech preview

I just realized that I did not do a getting started for Fuse Integration Service 2.0 Tech preview before I did the pipeline demo, thanks for those of you who reminded me! :)

To get started with FIS 2.0, for people who has just getting to know the technology, here is how I interpret it. Basically, it's divide into two aspect,

1. Integration development, FIS uses Apache Camel as the core technology that creates, orchestrate, compose microservices into a super lightweight thin integration layer, and become the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or Karaf.


2. Application Deployment and Management, FIS takes advantages of OpenShift platform, and allows you to separately deploy the micro-integration service among distributed environment, at the same time takes care of the failover, high availability, load balancing and service lookup problem for you.


So, now we know …

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 …

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 …