Java Message Service (JMS) Support

Java Message Service (JMS) is a widely used API in Java-based Message Oriented Middleware. It facilitates loosely coupled, reliable, and asynchronous communication between different components of a distributed application. JMS supports two models for messaging as follows: 

• Queues : point-to-point
• Topics : publish and subscribe 

This section provides information on JMS support in WSO2 ESB along with implementation details of common usecases, a configuration guide, troubleshooting guide and more.

• Configuring JMS Transport
  
  • Configure with WSO2 Message Broker
  • Configure with ActiveMQ
  • Configure with IBM MQ
  • Configure with Websphere MQ
  • Configure with MSMQ
  • Configure with Tibco EMS
  • Configure with SwiftMQ
• JMS Usecases
  
  • ESB as a JMS Consumer
  • ESB as a JMS Producer
  • ESB as Both a JMS Producer and Consumer
  • JMS Synchronous Invocations : Dual Channel HTTP-to-JMS
  • JMS Synchronous Invocations : Quad Channel JMS-to-JMS
  • Store and Forward Using JMS Message Stores
  • Publish-Subscribe (Pub-Sub) with JMS
• JMS Samples (When a sample is clicked, you will be navigated to the ESB Samplessection of this documentation)
  • Sample 250: Introduction to Switching Transports
  • Sample 251: Switching from HTTP(S) to JMS
  • Sample 252: Pure Text (Binary) and POX Message Support with JMS
  • Sample 253: Bridging from JMS to HTTP and Replying with a 202 Accepted Response
  • Sample 260: Switch from FIX to AMQP
  • Sample 263: Transport Switching - JMS to http/s Using JBoss Messaging(JBM)
  • Sample 264: Sending Two-Way Messages Using JMS transport
  • Sample 381: Class Mediator to CBR Binary Messages
• Advanced Topics
  
  • Clustering with JMS
  • JMS Security Management
    
    • Security in WSO2 Message Broker/Apache Qpid
    • Security in Apache ActiveMQ
  • JMS Transactions
  • Working with Multiple Types of Brokers
• JMS Troubleshooting Guide
• JMS FAQ