|By Israel Hilerio||
|October 16, 2000 12:00 AM EDT||
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?
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:
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:
- Message filtering
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)
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.
JMS and XML
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.
The 3rd International Internet of @ThingsExpo, co-located with the 16th International Cloud Expo - to be held June 9-11, 2015, at the Javits Center in New York City, NY - announces that its Call for Papers is now open. The Internet of Things (IoT) is the biggest idea since the creation of the Worldwide Web more than 20 years ago.
Nov. 28, 2014 05:00 PM EST Reads: 1,251
Cultural, regulatory, environmental, political and economic (CREPE) conditions over the past decade are creating cross-industry solution spaces that require processes and technologies from both the Internet of Things (IoT), and Data Management and Analytics (DMA). These solution spaces are evolving into Sensor Analytics Ecosystems (SAE) that represent significant new opportunities for organizations of all types. Public Utilities throughout the world, providing electricity, natural gas and water, are pursuing SmartGrid initiatives that represent one of the more mature examples of SAE. We have s...
Nov. 27, 2014 04:00 PM EST Reads: 1,338
The security devil is always in the details of the attack: the ones you've endured, the ones you prepare yourself to fend off, and the ones that, you fear, will catch you completely unaware and defenseless. The Internet of Things (IoT) is nothing if not an endless proliferation of details. It's the vision of a world in which continuous Internet connectivity and addressability is embedded into a growing range of human artifacts, into the natural world, and even into our smartphones, appliances, and physical persons. In the IoT vision, every new "thing" - sensor, actuator, data source, data con...
Nov. 27, 2014 04:00 PM EST Reads: 1,676
The Internet of Things is tied together with a thin strand that is known as time. Coincidentally, at the core of nearly all data analytics is a timestamp. When working with time series data there are a few core principles that everyone should consider, especially across datasets where time is the common boundary. In his session at Internet of @ThingsExpo, Jim Scott, Director of Enterprise Strategy & Architecture at MapR Technologies, discussed single-value, geo-spatial, and log time series data. By focusing on enterprise applications and the data center, he will use OpenTSDB as an example t...
Nov. 27, 2014 03:00 PM EST Reads: 1,500
How do APIs and IoT relate? The answer is not as simple as merely adding an API on top of a dumb device, but rather about understanding the architectural patterns for implementing an IoT fabric. There are typically two or three trends: Exposing the device to a management framework Exposing that management framework to a business centric logic Exposing that business layer and data to end users. This last trend is the IoT stack, which involves a new shift in the separation of what stuff happens, where data lives and where the interface lies. For instance, it's a mix of architectural styles ...
Nov. 27, 2014 03:00 PM EST Reads: 1,348
An entirely new security model is needed for the Internet of Things, or is it? Can we save some old and tested controls for this new and different environment? In his session at @ThingsExpo, New York's at the Javits Center, Davi Ottenheimer, EMC Senior Director of Trust, reviewed hands-on lessons with IoT devices and reveal a new risk balance you might not expect. Davi Ottenheimer, EMC Senior Director of Trust, has more than nineteen years' experience managing global security operations and assessments, including a decade of leading incident response and digital forensics. He is co-author of t...
Nov. 27, 2014 01:00 PM EST Reads: 1,695
The Internet of Things will greatly expand the opportunities for data collection and new business models driven off of that data. In her session at @ThingsExpo, Esmeralda Swartz, CMO of MetraTech, discussed how for this to be effective you not only need to have infrastructure and operational models capable of utilizing this new phenomenon, but increasingly service providers will need to convince a skeptical public to participate. Get ready to show them the money!
Nov. 27, 2014 11:00 AM EST Reads: 1,313
The Internet of Things will put IT to its ultimate test by creating infinite new opportunities to digitize products and services, generate and analyze new data to improve customer satisfaction, and discover new ways to gain a competitive advantage across nearly every industry. In order to help corporate business units to capitalize on the rapidly evolving IoT opportunities, IT must stand up to a new set of challenges. In his session at @ThingsExpo, Jeff Kaplan, Managing Director of THINKstrategies, will examine why IT must finally fulfill its role in support of its SBUs or face a new round of...
Nov. 27, 2014 10:00 AM EST Reads: 1,253
One of the biggest challenges when developing connected devices is identifying user value and delivering it through successful user experiences. In his session at Internet of @ThingsExpo, Mike Kuniavsky, Principal Scientist, Innovation Services at PARC, described an IoT-specific approach to user experience design that combines approaches from interaction design, industrial design and service design to create experiences that go beyond simple connected gadgets to create lasting, multi-device experiences grounded in people's real needs and desires.
Nov. 27, 2014 08:00 AM EST Reads: 1,270
Enthusiasm for the Internet of Things has reached an all-time high. In 2013 alone, venture capitalists spent more than $1 billion dollars investing in the IoT space. With "smart" appliances and devices, IoT covers wearable smart devices, cloud services to hardware companies. Nest, a Google company, detects temperatures inside homes and automatically adjusts it by tracking its user's habit. These technologies are quickly developing and with it come challenges such as bridging infrastructure gaps, abiding by privacy concerns and making the concept a reality. These challenges can't be addressed w...
Nov. 27, 2014 07:45 AM EST Reads: 1,545
The Domain Name Service (DNS) is one of the most important components in networking infrastructure, enabling users and services to access applications by translating URLs (names) into IP addresses (numbers). Because every icon and URL and all embedded content on a website requires a DNS lookup loading complex sites necessitates hundreds of DNS queries. In addition, as more internet-enabled ‘Things' get connected, people will rely on DNS to name and find their fridges, toasters and toilets. According to a recent IDG Research Services Survey this rate of traffic will only grow. What's driving t...
Nov. 27, 2014 07:00 AM EST Reads: 1,521
Scott Jenson leads a project called The Physical Web within the Chrome team at Google. Project members are working to take the scalability and openness of the web and use it to talk to the exponentially exploding range of smart devices. Nearly every company today working on the IoT comes up with the same basic solution: use my server and you'll be fine. But if we really believe there will be trillions of these devices, that just can't scale. We need a system that is open a scalable and by using the URL as a basic building block, we open this up and get the same resilience that the web enjoys.
Nov. 27, 2014 06:45 AM EST Reads: 1,417
Connected devices and the Internet of Things are getting significant momentum in 2014. In his session at Internet of @ThingsExpo, Jim Hunter, Chief Scientist & Technology Evangelist at Greenwave Systems, examined three key elements that together will drive mass adoption of the IoT before the end of 2015. The first element is the recent advent of robust open source protocols (like AllJoyn and WebRTC) that facilitate M2M communication. The second is broad availability of flexible, cost-effective storage designed to handle the massive surge in back-end data in a world where timely analytics is e...
Nov. 27, 2014 06:45 AM EST Reads: 1,353
We are reaching the end of the beginning with WebRTC, and real systems using this technology have begun to appear. One challenge that faces every WebRTC deployment (in some form or another) is identity management. For example, if you have an existing service – possibly built on a variety of different PaaS/SaaS offerings – and you want to add real-time communications you are faced with a challenge relating to user management, authentication, authorization, and validation. Service providers will want to use their existing identities, but these will have credentials already that are (hopefully) i...
Nov. 27, 2014 04:00 AM EST Reads: 1,264
"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 SYS-CON.tv interview at @ThingsExpo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
Nov. 27, 2014 04:00 AM EST Reads: 1,215
P2P RTC will impact the landscape of communications, shifting from traditional telephony style communications models to OTT (Over-The-Top) cloud assisted & PaaS (Platform as a Service) communication services. The P2P shift will impact many areas of our lives, from mobile communication, human interactive web services, RTC and telephony infrastructure, user federation, security and privacy implications, business costs, and scalability. In his session at @ThingsExpo, Robin Raymond, Chief Architect at Hookflash, will walk through the shifting landscape of traditional telephone and voice services ...
Nov. 26, 2014 02:00 PM EST Reads: 1,647
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at Internet of @ThingsExpo, James Kirkland, Chief Architect for the Internet of Things and Intelligent Systems at Red Hat, described how to revolutioniz...
Nov. 24, 2014 07:00 PM EST Reads: 1,741
Bit6 today issued a challenge to the technology community implementing Web Real Time Communication (WebRTC). To leap beyond WebRTC’s significant limitations and fully leverage its underlying value to accelerate innovation, application developers need to consider the entire communications ecosystem.
Nov. 24, 2014 12:00 PM EST Reads: 1,637
The definition of IoT is not new, in fact it’s been around for over a decade. What has changed is the public's awareness that the technology we use on a daily basis has caught up on the vision of an always on, always connected world. If you look into the details of what comprises the IoT, you’ll see that it includes everything from cloud computing, Big Data analytics, “Things,” Web communication, applications, network, storage, etc. It is essentially including everything connected online from hardware to software, or as we like to say, it’s an Internet of many different things. The difference ...
Nov. 24, 2014 11:00 AM EST Reads: 1,770
Cloud Expo 2014 TV commercials will feature @ThingsExpo, which was launched in June, 2014 at New York City's Javits Center as the largest 'Internet of Things' event in the world.
Nov. 24, 2014 09:00 AM EST Reads: 1,805