Book Image

HornetQ Messaging Developer's Guide

By : Piero Giacomelli
Book Image

HornetQ Messaging Developer's Guide

By: Piero Giacomelli

Overview of this book

<p>Messages and information can be exchanged at exponential speed with JBoss HornetQ asynchronous messaging middleware. Learn how to use the JAVA open source Message Oriented Framework, to build a high-performance, multi-protocol, embeddable, clustered system and manage millions of messages per second.<br /><br />In the HornetQ Messaging Developer’s Guide you will find the most common applications of a message exchanger with example code, as part of real-world scenarios. This practical and applicable guide increases reader knowledge chapter by chapter, covering basics to the most advanced features.<br /><br />You will start from a clean installation of a HornetQ sever and, having progressively become a HornetQ master, will finish by being able to use the framework embedded in your software and sharing information in a cluster environment.<br /><br />Starting from writing and reading a single message, we will discover more advanced features like managing queues, clustering the server, and controlling the undelivered messages. The book deals with a real-world advanced medical scenario as the main example that will lead you from learning the basics to the advanced features of HornetQ.</p>
Table of Contents (18 chapters)
HornetQ Messaging Developer's Guide
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Basic HornetQ configuration


Before discussing how to make HornetQ run as a service or the JBoss AS integration, we first need to understand how to configure the HornetQ standalone server. As we mentioned in Chapter 1, Getting Started with HornetQ, the HornetQ configuration files are stored in the HornetQ_ROOT\config folder. But if you take a look at the folder, you should see that it contains the following subfolders:

  • Jboss-as-5

  • Jboss-as-4

  • Stand-alone

And inside every one of these folders are two more subfolders named:

  • Clustered

  • Non-clustered

The folder structure mimics the possible configurations of HornetQ according to the type of installation and according to the fact that HornetQ runs in a clustered mode, which means that the workload can be shared between different nodes. The whole of Chapter 6, Advanced Programming Features of HornetQ will be devoted to understanding such concepts, so for the moment we will focus on the folder under HORNETQ_ROOT\config\standalone\non-clustered, where we...