1 Answers
A:
Here is how you can validate custom code compatibility on different BTP runtimes.
In the ABAP Environment on BTP, you develop using the ""ABAP for Cloud Development"" language, which is based on restricted language scope and relies on released APIs. SAP ensures backward compatibility, so patches to the underlying platform usually have no effect on your custom code.
For custom applications developed on Cloud Foundry (CF), the kernel and other platform components are managed by SAP. Your applications run in isolated containers, so kernel or ICM patches typically don't affect them directly. However, you are responsible for updating any client-side components or open-source libraries that your code depends on.
In the Kyma runtime (based on Kubernetes), SAP manages the core Kyma system namespace, but you have full access to your custom application's namespace. Patches to the underlying infrastructure (kernel, etc.) are handled by SAP.
The Cloud Connector, which links your on-premise system with BTP, requires manual patching. While this is not technically custom code, its function is critical for hybrid setups. After patching the connector, you must validate its compatibility.
Find the Best Data Backup Software
Explore all products with features, pricing, reviews and more
View All SoftwareHelp the community
Be the First to Answer these questions
Disclaimer
Techjockey’s software industry experts offer advice for educational and informational purposes only. A category or product query or issue posted, created, or compiled by Techjockey is not meant to replace your independent judgment.
20,000+ Software Listed
Best
Price Guaranteed
Free Expert
Consultation
2M+
Happy Customers