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/, Set 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!



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:

Unknown 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
Unknown said…
I used dac's xml conf file and it worked this way. Thanks dac.

Popular posts from this blog

Red Hat Fuse - Announcing Fuse 7 Tech preview 3 release.

Red Hat Fuse 7.0 technical preview three is out today! On the pathway to become one of the best cloud-native integration platform, Fuse gives developer freedom to choose how they want to develop the integration solution, where they want to deploy it and capabilities to address new integration personas that do not have development experience.
By supporting the three major runtime, developer is free to work on the runtime of their choice.By supporting standalone and cloud deployment, it simplifies the complexity to distinguish between these environments, allowing application to deploy freely among the environment of your choice. All levels of developers are welcome, you can either dive deep into creating customize complex integration logic, or using the new low code platform to quickly build a simple integration. In this Tech Preview release you get it all.
Fuse StandaloneSpring-boot for microserviceKaraf 4 for OSGi loverJBoss EAP for JavaEE developersFuse on OpenShiftPlugins for easy co…

JBoss EAP 6 - 效能調校 (一) DataSource 的 Connection Pool

效能沒有什麼Best Practice, 反正能調整的就那些。 通常,一個程式的效能大概有70-80% 都跟程式怎麼寫的其實比較有關係。

最近我最疼愛的小貓Puji 因為膀胱結石開刀的時候過世了,心情很差請原諒我的口氣沒有很好,也沒有心情寫部落格。

Puji R.I.P.



JBoss 的 SubsystemDatasource WebWeb Service EJB Hibernate JMSJCAJVM 調校OS (作業系統)

先來看一下 DataSource Subsystem, DataSource 的部分主要是針對Connection Pool 做調校。

通常,程式都會需要跟資料庫界接,電腦在本機,尤其是在記憶體的運算很快,但是一旦要外部的資源連接,就是會非常的耗資源。所以現在的應用程式伺服器都會有個Pool 放一些先連接好的 資料庫connection,當程式有需要的時候就可以馬上提供,而不用花那些多餘的資源去連接資料庫。

這就是為什麼要針對Connection Pool 去做調校。

以下會討論到的參數,都是跟效能比較有關係,Datasource 還有很多參數,像是檢核connection 是否正確的,我都不會提到。如果你追求的是非常快速的效能,那我建議你一個檢核都不要加。當然,這樣就會為伺服器上面執行的程式帶來風險。這就是你要在效能與正確,安全性上面的取捨了。 (套句我朋友說的話,不可能又要馬兒好,又要馬兒不吃草的..)

最重要的調校參數就是 Connection 的 Pool 數量。(也就是那個Pool 裡面要放幾條的connection.) 這個參數是每一個應用程式都不一樣的。


Connection Pool 最少會存留的connection 數量


Connection Pool 最多可以開啓的 connection 數量


事先將connection pool 裡面建立好min-pool-size 的connection.

我的建議是觀察一下平常程式要用到的量設定為 min-pool-size 。

My 2cents on the future of Integration - With Service Mesh/Istio and Serverless/KNative

It's been a year and half since I blogged about "Agile Integration architecture" (Gosh, time just flies). With the "microservices" and "cloud-native" hype, I was especially curious on how all these new concept and technology affect us on how to architect the integration systems. If you ever pay close attention to all the latest and greatest news from the Kubernetes community, I am sure you will hear a lot about the new "Service Mesh". And rumor has it that this is how integration can/should be done in cloud native world, but, is that so? Anyone who has ever worked on an integration project would tell you, it's a LOT more COMPLEX and can get worst overtime. I did a talk with Christian Posta in Red Hat Tech Exchange coming from a more comprehensive view of how different Red Hat technologies are applied under different patterns when building integration solutions. In fact he also did a great blog about it.

Since then, another topics has be…