Java message service
Author(s)
Bibliographic Information
Java message service
(The Java series)
O'Reilly, 2001
Available at 3 libraries
  Aomori
  Iwate
  Miyagi
  Akita
  Yamagata
  Fukushima
  Ibaraki
  Tochigi
  Gunma
  Saitama
  Chiba
  Tokyo
  Kanagawa
  Niigata
  Toyama
  Ishikawa
  Fukui
  Yamanashi
  Nagano
  Gifu
  Shizuoka
  Aichi
  Mie
  Shiga
  Kyoto
  Osaka
  Hyogo
  Nara
  Wakayama
  Tottori
  Shimane
  Okayama
  Hiroshima
  Yamaguchi
  Tokushima
  Kagawa
  Ehime
  Kochi
  Fukuoka
  Saga
  Nagasaki
  Kumamoto
  Oita
  Miyazaki
  Kagoshima
  Okinawa
  Korea
  China
  Thailand
  United Kingdom
  Germany
  Switzerland
  France
  Belgium
  Netherlands
  Sweden
  Norway
  United States of America
Description and Table of Contents
Description
This text provides an introduction to Java Message Service (JMS), the standard Java application program interface (API) from Sun Microsystems that supports the formal communication known as "messaging" between computers in a network. JMS provides a common interface to standard messaging protocols and to special messaging services in support of Java programs. The messages exchange crucial data between computers, rather than between users - information such as event notification and service requests. Messaging is often used to co-ordinate programs in dissimilar systems or written in different programming languages. Using the JMS interface, a programmer can invoke the messaging services of IBM's MQSeries, Progress Software's SonicMQ, and other popular messaging product vendors. In addition, JMS supports messages that contain serialized Java objects and messages that contain Extensible Markup Language (XML) pages. Messaging is a powerful new paradigm that makes it easier to uncouple different parts of an enterprise application. Messaging clients work by sending messages to a message server, which is responsible for delivering the messages to their destination.
Message delivery is asynchronous, meaning that the client can continue working without waiting for the message to be delivered. The contents of the message can be anything from a simple text string to a serialized Java object or an XML document. Java Message Service shows how to build applications using the point-to-point and publish-and-subscribe models; how to use features like transactions and durable subscriptions to make an application reliable; and how to use messaging within Enterprise JavaBeans. It also introduces a new EJB type, the MessageDrivenBean, that is part of EJB 2.0, and discusses integration of messaging into J2EE.
Table of Contents
Preface 1. Understanding the Messaging Paradigm Enterprise Messaging The Java Message Service ( JMS) Application Scenarios RPC Versus Asynchronous Messaging 2. Developing a Simple Example The Chat Application 3. Anatomy of a JMS Message Headers Properties Message Selectors Message Types 4. Publish-and-Subscribe Messaging Getting Started with the B2B Application Temporary Topics Durable Subscriptions Publishing the Message Persistently JMSCorrelationID Request and Reply Unsubscribing 5. Point-to-Point Messaging Point-to-Point and Publish-and-Subscribe The QWholesaler and QRetailer Creating a Queue Dynamically Load Balancing Using Multiple QueueSessions Examining a Queue 6. Guaranteed Messaging, Transactions, Acknowledgments, and Failures Guaranteed Messaging Message Acknowledgments Message Groups and Acknowledgment Transacted Messages Lost Connections Dead Message Queues 7. Deployment Considerations Performance, Scalability, and Reliability To Multicast or Not to Multicast Security Connecting to the Outside World Bridging to Other Messaging Systems 8. J2EE, EJB, and JMS J2EE Overview J2EE: A United Platform The JMS Resource in J2EE The New Message-Driven Bean in EJB 2.0 9. JMS Providers IBM: MQSeries Progress: SonicMQ Fiorano: FioranoMQ Softwired: iBus Sun Microsystems: Java Message Queue BEA: WebLogic Server ExoLab: OpenJMS A. The Java Message Service API B. Message Headers C. Message Properties D. Message Selectors Index
by "Nielsen BookData"