Release Notes: PubSub+ Connector for SAP_IS, Version 1.3.5
New Features Introduced in Release 1.3.5 Issues Resolved in Release 1.3.5 Changed Functionality in Release 1.3.5 Vulnerabilities Addressed in Release 1.3.5 Known Issues in Release 1.3.5
Release History for PubSub+ Connector for SAP_IS, Version 1.3.5
May 2025

New Features Introduced in Release 1.3.5 and Earlier Releases

This section lists the new features introduced in the PubSub+ Connector for SAP_IS for release 1.3.5 and earlier releases.
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

Issues Resolved in Release 1.3.5 and Earlier Releases

This section lists the history of resolved issues in the PubSub+ Connector for SAP_IS for release 1.3.5 and earlier releases.
Reference Number Description Resolved in Version
DATAGO-91712

Resolved an issue with the "Run on a single worker node" feature where queue consumers failed to automatically reconnect following CPI software or Platform updates.

Symptom

Integration flows using the adapter with the "Run on a single worker node" feature enabled experience intermittent failures during backend maintenance or software updates. During these periods of maintenance or updates, message processing may become blocked, and system logs show "Failed to acquire cluster lock for lock id..." errors across all worker nodes.

Prerequisites

Requires Cloud Integration and Cloud Integration Runtime Versions 6.65.x and 8.29.x and higher.

Note

Integration flows configured with "Run on a single worker node": Since these flows run on a single node (which can act as a single point of failure), any lifecycle change to the node, such as software updates, out-of-memory exceptions, etc. may cause a brief delay in message consumption due to the switchover to a new node.

1.3.5
DATAGO-96403

Fixed an issue where undeploying or updating adapters while iFlows were actively running would create orphaned connections that would prevent messages in the queue from being consumed in certain cases.

Upgrade Instructions

In order to upgrade to this version, please follow these steps:

  1. Identify all iFlows using the SolacePubSubPlus Adapter by navigating to Monitor > Integrations and APIs > "Manage Integration Content"
  2. Undeploy all identified iFlows and verify they have been successfully removed from the "Manage Integration Content" section
  3. Update the SolacePubSubPlus Adapter and deploy:
    1. Navigate to the Integration Package containing your existing SolacePubSubPlus Adapter.
    2. Click on the "Actions" tab and select "View metadata" from the dropdown menu.
    3. In the metadata dialog window:
      • Click the "Browse" button
      • Locate and select the new adapter version file
      • Click "Save" to confirm the update
    4. The adapter has now been updated. You can deploy this newer version to through the "Actions" tab.
  4. Verify the Adapter has been successfully deployed by checking its status in "Manage Integration Content"
  5. Redeploy all previously undeployed iFlows and confirm successful deployment in "Manage Integration Content"
 1.3.4
DATAGO-93559
Implemented metadata preservation for historical configuration to enable smoother migration from Apache Camel 2.24.x to 3.14.x.
1.3.3
DATAGO-87230
Upgraded the JCSMP dependency to v10.25.2 to address an issue that prevented message delivery when a consumer flowId grew larger than the max signed 32-bit integer.
 1.3.2
DATAGO-87229
Package Integration - Implemented a workaround to resolve the RuntimeError - CAMEL_CONTEXT_NOT_STARTED issue affecting Edge Integration Cell environments running version 8.21 and above
 1.3.1
DATAGO-81878
Package Integration - A minor improvement when using the Sender processing parameter "Run on a single worker node", to bind the Consumer on a single worker node
 1.3.1
DATAGO-72037
Package Integration - Fixed the UserProperties header not resolving after initial processing when using camel expression
 1.1.0

Changed Functionality in Release 1.3.5 and Earlier Releases

This section lists the history of changed functionality in the PubSub+ Connector for SAP_IS for release 1.3.5 and earlier releases.

None

Vulnerabilities Addressed in Release 1.3.5 and Earlier Releases

The following vulnerabilities have been resolved in the PubSub+ Connector for SAP_IS for release 1.3.5 and earlier releases.

None

Known Issues in Release 1.3.5 and Earlier Releases

This section describes known issues in the PubSub+ Connector for SAP_IS for release 1.3.5 and earlier releases.

None
For more details, refer to the Release Notes page for the individual Solace Messaging APIs.