Example JMS topologies and scenarios
With Web and EJB based applications performance and scalability requirements often force the choice of topology.
With JMS, there is no one topology that will suit all situations. Different combinations of point-to-point, publish/subscribe, MDBs, and WebSphere MQ will drive topology requirements.
The choice of topology will depend on the correct balance of non-functional requirements of performance, security, scalability, maintenance, reliability, availability and cost, as well as providing a topology that can give the required function.
The example application that has been used throughout this book is Trade3, uses JMS as an asynchronous communication mechanism between two parts of the application. Trade3 has no need to communicate with a back-end system and so a lot of the more complicated topologies do not apply.
For the purposes of this section, two scenarios will be described using Trade3 with slightly different requirements for functionality and other criteria.
This section is intended to help you use some of the configuration options described in this chapter in working examples. It should also help you begin to understand the thought process in deciding on the best topology for your application. It will not describe all possible topologies, and there are many other topologies. To find out more on choosing a topology take a look at the document JMS Topologies and Configurations with WAS and WebSphere Studio Version 5 available at:
http://www.ibm.com/developerworks/websphere/library/techarticles/0310_barcia/barcia.htmlIf high availability is important to you then you may also wish to look at the chapters that cover high availability in this redbook. Especially Chapter 11, WebSphere Embedded JMS server and WebSphere MQ high availability.
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.