Deployment Options 
This section describes the deployment options available for SAP NetWeaver Gateway.
The following diagram shows the software component (SC) structure; SAP NetWeaver Gateway core and optional backend components. The components are described in the following sections.
SAP NetWeaver Gateway Hub Components
SAP NetWeaver Gateway hub components are listed in the following table, together with a short description of each component.
Name |
Type |
Version |
Tech. |
Notes |
|---|---|---|---|---|
IW_CNT |
ABAP |
2.0 |
200 |
Contains well-defined content, including, for example:
|
IW_CBS |
ABAP |
2.0 |
200 |
Contains application basis functionality, such as SAP NetWeaver Gateway enablement of business workflow. IW_CBS applications are technically similar to IW_CNT applications. |
IW_FND |
ABAP |
2.5 |
250 |
Contains framework of SAP NetWeaver Gateway hub as follows:
|
GW_CORE |
ABAP |
2.0 |
200 |
Contains OData libraries. |
Backend Components
SAP NetWeaver backend components are listed in the following table, together with a short description of each component. These are optional components; however, if you wish to use the OData Channel, you must install the IW_BEP (Backend Enablement and Event Provisioning) component.
Name |
Type |
Version |
Tech. |
Notes |
|---|---|---|---|---|
IW_SCS |
ABAP |
2.0 |
200 |
Backend part of screen scraping |
IW_BEP |
ABAP |
2.0 |
200 |
Backend Enablement and Event Provisioning component that enables a business backend to provide OData resources and externalize events. For example, allows remote enabling of BOR events. |
Consumers
The consumers of SAP NetWeaver Gateway depend on customers' requirements; the components are therefore denoted by XX_XXX in the software components diagram (consumer-speciific layer).
Deployment Choices
You can install SAP NetWeaver Gateway independent of consumer technologies, but the consumer technologies' installed software components must also be installed on one SAP NetWeaver Gateway server. You can connect multiple consumer technologies to one SAP NetWeaver Gateway instance.
You can deploy SAP NetWeaver Gateway in two different ways:
Locally, where the SAP NetWeaver Gateway hub plus optional backend components are deployed in the SAP Business Suite system. With this option you only need the backend system and do not need a dedicated SAP NetWeaver Gateway hub server. Note that in this case the backend system needs to have SAP NetWeaver 7.02 SP07.
Remotely, where the SAP NetWeaver Gateway hub components can be deployed in a standalone system, either behind or in front of the firewall. In this case the optional backend components still need to be deployed on an SAP Business Suite backend system.
Remote Deployment
Remote deployment consists of a central single hub deployment with SAP NetWeaver Gateway on a dedicated server. The software component structure diagram at the beginning of the section shows a remote deployment.
Remote deployment 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 business backend.
Decoupled lifecycle of consumer applications from the application backend.
Central management of routing and connectivity with application 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 attacking the SAP NetWeaver Gateway system will not automatically harm the business backend.
A separate SAP NetWeaver Gateway system can be implemented in a DMZ (demilitarized zone) for external access.
Independent innovation speed of SAP NetWeaver Gateway and the connected application systems.
Note
Remote deployment is only possible based on SAP NetWeaver 7.02.
However, note the following considerations:
There will be redundant deployment of metadata or Data Dictionary structures.
SAP NetWeaver Gateway enabling component must be installed in each application system.
Local Deployment
Local deployment, that is, embedded deployment with the local application 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.
However, note the following considerations:
The innovation speed of SAP NetWeaver Gateway and the application system need to be in sync.
Devices need to be integrated with the application system on a point-to-point basis.
IW_FND requires SAP NetWeaver 7.02.
The following diagram shows an example of a local deployment option. The content component can be any software component that contains OData Channel-based content. The content component only depends on IW_BEP. This reduces the compile time dependency of the content component and also provides a remote deployment option.
