It seems that whichever way you turn now, there’s some new computing device on the market demanding your undivided attention because it’s lighter, faster and generally cooler than any of its rivals or predecessors. However, no matter what features the latest and greatest gadgets have, they all have one thing in common—an insatiable hunger for data!
Meeting this seemingly never-ending demand for business data can turn into a major headache for application developers if the API into each business system requires the use of proprietary protocols.
What would make life much simpler is an easy–to–use, well defined API that gives access to the rich wealth of business data and functionality in your SAP systems.
SAP NetWeaver Gateway provides an API that is designed to function in just such a manner; and it does so using Microsoft’s open and license free standard called OData.
Consumption of data through the SAP NetWeaver Gateway interface requires nothing more than the ability to make an HTTP request (something any browser can do); in other words, it does not require the use of any SAP proprietary software or protocols.
Although it is perfectly legitimate to do so, the consumption of data through the SAP NetWeaver Gateway interface does not impose any requirement on the developer to be able to write software in ABAP, or even to have any understanding of the internal workings of an SAP system.
Using nothing more than commonly available development tools such as Microsoft’s .Net or Apple’s XCode, or Open Source languages such as Ruby or PHP, you can easily create user interfaces for SAP business data and functionality by consuming the OData messages coming out of SAP NetWeaver Gateway.
In order to make the OData consumption process even easier, SAP deliver a Gateway Consumption Tool. This tool currently supports either Visual Studio 2010 or XCode and can be used to generate either an OData proxy object, or a basic application that wraps the generated proxy object.
As can be seen from the diagram on the right, Microsoft’s OData protocol is based on the Atom Publishing Protocol which in turn, is based on the Atom Syndication Format. SAP has used the standard extensibility features found in OData to provide its own annotations.
The combination of OData’s data format and the SAP Annotations make SAP business information both self-describing and human readable.
These two factors alone lower the barrier for consuming SAP business data and functionality to the point that no specialist knowledge of an SAP system is required before such data can be incorporated into a useful business application running on some external device.
The SAP NetWeaver Gateway interface has been designed to conform completely to the six architectural constraints that define a RESTful software system. This makes the business data content of your SAP systems accessible as RESTful resources through a uniform, stateless interface to any software system that can communicate using HTTP and the OData protocol.
It is easy to think of an “external device” as being simply some type of hand-held, mobile device; but while that idea is perfectly valid and may well be of great significance to you, it’s only one of several possibilities.
The whole focus of the SAP NetWeaver Gateway interface is the REST enablement of SAP business data and functionality, thereby making it easy for non-SAP applications to consume. These could be:
The SAP NetWeaver Gateway interface can be used by any programmable device that can speak HTTP. In providing this capability, it hides the complexities that exists within your system landscape by making use of:
In a word — No. SAP NetWeaver Gateway is not designed to be a channel for the type of transactional applications used by Power Users, neither is it designed to replace existing middleware like SAP NetWeaver PI. In addition to this, SAP NetWeaver Gateway applications are not designed to target A2A or B2B scenarios.
Instead, SAP NetWeaver Gateway is the door through which the mass consumption of SAP business data and functionality is made possible. The target audience for SAP NetWeaver Gateway applications is a group known as Occasional Platform Users (OPU). These are people who need ad hoc access to SAP data and functionality in an easy-to-consume manner.
As part of the SAP NetWeaver Gateway software, you get various Service Provisioning tools. These tools will generate the necessary source code to jump-start the development of your external business applications. These tools can be used in conjunction with widely used Integrated Development Environments (IDEs) such Eclipse, Visual Studio 2010 and XCode.
Not wanting to leave out all the die-hard ABAPers out there, the SAP NetWeaver Gateway Add-On provides you with the OData Channel. This is a set of ABAP classes and interfaces that can be used to develop your own Gateway Model Objects within your backend SAP system. These are then registered with your SAP NetWeaver Gateway system in order to make them accessible to the outside world as RESTful services.
The exact configuration of your SAP NetWeaver Gateway installation will vary depending on your particular use case, but in general, there are two ways in which it can be installed. Either as:
Either way, since the installation of SAP NetWeaver Gateway is provided through the ABAP Add-On process, it will not interfere with the functionality of your existing system.
The SAP NetWeaver Gateway interface:
Sap Technology >