Solace HybridEdge lets you easily integrate legacy ESBs and messaging tools with Solace PubSub+ so you can use Solace message brokers (appliance, software or cloud) to meet the messaging needs of new or migrated applications without modifying other on-premises applications or existing infrastructure.

HybridEdge is a product based on the open source Apache Camel framework that bridges Solace PubSub+ appliances, software and cloud services with leading JMS brokers. Since it’s based on Camel, it also gives you the flexibility to integrate other messaging technologies. You can choose from several flexible support plans when you want to deploy HybridEdge in production.


HybridEdge is a Java application that can be deployed on any server with a Java 8 or later JVM. HybridEdge features a plug-and-play architecture that makes it easy to integrate JMS brokers with Solace PubSub+ by simply providing the APIs for those legacy systems. This architecture also supports the addition of business logic, such as message transformation, and you can use other Camel connectors to bridge to other services such as database connectors and file systems.

Once those connections are in place, each Camel route is a one-way flow of data (either from the legacy environment to PubSub+, or vice versa) that includes the input queue/topic and the output queue/topic. As mentioned above, you can also include a processor component that implements some business logic like a message transformation operation.


HybridEdge is configured through a file that can define one or more Camel routes between the Solace PubSub+ message broker and the legacy environments. The first step in configuring Solace HybridEdge is determining the configuration and connection information for your components. Then you’ll need to define your routes using Spring XML. Finally, you’ll need to choose your components, figure out their URIs/parameters and define your IN/OUT routes from them.

Common Deployment Patterns

Connecting Legacy Systems with Solace Message Brokers in the Cloud

If you’re deploying PubSub+ message brokers in the cloud, or setting up instances of PubSub+ Cloud, to meet the messaging needs of a new cloud-based service, you’ll frequently still need to exchange information with legacy applications running on-premises. In this scenario you can configure Solace HybridEdge to consume messages from the legacy system and publish them to your Solace PubSub+ Cloud message broker, which would then publish messages to all intended recipients via the new queue/topic.

Connecting Legacy Systems with New On-Prem Solace PubSub+ Message Brokers

You may want to deploy Solace PubSub+ appliances or software message brokers within your datacenter, and use them to meet the messaging needs of select applications, while leaving others untouched. In such cases some data entering the system via PubSub+ may be needed by applications using different messaging or data-movement technologies. For example, certain records might need to be stored in a database. In such scenarios you could set up HybridEdge to consume messages from the PubSub+ message broker, then use the Camel JDBC or SQL component to inert the messages into DB2 via SQL query.

Get Started

Downloading HybridEdge

Solace HybridEdge is available for download as a pre-compiled JAR file that should give you everything you need to get up and running quickly by configuring a few files. The JAR includes the Solace, ActiveMQ and RabbitMQ Camel components, the Camel broker itself, a simple Camel processor, and the Spring framework. The download does not require a development environment, and is primarily intended for demos and POCs.

HybridEdge Starter Projects

A robust open-source starter project is available on GitHub. Intended to serve as a starting point for more robust development, and when you’re looking to introduce 3rd-party components, it includes Gradle for build/dependency management. Like the download on, it includes Camel components for Solace, ActiveMQ and RabbitMQ, along with Spring Boot framework and Log4j and jUnit.

Get Started