12.1 Introduction
Performance and stability of an application using JMS are largely governed by:
- Efficient and safe application usage of JMS
- The most efficient messaging and appserver topology, but also one that provides adequate failure handling
- Optimal configuration settings of each individual appserver and its resources
Stability is also important for maintaining performance; the application will need to be able to cope with failures in a graceful manner. If it is unable to do this then performance will degrade and the service provided by the application becomes unacceptable.
If you are new to JMS, then you should first look at chapter 10, "Asynchronous messaging", of the redbook WAS V6 System Management and Configuration Handbook, SG24-6451.
Also, the Trade 6 application is used in our examples, so familiarity with this application allows you to better understand what is being described. Some information about how Trade 6 uses JMS can be found in 12.8.1, What does Trade 6 use the default messaging provider for?. Also, refer to the document tradeTech.pdf coming with the Trade 6 download package. Trade 6 can be downloaded from:
http://www.ibm.com/software/webservers/appserv/performance.html