Connectivity News in AS ABAP 7.51

OlgaDolinskaja · ‎10-19-2016

ABAP Channels

Multiplexer for WebSocket connections

In contrast to HTTP connection, which is short-lived and can be reused for multiple HTTP requests, the WebSocket connection is long-lived and cannot be reused for other WebSockets. That means that each WebSocket-enabled component requires its own WebSocket connection and the number of WebSockets connections grows over time. Besides this any web browser has its own WebSocket connections limitations and the ABAP application server might reach its connection limit as well.

To get over these problems you can now benefit from the multiplexer which virtualizes multiple WebSocket connections via the only one real WebSocket connection which is then used for exchanging messages. Each application (component) still establishes its own WebSocket connection but now this connection is virtual and doesn’t cause any physical load. Multiplexing is enabled by default for the WebSocket application in the AS ABAP via transaction SAPC and shipped on the client side with the PCP JavaScript library.

Enhanced support for large ABAP Channels messages

Now you can send large messages via ABAP Push Channel (APC) and ABAP Messaging Channel (AMC). The max. message length of messages for AMC was increased from 31 kB to approx. 1 MB and can be configured. The max. message length of messages for APC was increased from approx. 64 kB to approx. 100 MB and can be configured as well.

Create ABAP Push Channels applications in Eclipse

Now you can create ABAP Push Channels (APC) and specify APC applications (transaction SAPC) also in the ABAP Development Tools for Eclipse and so manage your APC applications without accessing a SAP GUI.

SAP Web Dispatcher / Internet Communication Manager

Network Edge Authentication

With Network Edge Authentication you get integrated, simple and secure Web access to backend systems of SAP solutions. SAP Web Dispatcher intercepts all incoming requests from the Internet and forwards only authenticated requests to backend systems in the internal network. Single sign-on and single log-off are provided for multiple independent backend systems including Fiori and SAP Enterprise Portal. A prerequisite for using Network Edge Authentication with SAP Web Dispatcher version 7.49 is a SAP Single Sign-On 3.0 SP1 installation.

HTTP/2 Support

HTTP/2 (originally named HTTP/2.0) is a major revision of the HTTP protocol used by the World Wide Web. HTTP/2 reuses the HTTP1.1 (methods, status codes, semantics etc.) but focuses on end-user perceived performance by optimizing network and server resource usage. Major goal is to use one single connection from browsers to a Web site.

The SAP ABAP application server as well as the SAP Web Dispatcher support HTTP/2 in the HTTP server role with release 7.51 and kernel version 7.49. The feature has to be enabled by setting the profile parameter icm/HTTP/support_http2=true. Please note: server push feature of HTTP/2 is not yet supported by the SAP ABAP application server.

RFC

RFC: New Fast Serialization

Now if you need a faster RFC connection, you benefit from new fast RFC serialization for RFC communication. The new fast RFC serialization is many times faster then xRFC/classic RFC or basXML, behaves uniformly for all data types and allowed extensions and is fully compatible with the existing RFC serialization types. You choose the fast RFC serialization in the transaction SM59 while defining RFC Destinations. It is only possible if both communication partners support the new serialization type.

UCON: Managing HTTP(S) Whitelists

The UCON Framework offers you a new scenario within the transaction UCONCOCKPIT for whitelisting HTTP(S) calls based on a long-term logging. You can now maintain different whitelists for different context types. You are offered the comprehensive UI for all tasks and whitelists, where you can choose to maintain e.g. only one whitelist per context type and so that significantly reduce the number of whitelists. The number of context types itself was reduced from 10 to 3 by integrating similar context types into one new comprehensive context type.

oliver_huetkoeper1 · ‎04-10-2017

Hello Olga,

we have tried to call an HTTP/2 webservice using class cl_http_client from our NW 7.51 system. Unfortunately we did not find an option to use the HTTP/2 protocol version. Also in SM59 you can only use HTTP 1.0 and HTTP 1.1 for HTTP connections to other systems.

Is HTTP/2 only supported on the server side and not on the client side?

Thanks and best regards,
Oliver

OlgaDolinskaja · ‎04-18-2017

Hi Oliver,

yes, the HTTP/2 is only supported on the server side.

See above in the blog: "The SAP ABAP application server as well as the SAP Web Dispatcher support HTTP/2 in the HTTP server role with release 7.51..."

Best regards,

Olga.

oliver_huetkoeper1 · ‎04-21-2017

Hi Olga,

thanks for your reply. Must have missed that sentence.

Best regards,

Oliver

vodela · ‎05-26-2017

Hello

I have ABAP 7.5 trial version - installed as mentioned in

https://sap.github.io/cloud-s4ext/week-1/unit-6/

How I can upgrade this to 7.51 trial version to try out new features

Best regards

Ramesh

OlgaDolinskaja · ‎05-29-2017

Hi Ramesh,

the AS ABAP 7.51 trial version is not available yet.

Regards,

Olga.

Former Member · ‎07-07-2017

Hi Olga,

is the support for larger messages only available in 7.51 or also in 7.50?

Thanks,

Johannes

OlgaDolinskaja · ‎07-07-2017

Hi Johannes,

only in 7.51.

Best regards,

Olga.

vodela · ‎11-28-2017

I 'am trying out cds with odata service (annotations) on ABAP 750 ( with IDES)- When I activate the CDS I can see the view in SE11 but not the service in /IWFND/MAINT_SERVICE.

In eclipse I can see small blue icon next to the @AbapCatalog.sqlViewNam but nothing against @OData.publish: true.

How can I fix this.

Ramesh

OlgaDolinskaja · ‎11-28-2017

Hi Ramesh,

your question doesn't relate to connectivity and any other blogs, please put it into the questions and answers section on SAP community with tag "ABAP Development".

Thank you!

Best Regards,

Olga.

vodela · ‎11-29-2017

Olga

Thanks - I have raises this in ABAP development - I had raise it here as I felt this was connectivity issue as some settings could be wrong and hence Odata was not created but the view was.

Ramesh

former_member295872 · ‎07-19-2021

Hello Olga,

I have below questions.

Any plans to support PUSH_PROMISE? If yes, can you give pointers on how it is going to look?
HTTP/2 supports bi directional flow. Are there any plans to integrate HTTP/2 into RFC technology, for example triggering HTTP action like POST using ABAP statements like
```
CALL Function <<FUNCTION MODULE NAME>> destination<<DESTINATION>> <<HTTP VERB>>
```
If client sends 100 requests multiplexed in one HTTP connection? how will ABAP server react?
1. Will each request be allocated one dialog process?

AchimB · ‎07-19-2021

Hello,

re 1. HTTP/2 Push is dead. We have no plans of providing the feature any more.

re 2. HTTP/2 is not really bi-directional, it only supported push, which is not suitable for information transfer, just for pushing static resources into the browser cache.

However, WebSocket is a full duplex channel and supported by the ABAP server as part of the ABAP Push Channel (APC) technology. You could use it to implement something like you describe. We have currently no plans to offer such functionality out of the box.

re 3. The limit for concurrent streams over a single HTTP/2 connection in the ABAP server is 100, so the server will attempt to process the 100 requests in parallel. The same would happen if you opened 100 parallel connections.

Regards, Achim