JMS

The Solace PubSub+ Messaging API for JMS, version 10.14 uses the standard JMS interface to provide JMS service for Java-based applications through a Solace PubSub+ event broker. The PubSub+ Messaging API for JMS supports JMS version 1.1.

Resource Adapters

To use the Solace JMS implementation in a Java Platform, Enterprise Edition (Java EE) application server environment, you can deploy a Solace‑provided, Java Connector Architecture (JCA) 1.5-compliant resource adapter for the particular Application Server platform being used to provide enterprise applications with connectivity to event brokers. Solace currently provides a Resource Adapter for Red Hat JBoss EAP 6.2, and WebSphere Application Server V7 and V8. For more information, refer to Using Solace JMS in JEE Environments.

JMS Concepts

If you haven't used JMS and Solace PubSub+ event brokers together before, we recommend that you look at the JMS section in Overview: How Apps Interact with PubSub+ Messaging Components. It'll take you on a tour of the PubSub+ event broker's messaging components, and explain at a high level how they make data move with JMS from producers to the broker, and from the broker to consumers.

Get Started with JMS Messaging Tutorials

These tutorials introduce you to the fundamentals of using JMS to develop applications using Solace PubSub+. They cover pub/sub, message persistence, request/reply, and more.