There are a couple of reasons to standardize around SAPUI5. You don’t need to do anything if you’re working with SAP Web IDE, since it takes care of everything when you create development projects. While when you’re working with an external IDE, there’s a smart way to incorporate SAPUI5 component into your application.
But apart from these, the commonly used method to access SAPUI5 files is via a shared service called sapui5, which can be accessed within the HTML application by providing a particular route definition in the application’s deployment descriptor. The syntax for the same is shown below:
In the syntax, the path feature shows that any requests consisting of /resources path will be processed by the sapui5 service, that fills up SAPUI5 content.
After the route in the applicator descriptor is defined, you can use configured path in the HTML code. So, when that HTTP request is triggered, shared dispatcher service shall proxy via sapui5 service and the SAPUI5 content files, automatically!
Besides the route upfront setup, every other setup is just identical and simple to carry out. When you want to port pre-defined SAPUI5 apps or their content into SAP HCP, then the transparency of the application really helps.
Access to External Resources
Usually HTML5 applications developed on SAP HCP, will need to use data and information from RESTful services which aren’t accessible from public internet. Some of these are RESTful services, OData services and On-Premise services.
In order to use these services, you’ll be required to use the Connectivity Service, which gives intuitive entity types like, sales order, etc.