Deployment Options 
This section describes the two deployment options available for SAP NetWeaver Gateway:
Embedded deployment of SAP NetWeaver Gateway core components IW_FND and GW_CORE in an SAP Business Suite backend system.
As of SAP NetWeaver 7.40, the core software component for SAP NetWeaver Gateway is SAP_GWFND, which contains the composite functional scope of IW_FND, GW_CORE, IW_BEP, and IW_HDB.
Central hub deployment of SAP NetWeaver Gateway core components IW_FND and GW_CORE in an SAP NetWeaver Gateway hub system.
As of SAP NetWeaver 7.40, the core software component for SAP NetWeaver Gateway is SAP_GWFND, which contains the composite functional scope of IW_FND, GW_CORE, IW_BEP, and IW_HDB.
For more information about the SAP NetWeaver Gateway components, 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 must also be installed on one SAP NetWeaver Gateway server. You can connect multiple consumer technologies to one SAP NetWeaver Gateway instance.
Deployment options:
Embedded deployment: The core components for SAP NetWeaver Gateway and any optional backend components are deployed together in the SAP Business Suite backend system. For this deployment option, you need a backend system only, and not a dedicated SAP NetWeaver Gateway central hub system.
Central hub deployment: The SAP NetWeaver Gateway core components can be deployed in a standalone system, either behind or in front of the firewall. In addition, you can install the optional components for central hub deployment in your standalone system. For SAP NetWeaver 7.02, 7.03, and 7.31 you can install the component IW_BEP either in this hub system and/or in the backend system. For SAP NetWeaver 7.40 and higher, the core component SAP_GWFND is installed as standard and includes the functional scope of IW_BEP.
For information about how to choose the most suitable deployment option for your system landscape, see Embedded Versus Hub Deployment.
Embedded Deployment
Deployment embedded in the SAP Business Suite backend system has the following advantages:
Direct local access to metadata and business 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 backend system need to be synchronized.
Devices need to be integrated with the backend system on a point-to-point basis.
The following diagram shows an example of an embedded backend deployment option. The content component can be any software component that contains content based on the OData Channel. For SAP NetWeaver 7.0, 7.01, 7.02, 7.03, and 7.31 you can install the component IW_BEP in the backend system to reduce the compile time dependency of the content component and also provide a remote deployment option. For SAP NetWeaver 7.40 and higher, the core component SAP_GWFND is installed as standard and includes the functional scope of IW_BEP.
(Embedded Deployment)
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 backend system.
Decoupled lifecycle of consumer applications from the backend system.
Central management of routing and connectivity with backend 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 backend 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 backend systems.
However, note the following considerations:
There will be redundant deployment of metadata or ABAP Dictionary structures.
For SAP NetWeaver 7.00, 7.01,7.02, 7.03, and 7.31 you can install the component IW_BEP in each backend system. For SAP NetWeaver 7.40 and higher, the core component SAP_GWFND is installed as standard and includes the functional scope of IW_BEP
(Central Hub Deployment)
Core Components for SAP NetWeaver Gateway
The mandatory core components for SAP NetWeaver Gateway are listed in the following table, together with a short description of each component. You can install these components in an SAP Business Suite backend system (embedded deployment) or in an SAP NetWeaver Gateway hub system (central hub deployment).
Name |
Type |
Version |
Notes |
|---|---|---|---|
IW_FND |
ABAP |
250 |
Contains core functionality of SAP NetWeaver Gateway as follows:
For SAP NetWeaver 7.40 or higher, see SAP_GWFND. End of the note. |
GW_CORE |
ABAP |
200 |
Contains OData libraries.
For SAP NetWeaver 7.40 or higher, see SAP_GWFND. End of the note. |
SAP_GWFND |
ABAP |
740 |
Available as standard in systems based on SAP NetWeaver 7.40 or higher. This core component contains the functional scope of the core components IW_FND and GW_CORE together with the functional scope of the components IW_BEP and IW_HDB. Since this core component is included as standard in the SAP NetWeaver 7.40 delivery, you do not need to install it explicitly or the components it comprises, namely IW_FND, GW_CORE, IW_BEP, IW_HDB.
If you have 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.40 or higher. You only need to install this component if you have existing Generic Channel services. End of the note. |
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:
Name |
Type |
Version |
Notes |
|---|---|---|---|
IW_BEP |
ABAP |
200 |
Business Enablement Provisioning component. You can install this software component in an SAP NetWeaver Gateway central hub system to enable the implementation of OData resources in the same way as business data in a backend system.
If your system is based on SAP NetWeaver 7.40 or higher, you do not need to install IW_BEP since this functional scope is included in the core component SAP_GWFND, which is available as standard in the SAP NetWeaver 7.40 delivery. End of the note. |
IW_CNT |
ABAP |
200 |
Contains well-defined content, including, for example:
|
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_HDB |
ABAP |
100 |
Provides business content adapter for SAP NetWeaver Gateway with SAP HANA that enables OData exposure of SAP HANA views. For SAP NetWeaver 7.02, 7.03, and 7.31, you can install this component in an SAP NetWeaver Gateway system together with IW_BEP. For SAP NetWeaver 7.40 and higher, you do not need to install component IW_HDB because the core component SAP_GWFND already includes the functional scope of IW_HDB (and IW_BEP) as standard. |
IW_SPI |
ABAP |
100 |
Provides a generic OData adapter for content based on the Service Provider Infrastructure (SPI). For SAP NetWeaver 7.02, 7.03, and 7.31, you can install this component in an SAP NetWeaver Gateway system together with IW_BEP or in an SAP Business Suite system together with IW_BEP. For SAP NetWeaver 7.40 and higher, the core component SAP_GWFND in installed as standard and includes the functional scope of IW_BEP. Consequently you can install component IW_SPI in either an SAP NetWeaver Gateway system or an SAP Business Suite backend system provided the system is based on SAP NetWeaver 7.40 or higher. |
IW_PGW |
ABAP |
100 |
Content provider that enables exposure for SAP NetWeaver Business Process Management (BPM) and Process Observer Task exposure for BPM and SAP NetWeaver Business Workflow. For SAP NetWeaver 7.02, 7.03, and 7.31, you can install this component in an SAP NetWeaver Gateway system together with IW_BEP or in an SAP Business Suite system together with IW_BEP. For SAP NetWeaver 7.40 and higher, the core component SAP_GWFND in installed as standard and includes the functional scope of IW_BEP. Consequently you can install component IW_PGW in either an SAP NetWeaver Gateway system or an SAP Business Suite backend system provided the system is based on SAP NetWeaver 7.40 or higher. |
Optional Components for SAP Business Suite System
You can install the following components in an SAP Business Suite system:
Name |
Type |
Version |
Notes |
|---|---|---|---|
IW_BEP |
ABAP |
200 |
Business Enablement Provisioning component
For SAP NetWeaver 7.40 and higher, the core component SAP_GWFND in installed as standard and includes the functional scope of IW_BEP. End of the note. |
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). For SAP NetWeaver 7.01, 7.02, 7.03, and 7.31, you can install this component in an SAP Business Suite system together with IW_BEP. For SAP NetWeaver 7.40 and higher, the core component SAP_GWFND in installed as standard and includes the functional scope of IW_BEP. Consequently you can install component IW_GIL in an SAP Business Suite backend system provided it is based on SAP NetWeaver 7.40 or higher. |
IW_SPI |
ABAP |
100 |
Provides a generic OData adapter for content based on the Service Provider Infrastructure (SPI). For SAP NetWeaver 7.02, 7.03, and 7.31, you can install this component in either an SAP Business Suite system or an SAP NetWever Gateway system together with IW_BEP. For SAP NetWeaver 7.40 and higher, the core component SAP_GWFND is in installed as standard and includes the functional scope of IW_BEP. Consequently you can install component IW_SPI in either an SAP Business Suite system or in an SAP NetWeaver Gateway system provided it is based on SAP NetWeaver 7.40 or higher. |
IW_PGW |
ABAP |
100 |
Content provider that enables exposure for SAP NetWeaver Business Process Management (BPM) and Process Observer Task exposure for BPM and SAP NetWeaver Business Workflow. For SAP NetWeaver 7.00, 7.01, 7.02, 7.03, and 7.31, you can install this component in either an SAP Business Suite system or an SAP NetWever Gateway system together with IW_BEP. For SAP NetWeaver 7.40 and higher, the core component SAP_GWFND is in installed as standard and includes the functional scope of IW_BEP. Consequently you can install component IW_PGW in either an SAP Business Suite system or in an SAP NetWeaver Gateway system provided it is based on SAP NetWeaver 7.40 or higher. |
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 .