Register Login
Python Photoshop SAP Java PHP Android C++ Hadoop Oracle Interview Questions Articles Other

Deployment Option for SAP Gateway

Updated May 18, 2018

This tutorial describes the different option for deploying SAP Gateway related component based on commonly used scenarios.

There are three Deployment options for SAP Gateway

1) SAP Gateway hub deployment with service deployment in the SAP Business Suite backend

2) SAP Gateway hub deployment with service deployment in the SAP Gateway hub

3) SAP Business Suite embedded deployment & service development

SAP Gateway hub deployment with service deployment in the SAP Business Suite backend

  1. In this scenario, the SAP Gateway functionality are only used on one dedicated server that is SAP Gateway hub system.
  2. The services are developed in SAP Business Suite backend system and get exposed in SAP Gateway hub server.
  3. The Gateway service is best deployed in SAP Business Suite backend system where either the component IW_BEP is available or in case the system is running on top of SAP NetWeaver 7.40 those are leverage the component SAP SAP_GWFND.

Advantage of SAP Business Suite backend hub deployment

  • Routing and composition of multiple systems are supported
  • Single point of access to beckend system
  • The SAP Gateway hub system can be based on a newer upgrade (7.31 or 7.40) which supports the additional authentication option such as Kerberos.
  • For security, there is no direct access to the backend system but only by the SAP Gateway hub access.

SAP Gateway hub deployment with service deployment in the SAP Gateway hub.

  1. In this 2nd scenario, the SAP Gateway core components are only used on one dedicated server which is SAP Gateway hub system.
  2. In correspondence to the previous scenario in this scenario also the service development takes place in the SAP Gateway hub system.
  3. This option is used when either no service development are been performed on the backend system or in the case of upgrade higher than SAP NetWeaver higher than upgrade 7.40. This indicates that the  service developer is limited to an interface which is accessible the RFC in the backend.

Advantages of SAP Gateway hub deployment with service deployment in the SAP Gateway hub.

  • Routing and composition of multiple systems are supported
  • There is no need to install SAP Gateway component in the backend.
  • Services that have been developed by partner doesn't require any deployment in the backend system.
  • Single point of access to backend system
  • The SAP Gateway hub system can be based on a newer upgrade (7.31 or 7.40) which supports the additional authentication option such as Kerberos.
  • For security, there is no direct access to the backend system but only by the SAP Gateway hub access.

Disadvantages of SAP Gateway hub deployment with service deployment in the SAP Gateway hub.

  • Access are only limited to remote-enabled interfaces such as BAPIs, SPI Objects etc.
  • GENIL objects cannot be accessed remotely.
  • Interface that is remote-enabled may not optimally suited.

SAP Business Suite embedded deployment & service development

  • Services are developed and published in SAP Business Suite backend system same as SAP Gateway system.
  • No dedicated SAP Gateway hub system are needed and the required SAP Gateway components are directly deployed on SAP Business Suite system.
  • Additional security component is needed for extranet scenarios.

Advantage SAP Business Suite embedded deployment

  • Less runtime overhead as remote calls are reduced.

Disadvantages SAP Business Suite embedded deployment

  • As the multiple SAP Business Suite system are used therefore SAP Gateway system would have to be configured multiple times.
  • In the case of embedded deployment the system must not be used as a hub for additional SAP Bussiness Suite backend systems, therefore, Routing and composition cannot be used.
  • Upgradation of larger components in a SAP Bussiness Suite backend system is usually possible only once or twice per year

Recommended Posts:
×