Show TOC

Deployment OptionsLocate this document in the navigation structure

Use

Depending on your preferred system landscape, different deployment options are available for SAP GatewayFoundation:

  • Central Hub Deployment (service development in the SAP Business Suite backend system)

  • Central Hub Deployment (service development in SAP Gateway Foundation hub system)

  • Embedded Deployment (service development in the SAP Business Suite system)

The following graphic provides a simplified overview of the different deployment options available to you.

Deployment Options (Simplified)

For a quick overview of the SAP Gateway Foundation deployment options, see the following 7 minute video:

Disclaimer: The below video Information published on non-SAP site is not part of the SAP product documentation. Please read the legal disclaimer for video links before viewing this video.

Note

  • Central Hub Deployment: As of SAP NetWeaver 7.4 and higher, the core component for SAP Gateway Foundation, SAP_GWFND, is installed as standard. Depending on your use case, you can install optional components for SAP Gateway Foundation in the same standalone system, which can be located either behind or in front of the firewall.

  • Embedded Deployment: As of SAP NetWeaver 7.4 and higher, the core component for SAP Gateway Foundation, SAP_GWFND, is installed as standard. Depending on your use case, you can install optional components for SAP Gateway Foundation in the same SAP Business Suite system.

Central Hub Deployment

Central hub deployment of SAP Gateway Foundation has the following advantages:

  • Routing and composition of multiple systems is supported.

  • Dedicated SAP Gateway Foundation content is available.

  • Content can be deployed without touching the SAP Business Suite system.

  • Decoupled lifecycle of consumer applications from the SAP Business Suite system.

  • Central management of routing and connectivity with SAP Business Suite systems.

  • SAP Gateway Foundation capabilities need to be deployed only once within the landscape.

  • Better security, as a request is validated at the dedicated box and consequently attacks on the SAP Gateway Foundation system will not automatically affect the SAP Business Suite system.

  • A separate SAP Gateway Foundation system can be implemented in a demilitarized zone (DMZ) for external access.

  • Independent innovation speed of SAP Gateway Foundation and the connected SAP Business Suite systems.

  • Development of context specific to SAP Business Suite system within the SAP Business Suite system enables you to reuse data stored in the SAP Business Suite system easily since development takes place in the system in which your data is stored. This development is bound to the lifecycle of the SAP Business Suite system.

Embedded Deployment

Deployment embedded in the SAP Business Suite system has the following advantages:

  • Direct local access to metadata and business data, meaning easy reuse of data.

  • Less runtime overhead as one remote call is reduced.

  • No content merge for different applications required.

  • No additional, separate SAP Gateway Foundation system required.

  • Lower total cost of ownership as there is one less system to maintain.

However, note the following considerations:

  • The innovation speed of SAP Gateway Foundation and the SAP Business Suite system need to be synchronized.

  • Devices need to be integrated with the SAP Business Suite system on a point-to-point basis.

  • Cross-system composition is not advisable.

  • Central SAP Gateway Foundation content is not available. Content specific to SAP Business Suite is used in SAP Business Suite system.

Core Component for SAP Gateway

As of SAP NetWeaver 7.4 and higher, the core component for SAP Gateway Foundation SAP_GWNFD is installed as standard.

Name

Type

Version

Notes

SAP_GWFND

ABAP

740

750

751

Installed as standard in systems based on SAP NetWeaver 7.4 and higher.

This core component contains:

  • GW_CORE (OData libraries)

    IW_FND (runtime component, metadata store, shared services)

  • IW_BEP (business enablement provisioning)
  • IW_HDB (business content adapter for SAP Gateway with SAP HANA to enable exposure of SAP HANA views)

  • IW_PGW (content provider that enables exposure of SAP Business Process Management (BPM) and Process Observer Task exposure for BPM and SAP Business Workflow )

Note

If you have previously installed SAP Gateway on a SAP NetWeaver release lower than SAP NetWeaver 7.4 and/or previously created services for the Generic Channel that are still in use, you must install the component IW_FNDGC 100 in systems based on SAP NetWeaver 7.4and higher. You only need to install this component if you have existing Generic Channel services that you want to reuse.

IW_FNDGC

ABAP

100
Note

If you have previously installed SAP Gateway on a SAP NetWeaver release lower than SAP NetWeaver 7.4 and/or previously created services for the Generic Channel that are still in use, you must install the component IW_FNDGC 100 in systems based on SAP NetWeaver 7.4 and higher. You only need to install this component if you have existing Generic Channel services that you want to reuse.
More Information

For more information about landscape recommendations, see the following presentation on SAP Community Network: https://wiki.sdn.sap.com/wiki/display/SLGB/Landscape+Recommendations Information published on SAP site.

http://scn.sap.com/community/gateway/blog/2013/05/27/sap-netweaver-gateway-deployment-options-in-a-nutshell

SAP Note: 1942072 Information published on SAP site