This chapter presents the Java design techniques used to create the example application. We focus on Sun's Java Message Service (JMS) in the role it plays in enterprise messaging applications. We discuss supporting APIs, such as Sun's Java Naming and Directory Interface. Also, we will introduce WebSphere's JMS Listener, which is a component of extended messaging support in WebSphere Enterprise Services. The chapter concludes by extracting an application case from the example application, and providing a detailed description of the application design.
The document introduces Java Message Service (JMS) and its role in enterprise messaging for WebSphere Application Server 4.0. It covers the two messaging architectures—point‑to‑point (PTP) and publish/subscribe (pub/sub)—and describes the main JMS components such as connections, sessions, producers, and consumers.
It also explains how Java Naming and Directory Interface (JNDI) provides a portable naming service for JMS objects, allowing applications to obtain connection factories and destinations without hard‑coding provider‑specific details. This manual is written in Chinese.
JMS supports point‑to‑point (PTP) and publish/subscribe (pub/sub) architectures.