Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

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:

To configure WebLogic Server messaging:

  1. 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 custom persistent stores.
  2. 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.
  3. Create a JMS system module to contain your JMS resources, such as queue and topic destinations (stand-alone or distributed), connection factories, quota, destination keys, JMS templates, and JMS store-and-foward (SAF) destinations. See Configure JMS system modules.
  4. Optionally, configure store-and-forward (SAF) agents to communicate between distributed applications on the local and remote server instances. See Configure Store-and-Forward.
  5. 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.

Related Tasks

Related Topics

Back to Top