Skip to main content

Red Hat OpenShift xPaaS - Simple MQTT with OpenShift, Part Two, Simple client connecting to Broker on xPaaS

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

This is the 2nd part of the demo, we have previously setup a broker on Openshift, the PaaS offering from Red Hat. (see Part One). Now we have a broker running on the cloud ready to service. 

Apart from, MQTT is a very "lightweight " protocol. MQTT's nature act as a publish/subscribe messaging transport, so base on the scenario, it is more suitable for Topic, there will be no queue implementation for MQTT. 

This demo is a very simple producer and consumer, publishing messages through MQTT protocol. Using library of fusesource's mqtt-client. 

Before we start, please make sure you have successfully setup the broker on OpenShift. (see Part One). And we need to setup the environment in our local machine to work with xPaaS. Normally, the port are access on the PaaS itself. If the developer wants to access the broker in their machine, rather then configuring the complex networking setup. Openshift has a simple feature, which simply forward the service port on the PaaS to local machine. To do that , simply run the following command.

rhc port-forward $YOUR_CONTAINER_NAME 






For Mac Users, sometimes you need to add the following command to create an alias on your local machine for the IP address of the OpenShift broker 

sudo ifconfig lo0 alias $OPENSHIFT_IP

To run the demo, please clone the git repo to your local machine by running

git clone https://github.com/weimeilin79/mqtt-demo.git

And run the init.sh to setup. You will need to enter your Broker URL, user name of fuse console and the password. 

./init.sh
  • The broker URL is the mqtt port (default 1883 if you have been following the setup), and the IP will be mapped to your local machine. So it should be 127.0.0.1.
  • The user name of console and the password are given to you from previous setup in openshift. 










To run the consumer and producer, just go to the projects/mqttdemo directory and run 

mvn -P consumer 
mvn -P producer  

it will start sending the messages.  
In the same time you will see the statistics changing on Openshift.

Going through the development part. in pom.xml , remember to add the mqtt-client library. 

   
   
    org.fusesource.mqtt-client
    mqtt-client
    1.11-SNAPSHOT
   
   
    org.fusesource.mqtt-client
    mqtt-client-java1.4-uber
    1.11-SNAPSHOT
   
   
     org.fusesource.hawtbuf
    hawtbuf
    1.9
   
  
As for the producer and consumer, it's just simple API Call. 
(There are many different API to work with, I will show you if I have time.)
MQTT mqtt = new MQTT();
mqtt.setHost(props.getProperty(BROKER_URL));
mqtt.setUserName(props.getProperty(USERNAME));
mqtt.setPassword(props.getProperty(PASSWORD));
  
  
BlockingConnection connection = mqtt.blockingConnection();
connection.connect();
Topic[] topics = {new Topic(utf8("foo"), QoS.AT_LEAST_ONCE)};
connection.subscribe(topics);
Message message = connection.receive();
message.ack();
connection.disconnect();


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


Comments

Zachariah Young said…
How do you connect to the MQTT broker without doing the network alias? I'm working on a java program locally and don't want to setup the local network alias.

Thanks

Zach

Popular posts from this blog

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.) 這個參數是每一個應用程式都不一樣的。

min-pool-size 

Connection Pool 最少會存留的connection 數量

max-pool-size 

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

prefill

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

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

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…

The rise of Agile Integration, Integration is not DEAD nor LAME!

I wanted to blog about this for a very long time, but because of work and being too lazy to turn on my laptop on the weekends, now I finally have a couple of hours to sit down and start blogging.

"Integration is DEAD."
"No, no, let's talk about microservice!!"
"What is that again? Integration, you mean SOA? It's lame... ".

These makes the majority of the percentage when I talk about Integration. In fact, if you happen to be in any the software conference, you see the rooms full when it's about "container" and "microservice." I understand the nature of a developer, always seeking for the latest and greatest technology out there. BUT!! In my opinion, I don't think Integration is going AWAY if you containerize your application. Neither does it will DISAPPEAR in a microservice architecture. In fact, Integration just gets more complicated and tricky when you try to break an application into smaller pieces and have them runni…