JMS API
The PubSub+ Messaging API for JMS uses the standard JMS interface to provide JMS service for Java-based applications through a PubSub+ event broker. For information about version support in the PubSub+ JMS API see Supported Environments.
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 PubSub+ JMS API in JEE Environments.
JMS Concepts
If you haven't used JMS and 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.
Message Exchange Patterns
The PubSub+ Messaging API for JMS supports all common message exchange patterns.
- Publish/Subscribe
- Point to Point
- Request/Reply
Features
For the list of features that are supported for the PubSub+ Messaging API for JMS, see the JMS column in the table in Feature Support in PubSub+ Messaging APIs.
Get Started
These tutorials introduce you to how to develop applications using the PubSub+ Messaging API for JMS for common messaging requirements, and they will get you up-to-speed and sending messages with Solace PubSub+ as quickly as possible. They cover pub/sub, message persistence, request/reply, and more.
There are three ways you can get started using a PubSub+ event broker:
- If you have PubSub+ event brokers already deployed, obtain the hostname or IP address of an event broker to test against, a username and password to access it, and a Message VPN in which you can produce and consume messages.
- You can set up a software event broker as a container image. For more information, see Setting Up Container Images.
- You can spin up an event broker service, which is a SaaS-based software event broker running in PubSub+ Cloud.
Solace JNDI Objects
For information about managing Solace JNDI objects in the PubSub+ JMS API, see Solace JNDI Objects.
JMS Developer's Guide
We have a developer's guide to describe how to start using the PubSub+ Messaging API for JMS.
JMS API Reference
Click below to access the reference for the Solace PubSub+ Messaging API for JMS.
Click below to access the reference for the Solace PubSub+ Messaging API for Jakarta Messaging.
Jakarta Messaging API Reference
JMS API Release Notes
Click below to download the latest release notes for the Solace PubSub+ Messaging API for JMS.