SAP Datasphere Connector 1.0.0.3

The SAP Datasphere Connector lets you run task chains and replication flows and monitor their execution through completion.

This release includes no new features. For information on using this version of the SAP Datasphere Connector, see SAP Datasphere Connector 1.0.0.0.

Changes in Version 1.0.0.3

• The Connector now requires RunMyJobs 9.2.11 or later.

• SAP sometimes returns a text/html response if the access token used by a request is expired or about to expire, rather than returning a 401. Consequently, when the SAP Datasphere Connector receives such a text/html response, it now logs a warning, automatically fetches a new access token, and retries the request. If the retry fails, the Job goes into Error status.

• Fixed an issue where, if a Workflow had multiple Datasphere Jobs running in parallel, and the access token expired, only one of the parallel Jobs managed to refresh the access token and save it on the connection, completing successfully, while the other Job(s) remained stuck forever trying to update the connection. This version introduces a new caching mechanism that eliminates the need to cache access tokens temporarily on the connection.