Local install of SAPUI5 SDK on Windows


  • Do not remove the index.php file as this is the homepage of the wamp server.
  • Ensure that you have started the wamp server and open http://localhost/index.html (start page for sapui5 sdk). Your local server is now ready for SAPUI5 development with your choice of code editor.
  • You can use the path below to point to the SAPUI5.



Importing SHINE Delivery Unit in SAP Cloud Platform

Download SHINE and set the roles in SAP HANA Database Administration page

  1. Download the latest SHINE delivery unit from GitHub.
  2. SAP HANA Cloud Platform Cockpit. Go to Persistence > Databases & Schemas.
  3. Open your tenant database.
  4. Open SAP HANA Cockpit and login as the SYSTEM database user.
  5. On SAP HANA Database Administration page, choose Manage Roles and Users.
  6. If you haven’t created a user for SHINE, create it and name it as SHINE_DEV.
  7. Open the user SHINE_DEV and add the following roles:
    • sap.hana.admin.roles::Administrator
    • sap.hana.xs.lm.roles::Administrator
    • sap.hana.xs.ide.roles::Developer
    • sap.hana.xs.debugger::Debugger
  8. Save.
  9. In the Object Privileges tab, assign the priviledge GRANT_ACTIVATED_ROLE and allow Execute.
  10. Save your changes.

Import the delivery unit.

  1. Log in as SHINE_DEV in SAP HANA Database Administration page.
  2. Choose Lifecycle Management > Delivery Units .
  3. Import and then browse to locate the file HCO_DEMOCONTENT_….tgz you downloaded  previously from GitHub. Open, choose import and save.
  4. Log in with  the SHINE_DEV user into SAP HANA Cockpit
  5. Assign the roles below:


Run the Application

  1. On SAP Cloud Platform Cockpit, go to Persistence > Database & Schemas and open the database. Click on SAP HANA Web-based Development Workbench.
  2. Select Editor and log in as SHINE_DEV.
  3. Select sap > hana > democontent > epm > index.html.
  4. Run the application.

Gateway Service Architecture

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

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.