Scenario A: Central Hub Deployment — Development in SAP Business Suite Backend System

Advantage

It enables to reuse data stored in the SAP Business Suite system easily since development takes place in the system in which data is stored.

Considerations

To enable communication between the SAP NetWeaver Gateway system and the SAP Business Suite backend system, you must install IW_BEP in the backend system.

The life cycle of SAP NetWeaver Gateway content is dictated by the frequency of updates in the SAP Business Suite backend system.

Cons

Requires separate NetWeaver Gateway system

Scenario B: Central Hub Deployment — Development in SAP NetWeaver Gateway System

Advantages

Noninvasive deployment scenario for SAP Business Suite backend system.

The life cycle of SAP NetWeaver Gateway content is loosely coupled to the lifecycle of the SAP Business Suite backend system.

To enable external access and fulfill security requirements, you can locate the SAP NetWeaver Gateway system in a demilitarized zone (DMZ).

You need only a single installation of the SAP NetWeaver Gateway Add-Ons within the system landscape.

Cons

Requires separate NetWeaver Gateway system.

Considerations

The SAP NetWeaver Gateway content implementation cannot use the majority of development objects in the SAP Business Suite backend system. Consequently we need to create copies of structures and data domains.

We must choose this deployment scenario if we cannot install the SAP NetWeaver Gateway Add-Ons in the SAP Business Suite backend system. We might not be able to install Add-Ons in the backend system for reasons of security, stability, or incompatibility (due to system release).