Smart and Connect the World

RSS header - this is hidden

RoboMQ on Libelium IoT Gateway to unlock device data to SaaS, cloud and on-premise applications

Posted by Bramh Gupta on Nov 20, 2017 4:45:24 PM

November 20, 2017

RoboMQ (McLean, VA) joins Libelium’s IoT ecosystem of over 100 partners to provide seamless integration of the device and sensor data to cloud, SaaS and on-premise applications. IoT is revolutionizing enterprises and businesses with availability of information through devices and sensors. “The great interoperability of our IoT platform allows customers to access new market opportunities by connecting any sensor or even any device to any cloud platform through any communication protocol”, Alicia Asín, Libelium CEO, states.

Read More

Topics: Internet of Things, IoT, Libelium, IoT Gateway

Gartner lists RoboMQ as representative iPaaS vendor

Posted by Bramh Gupta on Jun 29, 2017 12:24:14 PM

We are excited to share the  news of our inclusion in "Gartner Market Guide for Application Integration Platforms" published June , 2017. We have been listed as one of the representative iPaaS (Integration Platform as a Service) vendors.
Read More

Topics: AMQP, Application Integration, EAI, Hybrid Cloud, Industrial Internet, Integration, Internet of Things, IoT middleware, boomi, Cloud, Container, Docker, Hybrid Integration Platform, informatica, IoT, iPaaS, iron.io, iSaaS, jitterbit, MFT, Microservices, middleware, MQTT, mulesoft, REST, REST Adapter, robomq.io, SaaS, SaaS Integration, SOA

RoboMQ Launches on IBM Cloud Marketplace

Posted by user on Apr 13, 2016 11:15:00 AM

RoboMQ is proud to announce that it has officially launched its IOT and Enterprise Application Integration Services on the IBM Cloud Marketplace.  You can visit the site using the link below.
Read More

Topics: Data Analytics, IBM, Integration, Intenet of Things, IoT, iPaaS, M2M, middleware, SaaS

A Robot Firefighter that wears a Fitbit...

Posted by user on Mar 1, 2016 5:59:00 PM

Read More

Topics: IoT

Silicon Review - RoboMQ is a Top 10 Fastest Growing IoT Company

Posted by user on Feb 1, 2016 10:22:00 AM

Read More

Topics: Active Directory, ADP, dockers, Integration, boomi, CRM, informatica, IoT, iron.io, jitterbit, M2M, Microservices, middleware, mulesoft, SaaS, SOA

Ron Swanson and Microservices

Posted by user on Jan 26, 2016 11:48:00 AM

 

Read More

Topics: AMQP, Data Analytics, EAS, ERP, Integration, Big Data, Container, CRM, Data, Docker, IoT, iPaaS, Microservices, middleware, Ron Swanson, SOA

Announcing Hybrid Messaging Cloud!

Posted by user on Nov 3, 2015 7:25:00 PM


Read More

Topics: Analytics, Big Data, Internet of Things, IoT, IoT middleware, middleware, MQTT

Unlocking SCADA Modbus networks to Internet of Things (IoT)

Posted by Bramh Gupta on May 5, 2015 4:46:00 PM

With the rapid expansion of sensors, devices, and applications all interconnecting at an increasing rate, there is an increasing need for integrating these devices to cloud based enterprise systems or analytics platforms.  Many existing sensors and devices utilized within industrial networks that communicate over Modbus protocol have been in use for many years. Modbus based automation systems are prevalent across the spectrum of industrial automation and control from manufacturing to steel making, power plants, utilities, oil & gas, transportation, and energy applications.

Modbus based system are critical part of the industrial Internet for automation and control. However, these systems have a lot of valuable information, which could be unlocked and be used by analytics and enterprise systems. The mere act of unlocking this data can have the “networking effect” of data and create value manifold.


Bridging SCADA networks to Internet of Things (IoT) using RoboMQ

Modbus is a relatively simple serial protocol typically used in master-slave applications to monitor and program devices, sensors, and instruments in a SCADA (supervisory control and data acquisition) network.  It is an ideal protocol for applications where remote communication and consistent interface to a large variety of equipment from a number of manufacturers is required using simple communication. However, with devices, sensors, and industrial networks increasingly becoming new players in the Internet of Things (IoT), there is an ever-increasing need to integrate these existing systems more efficiently to cloud and enterprise networks. Using open standard technologies  these industrial networks can be bridged to the wider Internet of people, processes and things.

With this vision, we recently added a Modbus connector to RoboMQ suite of connectors and adapters called “ThingsConnect”. With more and more connectors and adapters being added to ThingsConnect, we continue to deliver our promise of connecting any device, sensor or thing to any cloud, application or system.

RoboMQ Modbus adapter

What does this Modbus adapter mean for your industrial applications? 

Although Modbus device networks currently provide many levels of information and management capabilities, integrating them through “ThingsConnect” will expand access into the IoT world with many value-added benefits like:
  • Integrate with management, analytics, or data driven alert tools useful for collecting and reporting real-time statistical information
  • Fill in coverage gaps where central and consistent monitoring is key for mission critical equipments
  • Integrate with data storage solutions for historical tracking of equipment status/failures useful for training of operations staff, making it easier to identify the root cause of problems
  • Make SCADA or Modbus based applications an integral part of enterprise applications

For example, an energy company may have an established network of sensors reporting environment variables like CO2, pressure, and temperature to a dashboard accessible to the floor operations staff only. You could unlock this data and make it available to enterprise systems, analytics engines and use it across a wider base of systems and people. A much more effective decision-making can be done using this approach. Throw in machine learning and you build smarter applications that learn from the data.

The Modbus connector offers tremendous efficiency in having the ability to integrate cloud and enterprise hosted applications within existing industrial applications and solutions.  In addition, as a core feature of RoboMQ, it ensures guaranteed and reliable delivery of the information through its robust and scalable IoT infrastructure.  Finally, using open standards based protocols like MQTT (MQ for Telemetry), AMQP, STOMP, and REST all supported by RoboMQ in a interoperable and cross convertible fashion helps deliver a data integration platform where virtually any device can connect to any enterprise system over any communication channel.

With industries, small to large and local to global, increasingly relying on sensors and devices to collect information from the environment and making decisions upon it, the need to build a network of intelligent “things” while ensuring seamless connectivity to existing Modbus and SCADA networks is a paramount one!!
Read More

Topics: Industrial Internet, Internet of Things, IoT, ModBus, Oil & gas, robomq.io, SCADA, SCADA bridge, steel making, utilities

Device to Dashboard – real time analytics of sensor data with no programming needed

Posted by user on May 5, 2015 3:42:00 PM

Remote real-time monitoring and analytics of device and sensor data has always been a need. Fortunately, it has become an economically viable option due to confluence of multiple factors, like reduction in price of micro-controllers and microprocessors, easy and cheap connectivity options and availability of standard technologies and standard protocols.
Read More

Topics: Analytics, Big Data, Internet of Things, IoT, Monitor, robomq.io, Visualization

RoboMQ REST adapter for cross protocol conversion

Posted by Bramh Gupta on Apr 4, 2015 10:20:00 AM

RoboMQ, Internet ofThings (IoT) middleware platform is built ground up to allow collaboration and data interchange between any device to any system, cloud or thing.   It has a rich set of connectors and adapters to allow this promise. These set of connectors and adapter are collectively part of “ ThingsConnect” suite.
We recently released for GA (General Availability), the REST adapter for RoboMQ. REST is a common architectural style for exposing the application services over HTTP/HTTPS. It follows the basic model of how web works and supports operations to retrieve or modify objects identified as URI resource. We all are familiar with the operation like GET for reading an object and POST for creating an object. The beauty of REST is the simplicity, the convenience and the wide support it has across all platforms, programming languages and SaaS and mobile applications.
So what does it mean for you?  Quite simply you can integrate the device and sensors a.k.a. “things” to your applications using the very familiar and widely available REST interfaces that you may already be using.
How does it work? We know that the RoboMQ is a message-oriented middleware for IoT and application integration. There are numerous benefits of a Message Oriented Middleware (MOM), the primary ones being the reliable and guaranteed delivery and the ability to develop decoupled applications. The decoupling allows faster time to market (TTM), lower cost of development and ability to plug and play components allowing future proofing and flexibility to change as the needs and the business conditions change. You can learn more about these benefits at our readthedocspage.
With the messaging systems, you can either get (read) a message or publish (write) a message. It is that simple and this simplicity is reason behind the benefits that it offers. REST works in a vey similar style as well. For any resource, you can read it by GET operation on the resource. You can create or write a new resource by using the familiar POST operations.   We have basically mapped the REST GET operation to getting a message and the POST operation to publishing a message.   It’s that simple!!
You must be thinking – Ok, I get the mapping of the operations, but how do you identify a resource much the way we are used to doing it using the URI in REST?  Just as in messaging you read or write to a queue (or to be technically correct, route a message to a queue). The resource identification is at the queue level. A URI consists of the exchange name, queue name and the routing key which is used to identify a unique destination from which a to GET or POST a message.
Schematic of REST operations on RoboMQ
To summarize the operations of the RoboMQ REST adapter:
HTTP GET operation:read the message from a queue identified by its URI.
URI:/exchange/queue/routingKey
GET operation will read exactly one message if available from the Queue, much like the read from a Queue using any of the messaging protocols like MQTT, AMQP, Stomp, WebSTOMP etc.
HTTP POST operation:publish a message to a destination identified by its URI.
URI:  /exchange/routingKey
POST operation will publish the message at the exchange with a routing key. The RoboMQ platform will deliver the message to the recipient who has subscribed to these messages based on the routing key.
And did I tell you; you are not restricted to sending and receiving a message in REST, or for that matter in any of the protocols. RoboMQ supports full cross protocol conversion.  You can send a message in REST and receive it using any of the protocols like MQTT, Stomp, WebSTOMP or AMQP and vice-versa.
As you can see, this adapter makes the integration with RoboMQ extremely simple along the lines of REST calls you are so used to. Check it out and lets know how you find it. You can visit us at RoboMQ, signup for a free trial or just say hi at info@robomq.io.
Read More

Topics: AMQP, Internet of Things, IoT, IoT middleware, MQTT, REST, REST Adapter