One more time our development team delivered a fresh version with many updates and refinements. We recommend updating to 2.19.0.2 as soon as possible. If you’re already running a master–shadow setup, you can upgrade without downtime (follow the recommended high-availability upgrade path). The new build is available for download here.
What is new? As with previous updates, there are changes you’ll notice right away and others under the hood. Let’s take a quick tour—the complete list is in the release notes.
A few fixes to keep things smooth
System mappings via REST: You can now create entries with authenticationMode NONE_RESTRICTED using the API— andy when you don’t need principal propagation or a system-certificate logon.Windows SNC helper scripts: The scripts for generating SNC configuration with the SAP Common Crypto Library now handle special characters in parameters and spaces in file names
Enhancements that make daily work easier
Broader platform coverage:New OS and architecture support: Red Hat Enterprise Linux 10, SUSE Linux Enterprise Server 16, and macOS 26 (Tahoe). Linux on aarch64 is now supported. Check the Product Availability MatrixRuntime update: SapMachine 25 can be used as the Java runtime. Check the PrerequisitesSimpler trust management:Optional automatic trust synchronization makes it easier to use the automatic signing key rotation of SAP Authorization and Trust Management. How to configure trusted entities in Cloud Connector. Learn more: Trusted Entities Configuration and KeyrotationGovernance and roles:Managed subaccounts : These can be modified only by users with an administrator role; other users get read-only access for safer operations at scale. New role: AssociateAdministrator —a lighter-weight admin role to delegate tasks while keeping guardrails in place. Connectivity options:WebSocket RFC as an alternative to classic CPIC‑based RFC when talking to ABAP systems —useful in modern network environments. How to configure: can be found here.Operations and observability:Monitoring REST API for alerts: New endpoints to query and integrate alert information with your monitoring stack.More configuration REST APIs: Endpoints for alerting, e-mail, subject pattern rules, and principal propagation validity—making policy and configuration changes scriptable. See configuration APIs. Troubleshooting improvements: Additional categories with likely causes and suggested fixes to speed up analysis when something goes wrong.
Upgrade checklist
Verify OS and architecture support in the Product Availability MatrixConfirm your Java runtime meets prerequisitesPlan a master–shadow upgrade to avoid downtime and follow the recommended procedure.Consider enabling automatic trust synchronization to simplify signing key rotation. Review roles and governance: use AssociateAdministrator where suitable; adopt managed subaccounts.Evaluate switching ABAP RFC traffic to WebSocket RFC if it better fits your landscape.
We’re excited about this release—broader platform choice, simpler trust, stronger governance, and improved visibility all help keep hybrid connectivity reliable and secure. Happy updating!
One more time our development team delivered a fresh version with many updates and refinements. We recommend updating to 2.19.0.2 as soon as possible. If you’re already running a master–shadow setup, you can upgrade without downtime (follow the recommended high-availability upgrade path). The new build is available for download here.What is new? As with previous updates, there are changes you’ll notice right away and others under the hood. Let’s take a quick tour—the complete list is in the release notes.A few fixes to keep things smoothSystem mappings via REST: You can now create entries with authenticationMode NONE_RESTRICTED using the API— andy when you don’t need principal propagation or a system-certificate logon.Windows SNC helper scripts: The scripts for generating SNC configuration with the SAP Common Crypto Library now handle special characters in parameters and spaces in file names Enhancements that make daily work easierBroader platform coverage:New OS and architecture support: Red Hat Enterprise Linux 10, SUSE Linux Enterprise Server 16, and macOS 26 (Tahoe). Linux on aarch64 is now supported. Check the Product Availability MatrixRuntime update: SapMachine 25 can be used as the Java runtime. Check the PrerequisitesSimpler trust management:Optional automatic trust synchronization makes it easier to use the automatic signing key rotation of SAP Authorization and Trust Management. How to configure trusted entities in Cloud Connector. Learn more: Trusted Entities Configuration and KeyrotationGovernance and roles:Managed subaccounts : These can be modified only by users with an administrator role; other users get read-only access for safer operations at scale. New role: AssociateAdministrator —a lighter-weight admin role to delegate tasks while keeping guardrails in place. Connectivity options:WebSocket RFC as an alternative to classic CPIC‑based RFC when talking to ABAP systems —useful in modern network environments. How to configure: can be found here.Operations and observability:Monitoring REST API for alerts: New endpoints to query and integrate alert information with your monitoring stack.More configuration REST APIs: Endpoints for alerting, e-mail, subject pattern rules, and principal propagation validity—making policy and configuration changes scriptable. See configuration APIs. Troubleshooting improvements: Additional categories with likely causes and suggested fixes to speed up analysis when something goes wrong.Upgrade checklistVerify OS and architecture support in the Product Availability MatrixConfirm your Java runtime meets prerequisitesPlan a master–shadow upgrade to avoid downtime and follow the recommended procedure.Consider enabling automatic trust synchronization to simplify signing key rotation. Review roles and governance: use AssociateAdministrator where suitable; adopt managed subaccounts.Evaluate switching ABAP RFC traffic to WebSocket RFC if it better fits your landscape.We’re excited about this release—broader platform choice, simpler trust, stronger governance, and improved visibility all help keep hybrid connectivity reliable and secure. Happy updating! Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
