Using Solace JMS API in JEE Environments

To use the Solace JMS API in a Java Platform, Enterprise Edition (Java EE) or Jakarta 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 provides resource adapters for both legacy Java EE application servers, such as WebSphere Traditional, WebLogic, and JBoss EAP 7, and modern Jakarta EE application servers, such as WildFly 27+ and JBoss EAP 8+.

The Solace JCA resource adapter is provided as a standalone resource adapter archive (RAR) file that also provides the required Solace Messaging API for JMS libraries.

Solace provides two variants of the JCA Resource Adapter to support both legacy Java EE and modern Jakarta EE application servers. This page describes the Solace JCA Resource Adapter for JMS. For information about the Solace JCA Resource Adapter for Jakarta Messaging, see Solace JCA Resource Adapter for Jakarta Messaging Overview.

Resource Adapter Variants

Solace offers two resource adapter variants to support the full range of Java enterprise application servers:

  • Solace JCA Resource Adapter for JMS (sol-jms-ra-<version>.rar)—For legacy Java EE application servers that use the javax.* namespace, including WebSphere Traditional, WebLogic, and JBoss EAP 7. For information on how to integrate the Solace JMS implementation with particular Application Servers, contact Solace.
  • Solace JCA Resource Adapter for Jakarta Messaging (sol-jms-jakarta-ra-<version>.rar)—For modern Jakarta EE application servers that use the jakarta.* namespace, including WildFly 27+ and JBoss EAP 8+. See Solace JCA Resource Adapter for Jakarta Messaging Overview.

Choose the appropriate resource adapter based on your application server's Java/Jakarta EE support. The Solace JCA Resource Adapter for JMS and the Solace JCA Resource Adapter for Jakarta Messaging provide equivalent functionality but are binary-incompatible due to the namespace differences.

Integrating JMS Without the Resource Adapter

To integrate the Solace JMS API into a JEE environment without using the Solace JCA Resource Adapter, you should only use the following library files from the Solace JMS API to avoid potential conflicts with existing Java library files:

  • commons-logging-1.1.x.jar
  • sol-jms-10.x.x.jar
  • These library files are present in the lib directory of the extracted Solace JMS package. Copy these library files to the relevant directory for your application. Then add them to your CLASSPATH to use Solace as a JMS provider within a JEE container.