Considerations for JMS Providers

Ensure to review your JMS provider documentation for information about any specific considerations for JMS support.

AMQP Messaging Providers

Integration Server is certified to communicate with JMS providers that support AMQP protocol using QPID JMS client libraries. Integration Server supports the Qpid JMS AMQP 0-x 6.3.3 JMS client libraries.

Solace PubSub+ Appliance and Cloud

Direct Transport mode in Solace PubSub+ does not support the following features:

Message selector

Local transaction support

Durable subscription

Note: Guaranteed Transport mode in Solace PubSub+ supports the above features.

If you use Direct Transport mode in Solace PubSub+ and your JMS provider uses any of these features, Integration Server responds in these ways:

If a JMS trigger is subscribed to a topic and uses the Message selector feature, then Integration Server does not enable the trigger and displays the message, Error creating consumer - cannot use selector with direct messaging.

If the transaction type of a JMS connection alias pointing to Solace PubSub+ is Local transaction or XA transaction, then Integration Server cannot execute the JMS send and receive operations and displays the message, Transacted sessions or XA sessions are not supported with direct transport.

If a JMS trigger is subscribed to a topic with durable subscriber name, then Integration Server does not enable the trigger and displays the message, Unknown Durable Topic Endpoint.