Introduction, Overview, and Availability
By using WebSocket as an alternative transport layer for Remote Function Call (RFC), WebSocket RFC, the new web-enabled flavor of RFC, combines the benefits of a standardized transport layer with the well-know...
Introduction
Fast RFC serialization speeds up RFC-communication by factors and is easier to manage than other RFC serializations. It is required for all scenarios with t/q/bgRFC in the cloud and brings great advantages for all RFC communication with ...
SAP .NET Connector 3.0 is now released and you surely want to know more about it. In this weblog I want to
Give you a very short overview on what is new with the SAP .NET Connector 3.0
Show a very simple demo application on how to use the .NET...
SAP NetWeaver Enhancement Package 2 for SAP NetWeaver 7, which is delivered with Enhancement Package 5 of SAP ERP, brings a whole series of new ABAP Language features that make application development easier and more powerful.
In this weblog I wil...
In this weblog we will tell you how to use the Enhancement and Switch Framework most efficiently when you adapt SAP programs as customer or partner and how to save a lot of time and costs in subsequent upgrades. Maybe you already know that the new En...
Hello Andrei,
thank you for your interest in fast serialization and this weblog.
As to the problem you describe you should open a message. This way, our developers can solve your problem and get in touch with you the usual way.
In fact, it is not really a new protocol, but an RFC with fast serialization (also available for RFC via CPIC) only and WebSocket as the transport layer.
The WebSocket layer is standard compliant to the degree that you can use HTTP infrastructure - ...
Hello Alan,it is possible to use the function module IDOC_INBOUND_ASYNCHRONOUS, but it might be easier to process IDOCs if you use the SAP Business Connector. Use this link to find information on the SAP Business Connector: https://service.sap.com/co...
Hello Huseyin,there is one version for .NET framework 2.0 to 3.5 and another version for .NET framework 4.0, because .NET framework 4.0 contains incompatible changes.RegardsThomas
Hello Huseyin,yesterday we have uploaded a new version of JCo 3.0 that works with .NET Framework 4.0.I propose you should use this version.RegardsThomas
