Deployment Options
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
This section describes the two deployment options available for SAP Gateway:
Central hub deployment of SAP Gateway core components IW_FND and GW_CORE in an SAP Gateway hub system.
As of SAP NetWeaver 7.40 or SAP NetWeaver 7.50 and higher, the core software component for SAP Gateway is SAP_GWFND (740 or 750), which contains the composite functional scope of IW_FND, GW_CORE, IW_BEP, and IW_HDB.
Embedded deployment of SAP Gateway core components IW_FND and GW_CORE in an SAP Business Suite backend system.
As of SAP NetWeaver 7.40 or SAP NetWeaver 7.50 and higher, the core software component for SAP Gateway is SAP_GWFND (740 or 750), which contains the composite functional scope of IW_FND, GW_CORE, IW_BEP, and IW_HDB.
For more information about the SAP Gateway components, see Installing SAPÂ Gateway Components and the SAP Note 1569624 
.
All SAP Gateway 2.0 components are non-modifying components. For more information, see SAP Note 1569624 .
Embedded or Central Hub Deployment?
You can install SAP Gateway independent of consumer technologies, however the software components installed for the consumer technologies must also be installed on one SAP Gateway server. You can connect multiple consumer technologies to one SAP Gateway instance.
Deployment options:
Central hub deployment: The SAP 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 or SAP NetWeaver 7.50 and higher, the core component SAP_GWFND is installed as standard and includes the functional scope of IW_BEP.
Embedded deployment: The core components for SAP 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 Gateway central hub system.
For information about how to choose the most suitable deployment option for your system landscape, see Embedded Versus Hub Deployment.
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 backend system.
Decoupled lifecycle of consumer applications from the SAP Business Suite backend system.
Central management of routing and connectivity with SAP Business Suite backend 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 backend 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 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 or SAP NetWeaver 7.50 and higher, the core component SAP_GWFND is installed as standard and includes the functional scope of IW_BEP
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 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 backend system need to be synchronized.
Devices need to be integrated with the SAP Business Suite backend 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.
Core Components for SAP Gateway
The mandatory core components for SAP 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 Gateway hub system (central hub deployment).
Name |
Type |
Version |
Notes |
|---|---|---|---|
IW_FND |
ABAP |
250 |
Contains core functionality of SAP Gateway as follows:
Note
For SAP NetWeaver 7.40 or SAP NetWeaver 7.50 and higher, see SAP_GWFND. |
GW_CORE |
ABAP |
200 |
Contains OData libraries. Note
For SAP NetWeaver 7.40 or SAP NetWeaver 7.50 and higher, see SAP_GWFND. |
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. Note
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. |
SAP_GWFND |
ABAP |
750 |
Available as standard in systems based on SAP NetWeaver 7.50 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.50 delivery, you do not need to install it explicitly or the components it comprises, namely IW_FND, GW_CORE, IW_BEP, IW_HDB. Note
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.50 or higher. You only need to install this component if you have existing Generic Channel services. |
For more information about release dependencies, see Installing SAP 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 Gateway central hub system to enable the implementation of OData resources in the same way as business data in a backend system. Note
If your system is based on SAP NetWeaver 7.40 or SAP NetWeaver 7.50 and 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 and SAP NetWeaver 7.50 deliveries. |
IW_CNT |
ABAP |
200 |
Contains well-defined content, including, for example:
|
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_HDB |
ABAP |
100 |
Provides business content adapter for SAP 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 Gateway system together with IW_BEP. For SAP NetWeaver 7.40 or SAP NetWeaver 7.50 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 Gateway system together with IW_BEP or in an SAP Business Suite system together with IW_BEP. For SAP NetWeaver 7.40 or SAP NetWeaver 7.50 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 Gateway system or an SAP Business Suite backend system provided the system is based on SAP NetWeaver 7.40 or SAP NetWeaver 7.50 and 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 Gateway system together with IW_BEP or in an SAP Business Suite system together with IW_BEP. For SAP NetWeaver 7.40 or SAP NetWeaver 7.50 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 Gateway system or an SAP Business Suite backend system provided the system is based on SAP NetWeaver 7.40 or SAP NetWeaver 7.50 and 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 Note
For SAP NetWeaver 7.40 or SAP NetWeaver 7.50 and higher, the core component SAP_GWFND in installed as standard and includes the functional scope of IW_BEP. |
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 or SAP NetWeaver 7.50 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 SAP NetWeaver 750 and 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 Gateway system together with IW_BEP. For SAP NetWeaver 7.40 or SAP NetWeaver 7.50 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 Gateway system provided it is based on SAP NetWeaver 7.40 or SAP NetWeaver 7.50 and 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 Gateway system together with IW_BEP. For SAP NetWeaver 7.40 or SAP NetWeaver 7.50 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 Gateway system provided it is based on SAP NetWeaver 7.40 or SAP NetWeaver 7.50 and higher. |
For more information about landscape recommendations, see the following presentation on SAP Community Network: https://wiki.sdn.sap.com/wiki/display/SLGB/Landscape+Recommendations.