Connector for JMS

The Solace PubSub+ Connector for JMS bridges data between a PubSub+ event broker and a Java Message Service (JMS)-compliant broker. The Connector for JMS provides you (as an operator) a flexible and efficient way to integrate JMS-compliant broker data with your Solace-backed, event-driven architecture and the event mesh. The connector is deployable standalone or in redundancy modes of “active-standby” or “active-active” to allow for high-availability and horizontal scaling of your data movement. Each instance of this PubSub+ connector supports up to 20 individual, concurrent workflows (source-to-target pipeline), minimizing the number of connector instances deployed and managed.

Spring Framework technologies make it easy to configure the connector, perform advanced logging capabilities, and export live metric data to external monitoring solutions.

To get started deploying a connector locally or within a container, see:

• Getting Started With the Self-Managed Connectors

• Modifying the Container Configuration

For common configuration details, see:

• Configuring the Datapath for Your Connector

• Managing and Deploying Your Connector

For configuration settings that are specific to JMS, see:

• Configuring Connection Details

• Message Batching

• JMS Shared Durable Subscribers

• JMS Destination Types

• Message Headers

• Asynchronous Publishing