Fiori-like Prototype ( 2022 SAP Netweaver / Platform Connector Solutions )
SAP Connector Playground like :
SAP Java Connector,
SAP Connector for Microsoft .NET 3.0,
SAP Cloud Connector.
SAP Java Connector
The SAP Java Connector (SAP JCo) is a development library that enables a Java application to communicate with on-premise SAP systems via SAP's RFC protocol. The SAP JCo supports both communication directions: inbound Remote Function Calls (Java calls ABAP) as well as outbound Remote Function Calls (ABAP calls Java).
SAP Java Connector（SAP JCo）是一个开发工具库，它使Java应用程序能够通过SAP的RFC协议与内部的SAP系统进行通信。SAP JCo支持两种通信方向：入站远程功能调用（Java调用ABAP）以及出站远程功能调用（ABAP调用Java）。
Benefits of the SAP Java Connector for building SAP-enabled Java applications:
SAP Java 连接器在构建支持 SAP 的 Java 应用程序方面的优势：
High performance JNI-based RFC middleware.
Supports R/3 3.1I and higher releases (and other SAP components that have BAPIs or RFMs).
Supports inbound (Java client calls BAPI or RFM) and outbound (ABAP calls Java server) RFC communication.
Supports synchronous, transactional, queued and background RFC (sRfc, tRfc, qRfc, bgRfc protocols).
Provides client connection pooling.
Multi-platform support.Complete and correct code page handling (including Unicode and non-Unicode single- and multi-byte code pages).
基于 JNI ( Java Native Interface ) 的高性能 RFC 中间件。
支持 R/3 3.1 或 更高版本（以及其他具有 BAPI 或 RFM 的 SAP 组件）。
支持入站（Java 客户端调用 BAPI 或 RFM）和出站（ABAP 调用 Java 服务器）RFC 通信。
支持同步、事务、排队和后台 RFC（sRfc、tRfc、qRfc、bgRfc 协议）。
提供客户端连接池。
提供多平台支持。
提供完善的代码页处理（包括 Unicode 和非 Unicode 单字节和多字节代码页）
SAP Java Connector Resources
ZFiori Studio Demo 001
ZFiori Studio Demo 001 Fresh Look
SAP Connector for Microsoft .NET 3.0
SAP Connector for Microsoft .NET 3.0 (NCo 3.0) allows developers to use BAPIs and remote-enabled function modules in any .NET application (inside-out). You can also access .NET components from any ABAP application by implementing an RFC server in .NET (outside-in). See SAP Note 856863 for details about availability and platform requirements.
SAP Connector for Microsoft .NET 3.0 (NCo 3.0) 允许开发人员在任何 .NET 应用程序（由内而外）中使用 BAPI 和远程功能模块。您还可以通过在 .NET 中（由外向内）实现 RFC 服务器从任何 ABAP 应用程序访问 .NET 组件。有关可用性和平台要求的详细信息，请参阅 SAP Note 856863。
The main differences to NCo 2.0 are:
与 NCo 2.0 的主要区别是：
NCo 3.0 no longer distinguishes between a design time and a runtime. Instead of proxy classes and generated coding, you now program RFC calls dynamically. This has advantages (less and more easily understandable coding; robustness against changes on backend side — e.g. it is no longer necessary to re-generate the proxies and re-compile your application if the backend moves from non-Unicode to Unicode; no dependency on a fixed Visual Studio release) as well as disadvantages (no IntelliSense support; you need to know how the ABAP side looks when consuming RFMs in .NET).
NCo 3.0 不再区分设计时和运行时。您现在可以动态编程 RFC 调用，而不是代理类和生成的编码。这具有优势（更少且更容易理解的编码；对后端更改的稳健性——例如，如果后端从非 Unicode 移动到 Unicode，则不再需要重新生成代理并重新编译您的应用程序；不依赖于一个固定的 Visual Studio 版本）以及缺点（不支持 IntelliSense；您需要知道在 .NET 中使用 RFM 时 ABAP 端的外观）。
RFC protocol is re-implemented in C#, so there is no longer a dependency on librfc32.dll. This should result in better performance, as almost no marshalling between managed and unmanaged code is necessary now.
RFC 协议在 C# 中重新实现，因此不再依赖于 librfc32.dll。这应该会带来更好的性能，因为现在几乎不需要在托管和非托管代码之间进行编组。
SAP .NET Connector Resources
ZFiori Studio Demo 002 - Part 1
ZFiori Studio Demo 002 - Part 2
ZFiori Studio Demo 002 - Part 3
SAP Cloud Connector
The Cloud Connector is an optional on-premise component that is needed to integrate on-demand applications with customer backend services and is the counterpart of SAP Connectivity service.
Cloud Connector 是一个可选的内部部署组件，需要将按需应用程序与客户后端服务集成，并且是 SAP Connectivity 服务之一。
SAP Cloud Connector Resources
SAP Cloud Connector Backend
SAP BTP Cloud Connectors
SAP BTP Destination
