SAP Gateway is a development framework, which is available as an SAP NetWeaver Application Server ABAP (AS ABAP) add-on, which you can install on top of your existing SAP Business Suite or application platform.
SAP Gateway offers development and generation tools to create OData services to a variety of client development tools. Put simply, it establishes a connection between SAP Business Suite data and target clients, platforms, and programming framework.
SAP Gateway provides the following functionality:
Runtime environment for SAP solutions that integrates desktop programs with SAP systems
Runtime features, including user interface, secure data access, database connectivity, and network communications for managing applications running on top of the framework
Infrastructure and tools for developing applications to run on the framework or to enhance SAP solutions that integrate desktop programs with SAP systems
Connection to multiple SAP systems regardless of their versions
The software offers service generation tools that allow you to reuse existing data sources in creating the models and by that, speed up development time. The tools enable you to generate models based on existing:
Business objects that can be selected from the Business Object Repository (BOR)
Remote function modules
The tools do not require coding and allow not only to reuse exiting business objects or screens but also allow no-code based data adaptation capabilities. Data coming from multiple objects can be aggregated, filtered and adapted based on the client application requirements.
The software also offers a tool to develop models. This tool is based on the ABAP Workbench (SE80) and requires ABAP coding skills.
The SAP Gateway documentation consists of the following sections:
Features of the standard mode, introduced with Support Package 03 for SAP Gateway 2.0, are intended to be in accordance with the standards outlined in the Open Data Protocol Specification v2.0 (see http://odata.org). Therefore, any deviation from this standard is not intentional and is subject to change. Consequently, all client implementations shall be validated against the Open Data Protocol Specification.
Do not use objects in the /IWCOR namespace. Only use official APIs.
We strongly recommend using the OData Channel (ODC) programming paradigm for all SAP Gateway development.
As of SAP Gateway 2.0 Support Package 05, you are strongly recommended to use the Service Builder (transaction SEGW) for your OData design-time development . For more information, see SAP Gateway Service Builder.
Depending on whether you want to develop SAP Gateway content in an SAP Business Suite backend system or in an SAP Gateway hub system, you can choose between embedded deployment or central hub deployment. For more information, see Embedded Versus Hub Deployment and Deployment Options.
Copyright 2011, John Resig
Dual licensed under the MIT or GPL Version 2 licenses.
Copyright 2011, The Dojo Foundation
Released under the MIT, BSD, and GPL Licenses.
You can find additional information about SAP Gateway in SAP Note 1560585 .
Further release constraints are listed in SAP Note 1574568 .
Sizing information for SAP Gateway is available on the SAP Service Marketplace in the Quick Sizer Tool under http://service.sap.com/sizing and Quick Sizer Tool. You can use the Quick Sizer Tool for your hardware calculations for your system landscape.
The SAP Community Network (SCN) offers additional information, such as community discussions, blogs, forums, etc. under http://scn.sap.com/community/gateway.