The notion of guaranteed delivery of Java Message Service messages has been
lightly touched on in other recently published articles on JMS. But what
really makes a JMS message "guaranteed"? Should you just take it on faith, or
would you like to know what's behind it?
This article answers these questions via a detailed discussion of message
persistence, internal acknowledgment rules, and message redelivery. Using
excerpts condensed from the book we coauthored, Java Message Service, we'll
explain how JMS guaranteed messaging works - including once-and-only-once
delivery semantics, durable subscriptions, failure and recovery scenarios,
and transacted messages.
JMS Guaranteed Messaging
There are three key parts to guaranteed messaging: message autonomy,
store-and-forward, and the underlying message acknowledgment semantics.
Before we discuss these parts, we need to revi... (more)
The Java API for XML Messaging (JAXM) is a new Java application programming
interface (API) that provides a standard way for Java applications to send
and receive Simple Object Access Protocol (SOAP) messages. The basic idea is
to allow developers to spend more time building, sending, receiving, and
deconstructing messages for their applications and less time programming
low-level XML communications routines. Developed through the Java Community
Process, JAXM provides a simple yet flexible standard API for developing and
deploying SOAP-based applications that can be truly interop... (more)
Benchmarking any distributed computing middleware product is a complex task.
Knowing how well a distributed infrastructure will perform under heavy load
with a large number of concurrently connected users is a key factor in
planning a development and deployment strategy.
With the advent of Java Message Service (JMS) as the standard for a global
class middleware infrastructure, development organizations can enjoy the
luxury of building distributed applications using a common set of APIs and
message delivery semantics. At the same time they can pick and choose from a
variety of JM... (more)
Applications are increasingly being developed "built-to-integrate," providing
the ability to easily expose key functionality through commonly defined
interfaces. Gartner calls this concept SODA, or Service-Oriented Development
of Applications, fitting into its overall Service-Oriented Architecture
landscape. When applied to the ever-present integration challenge, SODA
represents a transition to service-oriented integration.
In this presentation, Chappell will examine the leading choices for
supporting service-oriented integration: enterprise service buses (ESBs),
integration ... (more)
According to Gartner, Inc., vice president and research fellow Roy Schulte,
"a new form of enterprise service bus (ESB) infrastructure will be running in
most major enterprises by 2005." ESBs combine Web services, enterprise
messaging, transformation, and routing to provide an integration network that
can span global enterprises and encompass potentially thousands of
application end points. Application integration is a top priority among CIOs,
and as the current IT value center in the enterprise, IT organizations must
shift their focus from application development to application ... (more)