EJB Messaging, Part I: JMS and JavaMail

he proliferation of enterprise applications (CRM, ERP, SCM, etc.) and disparate enterprise resources (RDBMS/OODBMS, legacy data store, data warehouse, XML/flat file repository, etc.) has required many a developer to integrate these applications into cohesive systems. In such an environment, enterprise messaging has arisen as a dominant integration solution and an increasingly important component of loosely coupled, yet reliable, enterprise frameworks.

Implementing enterprise messaging across a message-oriented middleware (MOM) system enables disparate systems to exchange messages in a reliable, loosely coupled manner, which improves overall performance and system maintainability.

This month's 10-Minute Solution is the first in a two-part series examining the messaging options available to Enterprise Java Beans (EJBs) developers. This first part explains how EJBs participate in a messaging exchange and explores Java Message Service (JMS) and JavaMail resources, comparing their relative strengths and weaknesses as enterprise messaging conduits for your EJBs. Part 2 will take a close look at message-driven beans.

Author's Note: This 10-Minute Solution requires a fundamental knowledge of several enterprise Java APIs, including EJB, JMS, JavaMail, and JNDI.



How can session and entity EJBs participate in a messaging exchange?



By utilizing resource manager connection factories, EJBs access extra-container resources, such as JMS and JavaMail sessions, for enterprise messaging.

Next Page