topics that matter; ideas worth sharing

share a tip, submit a link, add something new

Understanding Java messaging and JMS

Be the first to comment | 1I like it!
May 7, 2001, 10:07 AM —  Unix Insider — 

Foreword


Java and Java-related technologies continue to be introduced and
continue to mature. As Java becomes more enterprise ready, as
opposed to application-platform centric, we are seeing the
introduction of more sophisticated Java-related middleware. This
month we discuss one such type of middleware, JMS. The JMS
specification will no doubt result in many new products in the
market. We describe what JMS is all about and how it compares with
alternate solutions. IT architects will now need to consider this
technology when designing messaging infrastructures.

--Kara Kapczynski

In October 1998, JavaSoft released the Java Message Service (JMS)
specification v1.0.1, an API for accessing enterprise
messaging systems from Java. Because JMS is equipped to handle both
synchronous and asynchronous messaging, it represents a possible
alternative to strictly synchronous RMI.


This article will attempt both to define JMS and to compare it with other
Java messaging or traditional message-oriented middleware (MOM) messaging paradigms. The main
objective is to help you understand where JMS might fit into a
Java-based, enterprise-wide application architecture.


JMS is a set of interfaces and associated semantics that define how
a JMS client accesses the facilities of an enterprise messaging
product. Enterprise messaging is recognized as an essential tool for
building enterprise applications and ecommerce systems, and JMS
provides a common way for Java programs to create, send, receive,
and read an enterprise messaging system's messages.


With a solid implementation of JMS, one can implement client/server or
server/server asynchronous applications without CORBA. However, most ISP
implementations of JMS are by small firms that are trying to implement a
fairly comprehensive spec. Sun, though, has clearly stated that a vendor
does not need to implement the entire spec, only domains within the spec.
Sun has also indicated that there are domains outside of the scope of the
spec that should be implemented in order to provide a truly enterprise-wide
and robust messaging environment.


EAI = MOM = JMS

Enterprise Application Integration (EAI) using MOM products is becoming an essential component for integrating
intracompany operations (see August 1999's IT Architect column for more details). While JMS can be used by
itself and not just as a wrapper for MOMs, Sun's primary intention
is for corporations to use it in conjunction with such MOM products
as TIBCO or MQSeries.


The strategic intention of some JMS vendors is to provide Java
interfaces to MQSeries and TIBCO -- interfaces that allow the
developer to program in pure JMS using Java APIs, while using
MQSeries, TIBCO, and the like as the low-level transport. This
means an organization might not need to change its underlying
transport middleware; JMS gives developers a standard Java API so
messages can be sent transparently across the organization via TIBCO
or MQSeries.


JMS is clearly the missing piece in the enterprise Java
architecture, and Sun has already introduced a number of major
service APIs -- JDBC (for database access), JNDI (for naming and
directory services), and a Java mail API -- that are required in order to
write applications that integrate across the enterprise.


The JMS object model

The two dominant messaging approaches in use today and defined in the spec
are the Topic, or point-to-point messages, and the Queue, or
publish-and-subscribe messages. Because many message

I like it!
Post a comment
The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.
Resources
White Paper

Symantec Backup Exec 12 and Backup Exec System Recovery 8 deliver industry leading Windows data protection and system recovery. Download this whitepaper to find out the top reasons to upgrade and how to get continuous data protection and complete system recovery.

Webcast

Data and system loss — from a hard drive failure, malicious attack, natural disaster, or simple human error — can happen anytime. Don’t leave your business vulnerable. Make sure you have a secure recovery strategy in place. Symantec's latest backup and system recovery technology can efficiently restore critical applications, individual emails and documents and even restore your entire system in minutes in the event of a loss.

White Paper

Businesses face a growing challenge to ensure that the IT environment is properly protected. Backup Exec 12 integrates with other applications in the Symantec family of products, to complement your current data protection strategy, keep your data securely backed up and make it recoverable when you need it most.

Free stuff
Featured Sponsor

Get a broad understanding of important regulations and how you can make sure your site is in adherence.





Learn how VeriSign SGC-enabled SSL Certificates can help improve site security and customer confidence in the free white paper, "How to Offer the Strongest SSL Encryption." In this paper you will learn the differences between weak and strong encryption and what they mean for your site's performance.

Get VeriSign's free white paper: "The Latest Advancements in SSL Technology" and learn about the benefits of strong SSL encryption, Extended Validation (EV) SSL and security trust marks and what these SSL offerings can do for your site.

Now with Extended Validation (EV) SSL available from VeriSign, you can show your customers that they can trust your site. Learn about EV SSL benefits in this free VeriSign white paper.

More Resources