Name | Description | Introduced in Version |
---|---|---|
SAP IS: Support setting CLIENT_NAME so that has a customer-defined part and also unique |
Support client_name property in a multi-node environment
|
1.3.0 |
SAP IS: Add and propagate Correlation ID in iFlow |
Support propagation of SAP_MplCorrelationId both at Sender and Receiver Adapters
|
1.3.0 |
SAP IS: Connection count improvements to reduce unnecessary connections |
Package Integration - Solace PubSubPlus Sender Adapter - Support for consumer binding on a single worker node
|
1.2.0 |
SAP IS: Adapter retry attempts should grouped in a single log and indicate retry count |
Package Integration - Solace PubSubPlus Sender Adapter - Added two new non-SMF Exchange headers LocalProcessingAttempt and TotalLocalProcessingAttempt to hold counts of local processing attempts and total local processing attempts respectively, per message
|
1.2.0 |
SAP IS: Support Durable Topic Endpoints on Sender Adapter (consumer) |
Package Integration - Solace PubSubPlus Sender Adapter - Consume from a Durable Topic Endpoint
|
1.2.0 |
PubSub+ Adapter for SAP Integration Suite - Initial Feature Set |
Solace PubSubPlus Adapter for SAP Integration Suite
Version 1.0.0: Initial Release This release supports Camel 2.x and 3.14 in SAP Integration Suite tenants. Solace PubSubPlus Sender Adapter Consume Guaranteed (persistent) messages from a Solace PubSubPlus broker queue Consume Direct (non-persistent) messages using a Topic Subscription Number of Parallel Consumers for horizontal scaling of non-exclusive or partitioned queues Choice of Acknowledgement Mode Adapter-level message retry properties to augment broker-side redelivery settings Solace PubSubPlus Receiver Adapter Publish Guaranteed (persistent) messages to a Topic (recommended) or Queue in Solace PubSubPlus broker Publish Direct (non-persistent) messages to a Topic in Solace PubSubPlus broker Destination can be dynamically set at runtime via header or property expression Support for multiple message payload types: Text, Byte, Map message types Turn publish into a request/reply "Requestor" that send a message to the Destination, sets ReplyToAddress and CorrelationID, and synchronously waits for a response Set User Properties on outgoing message Set SMF message properties such as Priority, DMQ Eligible, and CorrelationId on outgoing message Connection with Solace PubSubPlus Broker: Connect to any broker Support for various authentication modes: Basic Client Certificate OAuth2 Support for setting less common connection properties |
1.0.0 |
Reference Number | Description | Resolved in Version |
---|---|---|
DATAGO-72037 |
Package Integration - Fixed the UserProperties header not resolving after initial processing when using camel expression
|
1.1.0 |