Solace Jakarta Messaging API Overview

The Solace Messaging API for Jakarta Messaging (formerly JMS) allows Java applications to access an event broker using the standard Jakarta Messaging Application Programming Interface (API). Jakarta Messaging provides a common way for Java applications to create, send, receive, and read an enterprise messaging system's messages. For detailed information on Jakarta Messaging, refer to the Jakarta Messaging specification.

Solace Jakarta Messaging API Programming Paradigm

The Solace Jakarta Messaging API is comprised of the following components:

• Solace Jakarta Messaging API

  The Solace Jakarta Messaging API uses the standard Jakarta Messaging interface to provide messaging service for Java-based applications through Solace products.

• Solace event broker

  An event broker acts as the Jakarta Messaging broker for the client. As such, it provides access control, message routing, selecting, and filtering.

  An event broker can also provide Java Naming and Directory Interface (JNDI) service, which allows Jakarta Messaging clients to perform JNDI lookups and object binding.

  Solace products can support multiple event brokers, each operating in its own Jakarta Messaging domain.

• SolAdmin

  The SolAdmin application is an administration tool that allows administrators to bind event broker objects (such as connection factories, topics, and queues) to Jakarta Messaging objects, which are then stored in the JNDI store. Administrators can use SolAdmin or the Command Line Interface (CLI) to configure and monitor these objects.

You can use the Solace Jakarta Messaging API to provide messaging service in Java Platform Enterprise Edition (Java EE) and Jakarta EE application server environments. Solace provides two variants of the JCA Resource Adapter: a legacy javax.*-based adapter for Java EE servers (see Using the API in JEE Environments) and a modern jakarta.*-based adapter for Jakarta EE servers (see Solace JCA Resource Adapter for Jakarta Messaging Overview).