Show TOC

Deployment OptionsLocate this document in the navigation structure

Use

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

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

  • Central Hub Deployment (service development in SAP Gateway 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 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 or SAP NetWeaver 7.5 and higher, the core component for SAP Gateway, SAP_GWFND, is installed as standard. Depending on your use case, you can install optional components for SAP Gateway 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 or SAP NetWeaver 7.5 and higher, the core component for SAP Gateway, SAP_GWFND, is installed as standard. Depending on your use case, you can install optional components for SAP Gateway in the same SAP Business Suite system.

For information about the optional components available for SAP Gateway, see Installing SAP Gateway Components.

Central Hub Deployment

Central hub deployment of SAP Gateway has the following advantages:

  • Routing and composition of multiple systems is supported.

  • Dedicated SAP Gateway 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 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 system will not automatically affect the SAP Business Suite system.

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

  • Independent innovation speed of SAP Gateway 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.

However, note that there will be a redundant deployment of metadata or ABAP Dictionary structures. If you want to use the Screen Scraping generator, you must install the component IW_SCS in the SAP Business Suite system.

The following diagram shows an example of central hub deployment in a standalone system based on SAP NetWeaver 7.4.

Central Hub Deployment in SAP NetWeaver 7.4

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 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 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 content is not available. Content specific to SAP Business Suite is used in SAP Business Suite system.

The following diagram show an example of embedded deployment in an SAP Business Suite system based on SAP NetWeaver 7.4.

Embedded Deployment in SAP NetWeaver 7.4

Core Component for SAP Gateway

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

Name

Type

Version

Notes

SAP_GWFND

ABAP

740

750

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

This core component contains:

  • Runtime components

  • Metadata store

  • Shared services, for example, monitoring

  • OData libraries

  • Business enablement provisioning

  • Business content adapter for SAP Gateway with SAP HANA to enable exposure of SAP HANA views

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 or SAP NetWeaver 7.5 and 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 or SAP NetWeaver 7.5 and higher. You only need to install this component if you have existing Generic Channel services that you want to reuse.
Note

For more information about release dependencies, see Installing SAP Gateway Components.

Optional Components for Central Hub Deployment

The following optional components are available for SAP Gateway:

Name

Type

Version

Notes

IW_CNT

ABAP

200

Contains well-defined content, including, for example:

  • Metadata describing data object

  • ABAP code for data mapping

  • Web service consumer and server proxies

IW_CBS

ABAP

200

Contains application basis functionality, such as SAP Gateway enablement of SAP NetWeaver Business Workflow.

IW_CBS applications are similar to IW_CNT applications.

IW_SPI

ABAP

100

Provides a generic OData adapter for content based on the Service Provider Infrastructure (SPI).

IW_PGW

ABAP

100

Content provider that enables exposure for SAP Business Process Management (BPM) and Process Observer Task exposure for BPM and SAP NetWeaver Business Workflow.

Optional Components for SAP Business Suite System

You can install the following optional components for SAP Gateway in an SAP Business Suite system:

Name

Type

Version

Notes

IW_SCS

ABAP

200

Component for Screen Scraping generator.

IW_GIL

ABAP

100

Provides a generic OData adapter for content based on the Generic Interaction Layer (GenIL).

IW_SPI

ABAP

100

Provides a generic OData adapter for content based on the Service Provider Infrastructure (SPI).

IW_PGW

ABAP

100

Content provider that enables exposure for SAP Business Process Management (BPM) and Process Observer Task exposure for BPM and SAP NetWeaver Business Workflow.
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