Show TOC

Embedded Versus Hub DeploymentLocate this document in the navigation structure

Use

Depending on whether you want to develop SAP Gateway content in an SAP Business Suite backend system or in an SAP Gateway central hub system, you can choose to implement SAP Gateway in an embedded or central hub deployment scenario:

  • Embedded deployment of core software 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, which contains the composite functional scope of IW_FND, GW_CORE, IW_BEP, and IW_HDB.

  • Central hub deployment of core software 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, which contains the composite functional scope of IW_FND, GW_CORE, IW_BEP, and IW_HDB.

Development System — Deployment Scenarios

To help you decide whether embedded or central hub deployment is the most suitable for you, see the following three deployment scenarios. These deployment scenarios have been conceived to provide you with the flexibility to decide which deployment option best meets your individual requirements.

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

    SAP NetWeaver Release

    Software Components

    Installed in SAP Gateway Hub System

    Installed in SAP Business Suite Backend System

    SAP NetWeaver 7.0, 7.01, 7.02, 7.03, 7.31

    IW_FND

    X

     

    GW_CORE

    X

     

    IW_BEP

     

    X

    SAP NetWeaver 7.40 or SAP NetWeaver 7.50 and higher

    SAP_GWFND

    (X — available as standard as part of SAP NetWeaver 7.40 or SAP NetWeaver 7.50 and higher)

    X

    Advantage:

    • 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.

    Considerations for SAP NetWeaver Releases 7.0, 7.01, 7.02, 7.03, and 7.31

    • Minimum requirement for installing the Add-On IW_BEP in the SAP Business Suite backend system is SAP NetWeaver 7.00 Support Package 18.

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

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

    • If you want to use the Screen Scraping generator, you must install the Add-On IW_SCS in the SAP Business Suite backend system. Minimum requirement for installation in the backend system is SAP NetWeaver 7.00 Support Package 18.

    Considerations for SAP NetWeaver Release 7.40 or SAP Netweaver 7.50 and higher

    • As of SAP NetWeaver 7.40 or SAP NetWeaver 7.50 and higher, component SAP_GWFND is already installed as part of the standard SAP NetWeaver delivery.

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

    • If you want to use the Screen Scraping generator, you must install the Add-On IW_SCS in the SAP Business Suite backend system.

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

    SAP NetWeaver Release

    Software Components

    Installed in SAP Gateway Hub System

    Installed in SAP Business Suite Backend System

    SAP NetWeaver 7.0, 7.01, 7.02, 7.03, 7.31

    IW_FND

    X

     

    GW_CORE

    X

     

    IW_BEP

    X

    You can combine this deployment scenario with an installation of IW_BEP in the backend system.

    SAP NetWeaver 7.40 or SAP NetWeaver 7.50 and higher

    SAP_GWFND

    X

    (X — available as standard as part of SAP NetWeaver 7.40 or SAP NetWeaver 7.50 and higher)

    Advantages:

    • Noninvasive deployment scenario for SAP Business Suite backend system.

    • The life cycle of SAP 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 Gateway system in a demilitarized zone (DMZ).

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

    Considerations

    • The SAP Gateway content implementation cannot use the majority of development objects in the SAP Business Suite backend system. Consequently, you need to create copies of structures and data domains, for example.

    • If you want to use the Screen Scraping generator, you must install the Add-On IW_SCS in the SAP Business Suite backend system. Depending on the setup of the backend system, this might not be permitted. Minimum requirement for installation in the backend system is SAP NetWeaver 7.00 Support Package 18.

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

  • Scenario C: Embedded Deployment — Development in SAP Business Suite Backend System

    SAP NetWeaver Release

    Software Components

    Installed in SAP Gateway Hub System

    Installed in SAP Business Suite Backend System

    SAP NetWeaver 7.0, 7.01, 7.02, 7.03, 7.31

    IW_FND

     

    X

    GW_CORE

     

    X

    IW_BEP

     

    X

    SAP NetWeaver 7.40 or SAP NetWeaver 7.50 and higher

    SAP_GWFND

     

    X

    Advantages:

    • Easy reuse of content in SAP Business Suite backend system. You can reuse structures from the backend system and access local business logic.

    • Reduced total cost of ownership (TCO) as you do not require a separate SAP Gateway system.

    Considerations:

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

    • You must integrate the consuming application or infrastructure with the SAP Business Suite system on a point-by-point basis.

    • Cross-system composition is not advisable.

    • Central SAP Gateway content is not available. Backend-specific content is used in the SAP Business Suite backend system.

For more information about embedded deployment and central hub deployment, see Deployment Options.

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