Solace PubSub+ Appliance and Cloud

Integration Server 10.15 | Integration Server Administrator's Guide | Configuring Integration Server for JMS Messaging | Supported JMS Providers | Considerations and Example Configuration Information for Third-Party JMS Providers | Solace PubSub+ Appliance and Cloud

Integration Server was tested with Solace PubSub+ messaging API for JMS libraries 10.6.

File to copy from Solace library or from Solace installation directory:

sol-common-10.6.0.jar

sol-jcsmp-10.6.0.jar

sol-jms-10.6.0.jar

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.