Solace JMS API

The Solace Messaging API for JMS uses the standard Java Message Service (JMS) interface to provide JMS service for Java-based applications through a Solace event broker. For information about version support in the Solace JMS API see Supported Environments.

The Solace JMS API supports the following Message Exchange Patterns:

  • Publish/Subscribe
  • Point to Point
  • Request/Reply

For information about managing Solace JNDI objects in the Solace JMS API, see Solace JNDI Objects.

JMS Developer Guide

Understand the Solace JMS API
JMS API Reference

View the Solace JMS API reference
Jakarta API Reference

View the Jakarta Messaging API reference
Solace JMS API Tutorials

Learn how to use the Solace JMS API
API Feature Support

View the features supported by each Solace Messaging API
Release Notes

Download the Solace JMS API Release Notes

Get Started

If you haven't used JMS and Solace event brokers together before, we recommend that you first look at the JMS section in Messaging Components and Application Interactions to learn how the Solace event broker's messaging components make data move with JMS from message producers to the event broker, and from the event broker to consumers. You may want to check out our JMS Tutorials.

Before you can start working with the Solace JMS API, you must have access to a Solace event broker to test and use your JMS application.

You can get started using a Solace event broker in any of these ways:

  • If you have an appliance event broker or software event broker already deployed, obtain
    • the hostname or IP address of an event broker to test against
    • a username and password to access it
    • 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. 
  • If you have Solace Cloud, you create a new event broker service. For more information, see Creating Event Broker Services.

Resource Adapters

To use the Solace JMS implementation in a Java Platform, Enterprise Edition (Java EE) or Jakarta EE application server environment, you can deploy a Solace‑provided, Java Connector Arations with connectivity to event brokers.

Solace provides two variants of the JCA Resource Adapter: