Optimizing use of JMS components
The Java Messaging Service (JMS) is used by J2EE applications for synchronous and asynchronous calls to back end applications and also as a communication mechanism between two parts of the same J2EE application. The parts of an application that rely on JMS need to have the correct underlying messaging topology and each component needs to be configured for optimal performance and stability.
This chapter describes how the various components for JMS interact, including such areas as connection and session pools. It will take the reader through manually configuring the JMS components for the Trade3 application and demonstrate running this on both an embedded JMS architecture and also with WebSphere MQ and WebSphere Business Integration Event broker.
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.