In SAP Web IDE’s homepage, choose Import Application.
Select the ABAP back-end server.
In the search field, enter SHOP.
Select the application EPMRA_SHOP.
Run the application by choosing Run-> Run-as ->SAP Fiori Launchpad Sandbox.
SAP Fiori Apps Reference Library shows all apps developed by SAP. You can browse and evaluate the apps before deploying them to your SAP landscape. This site will give all details concerning how to install and configure or extend the apps.
Access the site here.
A gateway service is built using 2 ABAP classes: Data Provider Class and Model Provider Class.
Data Provider Class – contains the implementation of the service’s functionality.
Model Provider Class – provides metadata about the service.
These 2 classes do not communicate with each other. They are linked using configuration.
Two configuration wrappers are created for each of the above classes.
Service Group – configuration wrapper for the Data Provider Class. Contains the internal and external service name. Note that the external name can be different and need not start with Z. By default, SAP sets both of them as the same.
Technical Model Object – configuration wrapper for the Model Provider Class.
A service is complete when we associate the Service Group and the Technical Model Object. This is shown in the diagram below.
Finally, the service needs to be added to the service catalog.
Use of Sybase’s Unwired Platform is not mandatory for consuming Gateway services. Any language can be used, as long as it supports read data from XML and via HTTPS.
SAP Netweaver Gateway is not a new software. It is an ABAP add-on installed on any SAP Netweaver system.
SAP Netweaver Gateway uses the OData RESTful interface.
- OData is an open interface which was developed by Microsoft.
- OData is based on XML and JSON and hence is easy to transfer over the network.
- OData is self-describing.
- Gateway has been designed primarily for the B2C scenario.