3/29/2018 SAP e-book

Unit 7: SAP Gateway Hub Functionalities

System Alias Settings

Figure 169: System Alias Settings

Since version 7.40, Gateway has become an integral part of SAP NetWeaver. With the release
of SAP NetWeaver 7.50 SP04, we have taken the opportunity to use the latest capabilities of
the stack to provide some fundamental performance optimizations to Gateway, such as using
Simple Transformations for the rendering of the OData service response or the shared use of
memory between different Gateway components. The majority of changes made within the
Gateway framework are implicitly used. This increases the speed of your application without
the need for any additional configuration, independent from the SAP Gateway deployment
scenario you are using. If you are using Gateway in Embedded Deployment scenario in SAP
NetWeaver on a central instance the performance optimizations are already active by default
since the SAP Gateway backend framework and SAP hub framework components reside on
one box.
After completing certain configurations on your hub system is acting in a special operating
mode and will route most service requests to Gateway on the appropriate backend server and
execute them there locally. This is possible because the functionality of both the Gateway hub
and the Gateway backend can now run “co-deployed” in the backend since both frameworks
reside in the same software component SAP_GWFND. In this operating mode the backend
system for instance is capable to serialize the data response with a simple transformation,
which will be performed much faster in the SAP NetWeaver kernel instead of ABAP. Those
Simple Transformations are automatically created by SAP Gateway for most READ
operations.
A detailed description can be found in the following blog:
https://blogs.sap.com/2016/10/10/take-advantage-performance-improvements-sap-
gateway-sap-netweaver-7.50-sp04/

Note:
The term “Micro Hub” does not indicate a new or different Gateway hub. It is
merely the normal hub, only now it is configured to forward valid OData service
requests immediately to the backend for further processing. We have thus
renamed the caption of the column to “OData on Backend” in SAP NetWeaver
7.51.

308 © Copyright. All rights reserved.

1/1