I need help because I'm new about kafka and mqtt.
I will try to briefly explain the architecture I am using.
I'm using the Confluent 5.3.1 platform and I configured a connector (source mqtt connector) that transfers data from the mqtt broker to kafka broker.
In order to connect to the mqtt broker I need a Json Web Token and I have no idea how to do it. I've read the Confluent documentation but i can't find any possible solutions.
Can someone help me?
Looking at the documentation for the connector it looks like it only support password-based authentication, not JWT.
IBM has MQIPT (IBM MQ Internet Pass-Thru) that acts as MQ forwarder/reverse proxy to implement messaging solutions between remote sites across the internet. Is there such an equivalence for Solace?
Solace has all kinds of fancy advanced features for load balancing and hybrid/multi-site deployments like bridges and dynamic message routing, but I don't really know those, and where's the fun in having everything ready-made and pre-solved for you anyway? :-)
So here I am going to assume you want to roll your own solution and use an actual reverse proxy:
You can switch to HTTP-based protocols, and just use any regular HTTP reverse proxy. Solace message brokers have a REST message interface, or if your application already uses the Solace API for messaging (or needs its advanced features), you can switch over to HTTP streaming or WebSockets as a transport by modifying the scheme portion of the broker URL in your application configuration. (http:// or ws:// instead of tcp://) This will only allow you to balance sessions, not individual messages within a single elephant flow.
We are looking at using MQTT as the messaging protocol on a new device we're building. We'd also like a web interface for the device. Does anyone know if you can implement a browser client app (without additional plugins) that talks MQTT?
Yes, as mentioned in Steve-o's comment MQTT via websockets is very possible.
There are 2 options at the moment
IBM's MQ 7.5 comes with websockets support, you can find details here.
The Mosquitto broker has a javascript client with an example running here.
To answer your second question lighttpd has a websockets module that can be used to do forwarding to an existing broker with details here.
I've not been able to find anything for Apache that doesn't need you to write your own library to do the forwarding.
To extend hardillbs answer:
There is a third option now:
HiveMQ supports native websockets without the need for any external web server. It works perfectly with the Javascript client of Eclipse Paho.
If you want to try it out, the public MQTTDashboard (which uses HiveMQ under the hoods) supports websockets on port 8000.
Disclosure: I am one of the developers of HiveMQ
IBM has released a WebSockets based JavaScript client. It is open-source on Eclipse Paho.
Git repository:
http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt.javascript.git/
Tutorial is here.
https://www.ibm.com/developerworks/community/blogs/c565c720-fe84-4f63-873f-607d87787327/entry/how_to_prog_javascript?lang=en
We've had good experience using WSS, the WebSocket to TCP Gateway (for MQTT). It means running a separate process, but that does avoid having to change Apache's configuration. WSS also has support for TLS.
Not Apache, but you can follow this guide to install lighttpd with mod_websocket,
http://oriolrius.cat/blog/2013/09/25/server-send-push-notifications-to-client-browser-without-polling/
but for easy of use I highly recommend HiveMQ, as #Dominik recommends.
The blog by jpmens is a good starting point to get mosquitto setup with websocket feature. He's client javascript code based on Paho is on github.
This blog "How to run your web server and MQTT WebSockets broker on the same por" explains two ways for the server side:
mosquitto with http configuration
apache+mod_websocket_mosquitto
Why not nodejs + socket.io? They come with all gadgets included (webscokets, pub/sub, webserver,mqtt broker...).
SocketCluster is another good starting point.
This link (Download codes) is useful. Download it and modify this file mosq-mqttws31.html. Instead of the embedded java script library use this cdn
https://cdnjs.cloudflare.com/ajax/libs/paho-mqtt/1.0.1/mqttws31.js
and the client instantiation should be client = new Paho.MQTT.Client("test.mosquitto.org", 8080,"myclien256tiddd_" + parseInt(Math.random() * 100, 10));
Need answers to below two questions:
Q1) Which JMX layer consists of resources
Options:
1.Agent
2.Instrumentation
3.Distributed Services
4.None
and
Q2) JMX does not contain
Options:
1.Instrumentation
2.Agent
3.management
4.Distributed Services.
Some document enlightening me on these very aspects of JMX will be helpful.
You can refer to : Understanding JMX
You will find out that :
the JMX layer dealing with resources is the Instrumentation
JMX do not include Management (but provides interfaces for clients to implement it)
The link mentioned in the answer has changed to - http://docs.oracle.com/cd/E13222_01/wls/docs100/jmxinst/understanding.html
I wanto to write a modified ActiveMQ broker that when he listens to producers' messages of a specific topic to handle them alternatively (use HDFS API for example and not use default persisten store). Do you have any ideas where to start with?
thanks in advance,
Petrucci
You could either implement your own ActiveMQ message store for HDFS which would allow ActiveMQ to use HDFS as a persistence store, or you could create an ActiveMQ broker plugin which would allow you to intercept messages as they enter the broker. Both are very different approaches, so it really depends on your requirements as to which path to take.
Bruce