Support for multiple authentication schemes in a single connector In earlier releases, while creating a connector, only one connection type or authentication scheme can be associated with a connector. As some SaaS application providers offer multiple authentication options to access their back end APIs, for example, Salesforce CRM v44, the connector developer needed to create a connector for each authentication scheme, for example, one connector for Basic authentication and another connector for OAuth 2.0 authentication. From this release, a connector developer can build a single connector that supports multiple authentication schemes. You can then select different connection types for the same connector and for the same back end from the connection configuration page in Integration Server Administrator.

Support for generating OAuth 2.0 Tokens while creating connections In earlier releases, CloudStreams did not have the provision to generate Access Tokens required to configure the connection for OAuth 2.0 authorization. From this release, for some connectors, for example, Salesforce CRM v44, you can generate OAuth 2.0 Access Tokens while creating a new connection from the connection configuration page in webMethods Integration Server Administrator. You can generate OAuth 2.0 tokens using the Authorization Code Flow or the JSON Web Token (JWT) Flow approaches.

Clustering support for connector listeners In earlier releases, CloudStreams connector listeners were not cluster aware. From this release, CloudStreams supports the use of clustering by either distributing the processing load for Streaming API events across Integration Server instances (Multi-Node mode) or limiting the processing to a single Integration Server node (Single-Node mode), while guaranteeing exactly once processing in each mode. CloudStreams leverages the distributed cache, which stores data in a Terracotta Server Array to coordinate processing of events between different Integration Server instances. The choice of a cluster support mode for a connector listener is predefined by the connector developer for a back end.

Support for Salesforce replay events In earlier releases, CloudStreams did not have a mechanism to retrieve and replay lost events in case a SaaS provider sends those events. For example, Salesforce stores standard-volume events for 24 hours. So for versions later than 37.0 in Salesforce, you can now retrieve events if they are within the retention window. You can replay the lost events by selecting the appropriate replay option (ALL or NEW) on the Providers Listener configuration page in Integration Server Administrator.

Update/Upgrade Services Enhancements The pub.cloudstreams.admin.service:update and pub.cloudstreams.admin.service:batchUpdate services have been enriched to update the Connector Services from a lower version of the connector API to a higher version having new features like inline connection and multi-part. Further, the new service pub.cloudstreams.upgrade:batchUpgrade service updates batches of CloudStreams connector service nodes and connector listener nodes from a lower version of the connector API to a higher version.

Migrate Services Enhancements The pub.cloudstreams.migration:migrate service migrates old CloudStreams Connector services, connections, and connector listeners in custom packages that depend on the WmCloudStreams package, and updates them to be compatible with CloudStreams. The updated migrate service can migrate the Connector Service nodes which has new features like inline connection and multi-part.