Solace PubSub+ Agent for Gluesync: Target Integration

Index

Core principles

Gluesync streams entity changes into Solace PubSub+ so you can keep the application side focused on the business model while Solace handles delivery.

In v2.2, the target agent publishes each entity change to a topic derived from the entity collection and the CRUD action. Delete events also emit a tombstone message so downstream consumers can react to removals explicitly.

Gluesync’s Solace PubSub+ agent uses the SMF protocol through Solace’s official Java SDK.

Change data capture

This agent does not currently support reading incremental changes from Solace PubSub+.

Platform supported features

Feature	Support	Notes
Target role	✅	Publishes messages to Solace PubSub+ topics using the official Java SDK over SMF.
Source role	❌	Solace is target-only; Gluesync does not subscribe to PubSub+ messages.
Snapshots	❌	Not supported, as this agent does not supporting reading from Pub/Sub.
CDC	❌	Not supported, as this agent does not supporting reading from Pub/Sub.
CDC type	N/A	Not supported, as this agent does not supporting reading from Pub/Sub.
Bulk load	N/A	Publishing already batches efficiently; no staging-table workflow.
Database pooling	N/A	The agent keeps a single MessagingService per agent and caches publishers per entity and delivery mode; there is no pool configuration to tune.
Source persisted internal cache	N/A	Target-only connector.
Target persisted internal cache	N/A	Messages are sent directly to PubSub+ with no local buffering, while publishers are cached per entity and delivery mode.
Driver / connector	Solace Java SDK (SMF)	Uses basic authentication with optional TLS trust-store configuration in v2.2.
Chains	N/A	Target-only connector.
Truncate operation support (reading)	N/A	Target-only connector.
Truncate operation support (writing)	N/A	Truncate is not propagated to Solace; delete events are emitted as messages and tombstones instead.

Feature

Support

Notes

Target role

✅

Publishes messages to Solace PubSub+ topics using the official Java SDK over SMF.

Source role

❌

Solace is target-only; Gluesync does not subscribe to PubSub+ messages.

Snapshots

❌

Not supported, as this agent does not supporting reading from Pub/Sub.

CDC

❌

Not supported, as this agent does not supporting reading from Pub/Sub.

CDC type

N/A

Not supported, as this agent does not supporting reading from Pub/Sub.

Bulk load

N/A

Publishing already batches efficiently; no staging-table workflow.

Database pooling

N/A

The agent keeps a single MessagingService per agent and caches publishers per entity and delivery mode; there is no pool configuration to tune.

Source persisted internal cache

N/A

Target-only connector.

Target persisted internal cache

N/A

Messages are sent directly to PubSub+ with no local buffering, while publishers are cached per entity and delivery mode.

Driver / connector

Solace Java SDK (SMF)

Uses basic authentication with optional TLS trust-store configuration in v2.2.

Chains

N/A

Target-only connector.

Truncate operation support (reading)

N/A

Target-only connector.

Truncate operation support (writing)

N/A

Truncate is not propagated to Solace; delete events are emitted as messages and tombstones instead.

Security

Gluesync uses the Solace Java SDK over SMF. In v2.2, the target agent is documented around basic authentication and optional TLS trust-store configuration. We recommend TLS for any production use case.

Support for other Solace authentication schemes is not documented for this target version.

Supported versions

Gluesync works both on PubSub+ on-prem and on PubSub+ Cloud.

Q&A

I am using a different authentication mechanism, is it supported? This target version is documented around basic authentication and optional TLS trust-store configuration. If you need a different Solace auth flow, contact MOLO17.