Configure Messaging

WebLogic Server provides an enterprise-class messaging system that fully supports the JMS specification, and which also provides numerous extensions that go above and beyond the standard JMS APIs. It is tightly integrated into the WebLogic Server platform, allowing you to build highly secure J2EE applications that can be easily monitored and administered through the WebLogic Server console. In addition to fully supporting XA transactions, WebLogic Server messaging also features high availability through its clustering and service migration features while also providing seamless interoperability with other versions of WebLogic Server and third-party messaging vendors.

WebLogic Server messaging is comprised of these areas:

JMS Servers -- configuration resources that act as management containers for JMS queue and topic destinations in a JMS module that are targeted to them. A JMS server's primary responsibility for its destinations is to maintain information on which persistent store is used for any persistent messages that arrive on the destinations, and to maintain the states of durable subscribers created on the destinations.
Store-and-Forward Agents -- provide a mechanism for reliably delivering messages between applications that are distributed across WebLogic Server subsystems, in particular the WebLogic JMS and Web Services subsystems. Using the highly available SAF service, an application can send messages to an remote endpoint that is not available at the moment when the messages are sent, either because of network problems or system failures.
JMS System Modules -- contain global configuration JMS resources, such as queues, topics, templates, connections factories, and JMS store-and-forward (SAF) destinations, and are defined by XML documents that conform to the weblogic-jmsmd.xsd schema. JMS system modules are stored in the config\jms subdirectory of the domain directory, and a reference to the module is added in the domain's configuration file as a JMSSystemResource element. System modules are globally available for targeting to servers and clusters configured in the domain, and therefore are available to all applications deployed on the same targets and to client applications.
Messaging Bridge -- provides a forwarding mechanism between any two messaging products that support the JMS API. Use a messaging bridge to provide interoperability between separate implementations of WebLogic JMS, or between WebLogic JMS and another messaging product.

To configure WebLogic Server messaging:

For storing persistent messages, you can simply use the host server's default Persistent Store, which requires no configuration on your part. However, you can also create a dedicated file-based store or JDBC-accesible store for JMS. See Configure persistent stores.
Create a JMS server to manage the JMS queue and topic destinations in JMS modules that are targeted to the JMS server. See Configure JMS servers.
Create a JMS system module to contain your JMS resources, such as queue and topic destinations (standalone or distributed), connection factories, quota, destination keys, JMS templates, and JMS store-and-foward (SAF) destinations. See Configure JMS system modules.
Optionally, configure store-and-forward (SAF) agents to communicate between distributed applications on the local and remote server instances. See Configure Store-and Forward services.
Optionally, configure a messaging bridge to forward messages between any two destinations. These destinations are mapped to a pair of configured source and target bridge destinations. See Configure and Manage Messaging Bridges.