Overview (Solace Java RTO Messaging API v10.8.0)

Packages
Package	Description
com.solacesystems.solclientj.core	Entry point into the Solace Java RTO Messaging API (`Solclient`).
com.solacesystems.solclientj.core.event	Messaging API Event and Callback Interfaces
com.solacesystems.solclientj.core.handle	Handles for wrapping the various concepts managed in the messaging API.
com.solacesystems.solclientj.core.resource	Interface definitions for key messaging objects.

The Java RTO Messaging API (also referred to as solclientj) is specifically designed to provide high message throughput and low latency with the lowest CPU utilization possible. The API is a Java interface, via JNI, to the Solace Messaging API for 'C'. Many of the concepts will be familiar to developers that have worked with the C-API:

Allows the application to connect to a Solace messaging appliance through the concept of a "Session" (see SessionHandle).
Allows messages to be constructed and sent on a Session and to be received from a Session. (see MessageHandle).
Allows subscriptions to be added to specify what messages are to be received. Subscriptions are topic-based. Topic-based subscriptions require the use of a Solace messaging appliance with a Topic Routing Blade (TRB) and they work with assigned Topics. (see SessionHandle.subscribe()).
Support for Guaranteed Message delivery (Queue-based or Topic Endpoint-based). Guaranteed messages are received on "Flows" (see FlowHandle), which are constructed within a Session. Guaranteed Messaging is only available to clients when a Solace messaging appliance is used that has an Assured Delivery Blade (ADB) installed and Guaranteed Messaging and message spooling enabled.
Allows fine-tuning of API behavior, such as whether operations should be blocking or non-blocking in nature.
Support for logging, including support for logging filter levels, and the ability for the application to be called back for generated logs so that they can be placed into the application's logging system.
Support for Topic-based subscriptions.

Application Structure

All applications that use the Java RTO Messaging API will use the same basic structure for connecting to the Solace Messaging appliance:

Initialize the Java RTO Messaging API (see SolClient.init())
Create one or more messaging contexts (see ContextHandle)
Create one or more sessions within a context (see SessionHandle)
Publish messages on the session (see MessageHandle)
Subscribe to topics of interest (see SessionHandle.subscribe())
Create flows to receive Guaranteed Messages (see FlowHandle)