Click here to close now.


Industrial IoT Authors: Liz McMillan, Sanjeev Sharma, Tim Hinds, Elizabeth White, Ed Featherston

Related Topics: Industrial IoT

Industrial IoT: Article

When Should Java And XML Be Used For Messaging?

When Should Java And XML Be Used For Messaging?

When does it make sense to use JMS (Java Message Service) and XML to support a heterogeneous messaging environment? Most buzzword-compliant people talk about JMS and XML when thinking about developing a messaging solution for their organization.

While in most cases this is the correct answer, we need to understand the requirements we're trying to fulfill before giving an answer. For example:

  • Can the solution be deployed using asynchronous communications or does it require synchronous behavior?
  • Will the solution be used in the intranet or extranet?
  • What are the messaging paradigms supported by your system?
  • Does the underlying messaging system support JMS?
  • What qualities of service (QoS) are supported by the messaging system?
  • What are the characteristics of the information to be published on the network?
  • Are e-mail messages a requirement?
  • What are the possible messaging systems the solution will be deploying against?
In short, we need to understand the characteristics of the problem before we can justify the use of any technology - in this case JMS and XML. Let me first give a brief introduction to JMS and explain the role of XML. My goal this month is to help you understand the requirements that XML and JMS are attempting to meet.

Sun, IBM, Modulus, NEON, OpenHorizon, Oracle, TIBCO, and Vitria developed the JMS specification. The purpose was to define a common API that would enable Java developers to use the same messaging system. In the JMS specification there's a clear distinction between the application and the message provider layers. The software developer is responsible for coding his or her application against the JMS interfaces; the message provider is responsible for coding the implementation to the interfaces. The idea behind this approach is to decouple the client application from the specifics of the messaging system. This allows the message provider layer to plug into the application layer. JMS defines two types of messaging paradigms:

  • Point-to-point
  • Publish/subscribe
The point-to-point paradigm follows a producer/consumer pattern that allows the producer application to write information to a queue and a consumer application to read it from the queue (see Figure 1). The queue mechanism identifies the decoupling point between the producer application and the consumer application. The producer application doesn't depend on the consumer application to access the queue to write to it, or vice versa. Some messaging systems provide QoS that enables persistence of the information stored inside a queue.

The publish/subscribe paradigm follows an observer pattern with explicit interest defined (see Figure 2). This approach allows subscriber applications to specify the types of events they're interested in receiving and allows the publishing application to broadcast messages independent of interested parties. The mapping between interested subscribers and published content is facilitated by the messaging system. This allows subscribers to publish information totally independent of recipients and vice versa. Some messaging systems provide QoS that enables the persistence of published messages for future processing.

JMS developers are responsible for selecting the message provider and for specifying the type of messaging model they want to implement. In addition, some JMS services are supported by the JMS layer independent of the underlying messaging implementation. These are:

  • Transactions
  • Message filtering
These need to be supported by the JMS provider implementation layer, however.

Most messaging systems, including the JMS specification, are agnostic when it comes to message content. They categorize message content as:

  • Basic types (int, float, char, long, etc.)
  • Text (string)
  • Bytes (byte arrays)
This is where XML comes to the rescue by providing the mechanisms to define the content of a message. This information is used by both sender and receiver clients to manipulate complex objects. The XML tags allow the sender application to serialize an object for future consumption by the receiver application. It's the responsibility of the receiver application to reconstruct the object for further manipulation.

Another advantage of using XML for defining the content of a message is that it provides a platform-independent mechanism for exchanging information between heterogeneous applications. This means a Visual Basic application can package an object using XML and send it to a Java application where it can be reconstructed from the XML message.

It's important to realize that XML doesn't provide a communications transport like TIBCO, MQSeries, IIOP, SMTP, and HTTP. However, it can work with any of these transports to provide message- content abstraction. One example of how XML facilitates the creation of communication transport is the use of HTTP and XML to develop XML RPCs.

Does this mean that the buzzword-compliant people know best? I don't think so! However, they pay enough attention to know what the technologists are saying. As mentioned earlier, JMS provides a communication abstraction layer for messaging while XML provides a message content abstraction layer. JMS enables the use of XML via its TextMessage content type. This enables string-based messages and XML text (see Listing 1).

When JMS and XML?
JMS and XML provide a total abstraction of communications transport and data content. Given this statement, why should you care about any requirements? Isn't this the solution to all your messaging needs? Let's revisit the questions asked earlier:

Q: Can the solution be deployed using asynchronous communications or does it require synchronous behavior?
A: JMS deals with asynchronous communications. If you need to manipulate synchronous flows like RMI, CORBA, or HTTP, you may want to consider using synchronous protocols. While you can implement synchronous behavior with asynchronous protocols, this isn't the norm and it's more difficult.

Q: Will this solution be used in the intranet or extranet?
A: JMS deals with messaging in thje intranet. Publish/subscribe and queue management systems aren't designed to deal with unreliable networks like the Internet. If you want to set up extranet communications, you need to consider XML RPC (SOAP) or SMTP (e-mail).

Q: What are the messaging paradigms supported by your system?
A: Does the underlying system support publish/subscribe or point-to-point? Some systems support only one or the other. Publish/subscribe systems have been optimized for broadcast (e,g., TIBCO). They haven't been optimized for point-to-point. Similarly, queue management systems have been optimized to provide message persistence via queues and point-to-point communications. They haven't been optimized for publish/subscribe.

Q: Does the underlying messaging system support JMS?
A: If your corporate messaging system doesn't support JMS, you may be stuck with their proprietary Java interfaces or you may need to develop your own JNI interfaces.

Q: What QoS are supported by the messaging system?
A: Does the JMS implementation that comes with your messaging system support guaranteed delivery, transactions, and message filtering? If your application requires transactions and your JMS implementation doesn't support them, this may be a problem. You may be forced to evaluate a different JMS provider. If your JMS provider supports message persistence, where is the persistence storage happening, in an RDBMS or proprietary storage? Persistence may be an issue if your JMS provider requires you to purchase a specific RDBMS.

Q: What are the characteristics of the information to be published on the network?
A: If you're using publish/subscribe, what type of information are you publishing? This issue is particularly important if you're using publishing as an event mechanism. Events are normally regarded as lightweight messages. Because of this requirement, it may not make sense to inquire about the overhead of wrapping a simple event value in an XML message. The subscribers may be listening on a topic called shipping orders, and the only content inside the event may be the order number. In this situation there's no need to create an XML message to publish the information. However, if subscribers are listening for the complete order with all of its parameters, it makes sense to package the order object inside an XML message for further processing by the subscriber application.

Q: Are e-mail messages a requirement?
A: JMS doesn't handle e-mail sending or receiving. That's the purpose of the JavaMail APIs. If the application needs to support e-mail for asynchronous messaging, then JMS isn't the answer. However, if your application needs to use an intranet-based messaging system like TIBCO, and you want to implement an e-mail gateway, the combination of JMS and JavaMail is ideal.

Q: What are the possible messaging systems that the solution will be deployed against?
A: If the solution being developed will be used only against one messaging system, it may not make sense to use JMS. This is the case if there's no JMS provider for a particular messaging framework but there is a Java API for that system. However, if the solution can be deployed against multiple messaging systems, it makes sense to leverage a communications abstraction layer.

JMS and XML are an ideal combination and can be deployed to provide a total abstraction solution for messaging and data content. However, you need to understand your requirements clearly before making the technology call. Therefore, it's important to know the limitations and correct usage of the JMS and XML technologies.

More Stories By Israel Hilerio

Israel Hilerio is a program manager at Microsoft in the Windows Workflow Foundation team. He has 15+ years of development experience doing business applications and has a PhD in Computer Science.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

@ThingsExpo Stories
The buzz continues for cloud, data analytics and the Internet of Things (IoT) and their collective impact across all industries. But a new conversation is emerging - how do companies use industry disruption and technology enablers to lead in markets undergoing change, uncertainty and ambiguity? Organizations of all sizes need to evolve and transform, often under massive pressure, as industry lines blur and merge and traditional business models are assaulted and turned upside down. In this new data-driven world, marketplaces reign supreme while interoperability, APIs and applications deliver un...
Too often with compelling new technologies market participants become overly enamored with that attractiveness of the technology and neglect underlying business drivers. This tendency, what some call the “newest shiny object syndrome,” is understandable given that virtually all of us are heavily engaged in technology. But it is also mistaken. Without concrete business cases driving its deployment, IoT, like many other technologies before it, will fade into obscurity.
Today air travel is a minefield of delays, hassles and customer disappointment. Airlines struggle to revitalize the experience. GE and M2Mi will demonstrate practical examples of how IoT solutions are helping airlines bring back personalization, reduce trip time and improve reliability. In their session at @ThingsExpo, Shyam Varan Nath, Principal Architect with GE, and Dr. Sarah Cooper, M2Mi's VP Business Development and Engineering, will explore the IoT cloud-based platform technologies driving this change including privacy controls, data transparency and integration of real time context w...
"Matrix is an ambitious open standard and implementation that's set up to break down the fragmentation problems that exist in IP messaging and VoIP communication," explained John Woolf, Technical Evangelist at Matrix, in this interview at @ThingsExpo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
WebRTC converts the entire network into a ubiquitous communications cloud thereby connecting anytime, anywhere through any point. In his session at WebRTC Summit,, Mark Castleman, EIR at Bell Labs and Head of Future X Labs, will discuss how the transformational nature of communications is achieved through the democratizing force of WebRTC. WebRTC is doing for voice what HTML did for web content.
The IoT is upon us, but today’s databases, built on 30-year-old math, require multiple platforms to create a single solution. Data demands of the IoT require Big Data systems that can handle ingest, transactions and analytics concurrently adapting to varied situations as they occur, with speed at scale. In his session at @ThingsExpo, Chad Jones, chief strategy officer at Deep Information Sciences, will look differently at IoT data so enterprises can fully leverage their IoT potential. He’ll share tips on how to speed up business initiatives, harness Big Data and remain one step ahead by apply...
Nowadays, a large number of sensors and devices are connected to the network. Leading-edge IoT technologies integrate various types of sensor data to create a new value for several business decision scenarios. The transparent cloud is a model of a new IoT emergence service platform. Many service providers store and access various types of sensor data in order to create and find out new business values by integrating such data.
The broad selection of hardware, the rapid evolution of operating systems and the time-to-market for mobile apps has been so rapid that new challenges for developers and engineers arise every day. Security, testing, hosting, and other metrics have to be considered through the process. In his session at Big Data Expo, Walter Maguire, Chief Field Technologist, HP Big Data Group, at Hewlett-Packard, will discuss the challenges faced by developers and a composite Big Data applications builder, focusing on how to help solve the problems that developers are continuously battling.
There are so many tools and techniques for data analytics that even for a data scientist the choices, possible systems, and even the types of data can be daunting. In his session at @ThingsExpo, Chris Harrold, Global CTO for Big Data Solutions for EMC Corporation, will show how to perform a simple, but meaningful analysis of social sentiment data using freely available tools that take only minutes to download and install. Participants will get the download information, scripts, and complete end-to-end walkthrough of the analysis from start to finish. Participants will also be given the pract...
WebRTC services have already permeated corporate communications in the form of videoconferencing solutions. However, WebRTC has the potential of going beyond and catalyzing a new class of services providing more than calls with capabilities such as mass-scale real-time media broadcasting, enriched and augmented video, person-to-machine and machine-to-machine communications. In his session at @ThingsExpo, Luis Lopez, CEO of Kurento, will introduce the technologies required for implementing these ideas and some early experiments performed in the Kurento open source software community in areas ...
Internet of Things (IoT) will be a hybrid ecosystem of diverse devices and sensors collaborating with operational and enterprise systems to create the next big application. In their session at @ThingsExpo, Bramh Gupta, founder and CEO of, and Fred Yatzeck, principal architect leading product development at, discussed how choosing the right middleware and integration strategy from the get-go will enable IoT solution developers to adapt and grow with the industry, while at the same time reduce Time to Market (TTM) by using plug and play capabilities offered by a robust IoT ...
Today’s connected world is moving from devices towards things, what this means is that by using increasingly low cost sensors embedded in devices we can create many new use cases. These span across use cases in cities, vehicles, home, offices, factories, retail environments, worksites, health, logistics, and health. These use cases rely on ubiquitous connectivity and generate massive amounts of data at scale. These technologies enable new business opportunities, ways to optimize and automate, along with new ways to engage with users.
The Internet of Things (IoT) is growing rapidly by extending current technologies, products and networks. By 2020, Cisco estimates there will be 50 billion connected devices. Gartner has forecast revenues of over $300 billion, just to IoT suppliers. Now is the time to figure out how you’ll make money – not just create innovative products. With hundreds of new products and companies jumping into the IoT fray every month, there’s no shortage of innovation. Despite this, McKinsey/VisionMobile data shows "less than 10 percent of IoT developers are making enough to support a reasonably sized team....
“In the past year we've seen a lot of stabilization of WebRTC. You can now use it in production with a far greater degree of certainty. A lot of the real developments in the past year have been in things like the data channel, which will enable a whole new type of application," explained Peter Dunkley, Technical Director at Acision, in this interview at @ThingsExpo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
Through WebRTC, audio and video communications are being embedded more easily than ever into applications, helping carriers, enterprises and independent software vendors deliver greater functionality to their end users. With today’s business world increasingly focused on outcomes, users’ growing calls for ease of use, and businesses craving smarter, tighter integration, what’s the next step in delivering a richer, more immersive experience? That richer, more fully integrated experience comes about through a Communications Platform as a Service which allows for messaging, screen sharing, video...
SYS-CON Events announced today that Dyn, the worldwide leader in Internet Performance, will exhibit at SYS-CON's 17th International Cloud Expo®, which will take place on November 3-5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Dyn is a cloud-based Internet Performance company. Dyn helps companies monitor, control, and optimize online infrastructure for an exceptional end-user experience. Through a world-class network and unrivaled, objective intelligence into Internet conditions, Dyn ensures traffic gets delivered faster, safer, and more reliably than ever.
The IoT market is on track to hit $7.1 trillion in 2020. The reality is that only a handful of companies are ready for this massive demand. There are a lot of barriers, paint points, traps, and hidden roadblocks. How can we deal with these issues and challenges? The paradigm has changed. Old-style ad-hoc trial-and-error ways will certainly lead you to the dead end. What is mandatory is an overarching and adaptive approach to effectively handle the rapid changes and exponential growth.
Mobile messaging has been a popular communication channel for more than 20 years. Finnish engineer Matti Makkonen invented the idea for SMS (Short Message Service) in 1984, making his vision a reality on December 3, 1992 by sending the first message ("Happy Christmas") from a PC to a cell phone. Since then, the technology has evolved immensely, from both a technology standpoint, and in our everyday uses for it. Originally used for person-to-person (P2P) communication, i.e., Sally sends a text message to Betty – mobile messaging now offers tremendous value to businesses for customer and empl...
Can call centers hang up the phones for good? Intuitive Solutions did. WebRTC enabled this contact center provider to eliminate antiquated telephony and desktop phone infrastructure with a pure web-based solution, allowing them to expand beyond brick-and-mortar confines to a home-based agent model. It also ensured scalability and better service for customers, including MUY! Companies, one of the country's largest franchise restaurant companies with 232 Pizza Hut locations. This is one example of WebRTC adoption today, but the potential is limitless when powered by IoT.
You have your devices and your data, but what about the rest of your Internet of Things story? Two popular classes of technologies that nicely handle the Big Data analytics for Internet of Things are Apache Hadoop and NoSQL. Hadoop is designed for parallelizing analytical work across many servers and is ideal for the massive data volumes you create with IoT devices. NoSQL databases such as Apache HBase are ideal for storing and retrieving IoT data as “time series data.”