Red Hat DocumentationFuse Message BrokerToggle FramesPrintFeedback

Introduction

JMS, and messaging in general, can be hard to grasp without concrete examples. This guide explores the basics of JMS using a combination of general knowledge and runnable samples.

Overview

This book is intended for developers that are unfamiliar with messaging and JMS. It describes the basic concepts involved in building messaging applications with JMS. It then walks you through running and deploying a number of basic application samples.

The included samples can be deconstructed to further explore the JMS APIs.

Using the book

The book is broken into three sections:

  1. ???? describes the basic concepts used when developing JMS applications.

  2. ???? through ???? are samples that demonstrate the basic JMS concepts.

  3. ???? describes different ways you can modify the samples to further explore JMS.

What you will see

In these samples, the standard input and standard output displayed in the console represents data flows to and from applications and Internet-enabled devices such as:

  • Application software for accounting, auditing, reservations, online ordering, credit verification, medical records, and supply chains

  • Real-time devices with embedded controls such as monitor cameras, cell phones, medical delivery systems, and climate control systems, and machinery

  • Distributed knowledge bases such as collaborative designs, service histories, medical histories, and workflow monitors

What is demonstrated

The samples demonstrate the basic JMS features, as follows:

  • publish and subscribe messaging—Messages are published to a destination and multiple consumers can subscribe to receive the messages.

  • point-to-point messaging—Messages are published to a destination and a single consumer can receive the message.

  • request and reply—The initiator of the transaction expects a reply to its message.

  • test loop—This sample shows how quickly messages can be sent and received in a test loop.

Comments powered by Disqus