The WSO2 ESB JMS inbound protocol is a multi-tenant capable alternative to the WSO2 ESB JMS transport. The JMS inbound protocol implementation requires an active JMS server instance to be able to receive messages, and you need to place the client JARs for your JMS server in the ESB classpath.
The recommended JMS server is servers are WSO2 Message Broker or Apache ActiveMQ, but other implementations such as Apache Qpid and Tibco are also supported.
- To configure the JMS inbound protocol with WSO2 Message Broker , see Configuring the JMS Inbound Protocol with WSO2 Message Broker.
- To configure the JMS inbound protocol with ActiveMQ, see Configuring the JMS Inbound Protocol with ActiveMQ.
Configuration parameters for a JMS inbound endpoint are XML fragments that represent JMS connection factories.
...
| Info | ||
|---|---|---|
| ||
To subscribe to topics, set the value of |
...
Samples
For a sample that demonstrates how one way message bridging from JMS to HTTP can be done using the JMS inbound endpoint, see Sample 901: Inbound Endpoint JMS Protocol Sample.