Deployment Options

Use

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

Embedded deployment in an SAP Business Suite system

As of SAP NetWeaver 7.4, the core component for SAP NetWeaver Gateway, SAP_GWFND, is installed as standard. In addition to this core component, you can install optional components for SAP NetWeaver Gateway in the same SAP Business Suite system.
Central hub deployment in a standalone system

As of SAP NetWeaver 7.4, the core component for SAP NetWeaver Gateway, SAP_GWFND, is installed as standard. In addition to this core component, you can install optional components for SAP NetWeaver Gateway in the same standalone system, which can be located either behind or in front of the firewall.

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

Embedded or Central Hub Deployment?

You can install SAP NetWeaver Gateway independent of consumer technologies, however the software components installed for the consumer technologies could also be installed on one SAP NetWeaver Gateway system. You can connect multiple consumer technologies to one SAP NetWeaver Gateway instance.

In short, the following scenarios are feasible:

Embedded deployment - development in SAP Business Suite system
Central hub deployment - development in SAP NetWeaver Gateway system
Central hub deployment - development in 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 NetWeaver 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 NetWeaver 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 NetWeaver Gateway content is not available. Content specific to SAP Business Suite is used in SAP Business Suite system.

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

Embedded Deployment in SAP NetWeaver 7.4

Central Hub Deployment

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

Routing and composition of multiple systems is supported.
Dedicated SAP NetWeaver 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 NetWeaver 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 NetWeaver Gateway system will not automatically affect the SAP Business Suite system.
A separate SAP NetWeaver Gateway system can be implemented in a demilitarized zone (DMZ) for external access.
Independent innovation speed of SAP NetWeaver 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

Core Component for SAP NetWeaver Gateway

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

Name	Type	Version	Notes
SAP_GWFND	ABAP	740	Installed as standard in systems based on SAP NetWeaver 7.4 or higher. This core component contains: Runtime components Metdata store Shared services, for example, monitoring OData libraries Business enablement provisioning Business content adapter for SAP NetWeaver Gateway with SAP HANA to enable exposure of SAP HANA views Note If you have previously installed SAP NetWeaver 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 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 NetWeaver 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 higher. You only need to install this component if you have existing Generic Channel services that you want to reuse.

Name

Type

Version

Notes

SAP_GWFND

ABAP

740

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

This core component contains:

Runtime components
Metdata store
Shared services, for example, monitoring
OData libraries
Business enablement provisioning
Business content adapter for SAP NetWeaver Gateway with SAP HANA to enable exposure of SAP HANA views

Note

If you have previously installed SAP NetWeaver 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 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

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

Optional Components for Central Hub Deployment

The following optional components are available for SAP NetWeaver 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 NetWeaver 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 NetWeaver 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 .