In the end of 2017, SAP announced the end of maintenance for the Hybrid App Toolkit add-on, also named HAT. Instead of the HAT toolkit, SAP introduced the Cloud build feature which is part of Mobile services. You can find more details about this announced in the blog published by Ludo Noens: https://blogs.sap.com/2017/12/18/end-of-maintenance-for-hybrid-app-toolkit-local-add-on
I was very happy with this announcement, finally no need to install any tool anymore to build my apps. Installing the HAT toolkit was not that hard but it always took some time (time we don’t have during projects). Also, the HAT toolkit required updates frequently, which again took time. This Cloud build feature will ensure us that we don’t have to install anything.
During this announcement, I just started on a new Mobile project. Perfect timing to investigate if the Cloud Build feature was relevant for the project. Main requirement for Mobile Services, the mobile app should have offline capabilities. For that reason, I was looking into mobile services, HAT and the Cloud Build Feature.
Web IDE Cloud Build
I created a first sample app to try out the new Cloud Build feature and already came across my first issue:
I wanted to build my mobile app using the SAP Web IDE. First, I had to deploy it to the Cloud platform, no problem. Then I had to register it to the Fiori Cloud Launchpad, again no problem, at least that’s what I thought. Apparently, the Fiori Cloud Launchpad was not part of our license?! We have Mobile Services (which has the Cloud Build feature) but it still requires the Fiori Cloud Launchpad?!
This means you need SAP Fiori Launchpad in SCP to use the Cloud Build option in the SAP Web IDE
Mobile Services Cloud Build
Although it wasn’t possible in the SAP Web IDE, I didn’t give up. Instead of the SAP Web IDE, I went looking directly in the Build feature of SCP Mobile Services. There I had multiple options:
- the defaulted option was the Fiori Cloud Launchpad
- This is the same as in the SAP Web IDE, useless because we don’t have the Cloud Portal in the license.
- a custom URL
- I could enter a free url, this looked an interesting option
- Fiori destination
- Like the custom url option but here the URL is wrapped in a destination
Regarding the documentation, the options “custom url” and “Fiori destination” should allow us to configure the Cloud Build for on-premise apps. This could be a work-around for missing the Cloud Portal in our license. So, I tried it out:
Issue: which URL should we use? Expecting that my app should use SCP Mobile Services (for offline support), I assumed I had to use my SCP destination to the backend and used the virtual defined url for the Fiori launchpad (which is configured in the Cloud Connector).
Result: didn’t work…
Solution: Use the on-premise url for your app or Fiori Launchpad. (see this tutorial: https://blogs.sap.com/2018/01/24/create-a-fiori-client-with-the-cloud-build-service-for-on-premise-fiori-launchpad/ )
Warning: In the end, this is just a build of the Fiori client with a predefined url and without any connection to SCP Mobile Services.
This means, I still need to use the HAT add-on to support offline…
The Build Feature for on-premise apps is just building the Fiori Client with a predefined url. Nothing more, yet.
If you want to use SCP Mobile Services and don’t have the Cloud Portal, you still need the HAT toolkit to build apps (even if you know that it will be deprecated).
SAP has some work to do before they can deprecate HAT, Cloud Build should support every function of the HAT first.