An enterprise messaging system, enables applications to communicate with one another through the exchange of messages, also referred to as Message-Oriented Middleware(MOM). A message is a request, and/or event that contains information needed to coordinate communication between different applications or a report. Allowing you to separate the details about the destination system from the application code a message provides a level of abstraction.

• Provides a unified and single messaging API.





• Implements the JavaSoft JMS specification version 1.0.2a, including the latest JMS API.





• Supports messaging for applications that span different operating systems and machine architectures.





• Supports clustering.





• Can be configured by setting attributes from the WebLogic Administration using the JMS API to override values and/or Console.





• Supports messages containing Extensible Markup Language(XML).





• Supports for multicasting allowing the delivery of messages to a select group of hosts using an IP multicast address.





• Can use either a database or file for persistent message storage.





• By using the Java Transaction API(JTA) transactions allows interoperability between JMS applications and other resource managers(primarily databases). JMS applications can participate in transactions with other Java APIs that use JTA.





• Can be used with other BEA WebLogic Server APIs and facilities, such as JDBC connection pools, Servlets, Enterprise Java Beans (EJB), and RMI.

The figure above illustrates the WebLogic JMS architecture.

The major components of the JMS WebLogic Server architecture are illustrated in the figure above:

• WebLogic JMS servers implementing the messaging facility.





• The Java Naming and Directory Interface(JNDI), which provides a server lookup facility.





• Backing stores (file or database) for storing persistent data





• Client applications.