The messaging API for JMS uses the standard JMS interface to provide JMS service for Java-based applications through a Solace PubSub+ event broker. The Solace JMS API supports JMS version 1.1.
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 Component Concept Map
If you haven't used JMS and Solace PubSub+ together before, you might want to look at the JMS section of the Overview: How Apps Interact with PubSub+ Messaging Components page. 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 from producers to the broker, and from the broker to consumers, with JMS.
These tutorials will introduce you to the fundamentals of using JMS to develop applications using Solace PubSub+. They cover pub/sub, message persistence, request/reply, and more.