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 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.
Following is a sample JMS inbound endpoint configuration:
coordination are common to all polling inbound endpoints. For descriptions of these parameters, see Common polling inbound endpoint parameters.
JMS inbound endpoint parameters
The JNDI initial context factory class. The class must implement the
A valid class name
The URL of the JNDI provider.
A valid URL
The JNDI name of the connection factory.
The type of the connection factory.
The JNDI name of the destination.
The defaults value is the service name.
Whether the JMS session should be transacted or not.
The JMS session acknowledgment mode.
The JMS resource cache level.
The JMS connection username.
The JMS connection password.
The JMS API version.
|transport.jms.SubscriptionDurable||Whether the connection factory is subscription durable or not.||No|
|transport.jms.DurableSubscriberClientID||The ||Required if the value specified as ||-||-|
The name of the durable subscriber.
Required if the value specified as
Message selector implementation.
|The time to wait for a JMS message during polling. |
Set this parameter value to a negative integer to wait indefinitely. Set it to zero to prevent waiting.
|No||The number of milliseconds to wait.|
|transport.jms.ContentType||How the inbound listener should determine the content type of received messages. Priority is always given to the JMS message type.||No||A simple string value, in which case the transport listener assumes that the received messages always have the specified content type, or a set of rules. For more information, see http://axis.apache.org/axis2/java/transports/jms.html#Service_configuration.||-|
|transport.jms.ContentTypeProperty||Get the content type from message property||No||-|
|transport.jms.ReplyDestination||The destination that the response generated by the back-end service is stored.||No||-||ReplyTo from the message|
Whether messages should be published via the same connection that they were received.
To subscribe to topics, set the value of
For a sample that demonstrates how one way message bridging from to HTTP can be done using the JMS inbound endpoint, seeSample 901: Inbound Endpoint JMS Protocol Sample.