The same is true for SAP NetWeaver 7.52 SP02 are equivalent to their counterparts in the SAP Gateway framework in SAP NetWeaver 7.51 SP06 and SAP NetWeaver 7.50 SP12.

 

 

Deployment Scenarios

When using the central hub deployment option, a single SAP Gateway server is used where server software components IW_FND or GW_CORE are deployed, or where the server runs on top of SAP NetWeaver 7.40 or later. The development of OData services takes place in the back end, based on the back-end enablement component IW_BEP (Backend Event Publisher), or on top of software component SAP_GWFND if the back end is based on SAP NetWeaver 7.40 or later, and services are published on the SAP Gateway (ABAP) hub on-premise.

 

When using OData provisioning, the SAP Gateway hub components are basically moved to SAP Cloud Platform, whereas the service implementation still resides on the SAP Business Suite powered by SAP HANA back end.

 

When using the embedded deployment option, the server and the back-end software components are deployed in an SAP Business Suite powered by SAP HANA back-end system.

 

Hub Deployment Type 1: Development in Back End

The pros and cons of this are:

• Pros
  • Administration advantages (component upgrades without shutting down back-end systems, central front end, etc.)
  • Hub features (multi origin composition, routing)
  • Enhanced security

 

• Cons
  • Additional server required

 

 

When developing SAP Gateway in the back end, Gateway server functionality is only used on one dedicated server, the hub system. The services are deployed on the back-end systems and are registered on the server.

 

The Gateway service is therefore deployed in the Gateway back-end systems, where either IW_BEP is deployed or where the back-end system is running on top of 7.40, leveraging core component SAP_GWFND.

 

Hub Deployment Type 2: Development in the Hub

When using hub deployment with development in the hub, the Gateway server functionality is only used on one dedicated server, the hub system. In contrast to the development in the back end, the service deployment takes place on the hub system. This option is used if either no development is required in the back-end system or, in cases of releases prior to 7.40, if you are not allowed to deploy the add-on IW_BEP in the back end. In this case, you are limited to the interfaces that are accessible through the RFC in the back end.

 

 

Embedded Deployment

The pros and cons of this are:

• Pros
  • Quick and easy way to expose SAP Gateway services from a single back end
  • Performance improvements for SAP S/4HANA with SAP NetWeaver 7.50 SP04
• Cons
  • Disadvantages when combining data from several back ends
  • Downtime for SAP Business Suite systems when upgrading UI components

 

 

In the case of embedded deployment, development takes place in the SAP Business Suite back-end system, which is the same as the Gateway system. The services are registered, as well as published, in the SAP Business Suite powered by SAP HANA back-end system.

 

Hub Deployment Type 3: SAP Cloud Platform OData Provisioning

 

• Pros
  
  
  • The SAP Gateway hub runs in the cloud and you can leverage the cloud benefits (SAP handles upgrades, scaling, security, etc.).
    
  • The solution is integrated with other SAP Cloud Platform services.
    
  • Multiple origin composition is supported.
    
• Cons
  
  
  • The solution does not support all features of the SAP Gateway (ABAP) hub. One example of such a non-supported feature is routing.
    
  • Routing is not supported

 

SAP Fiori Front-End Server Scenarios