PowerConnect for SAP Solutions

PowerConnect Cloud 9.2.0 Release Notes

Overview

PowerConnect Cloud 9.2.0 release. Install the tarball by following the upgrade instructions

New

SAP Datasphere integration (new plugin suite)

  • Datasphere foundation: runtime JDBC support + base plugin, with customer-supplied driver loading

  • Datasphere task input

  • Per-space memory, OOM-events, and admission-controls inputs

JDBC driver management (used for Datasphere)

  • Upload JDBC drivers via the UI

  • Runtime reload of drivers with cluster replication + admin API

  • Driver loader inspects class/version and exposes it via the API, shown as columns in the driver table

API access & machine auth

  • OAuth2 client_credentials bearer auth for machine API clients

  • API Access admin UI for managing API clients

Job & task visibility

  • Track in-progress jobs, exposed via /api/jobs/in-progress and shown on the tasks page

  • Failure reason column added to the failed-tasks table

Audit logging for configuration changes

  • Supports both log output and sending to SIEM

JSON field mapping support

Per-mapping "omit if empty" flag for fallback mappings

Changes

  • Input descriptions now shown as info tooltips in the picker and edit modal

  • Metrics reporter logs split into a separate metrics.log (breaking change)

    • Metrics are now logged to a dedicated metrics.log file instead of being interspersed in the powerconnect.log file. If you are relying on metrics for monitoring the health of PC Cloud then update your monitoring tool to point to the new metrics.log file instead.

  • Conditional CSRF applied to service routes

  • Outputs now use same security model as Inputs (keystore migration)

  • Outputs and Inputs now use new Connection Manager (possible breaking change, see KB 242)

  • Dynatrace log monitoring - partial response logs success, not failure

Bug Fixes

  • Clustering: under heavy load duplicate events could be created, this is now fixed

  • Task view now reports errors correctly

  • CPI log parsing: fixed regexes to prevent catastrophic backtracking and to preserve the SAP #N thread name in traces

  • Expired certs no longer offered as outbound client certs

  • Properly mask ingest tokens in logs when updating an output

Known issues 

None