Over the past 18 months, I’ve published numerous blogs about the mobile service for SAP Fiori and how it can help customers achieve the full potential of the Fiori/SAPUI5 investment on mobile devices. Aside from a recent post talking about my colleagues who were attending SAP TechEd Las Vegas, I’ve been pretty quiet. Why is that? You might ask, and I’m glad you did.
I’ve been working on a secret project.
But let’s back up. For anyone that’s done any testing with the mobile service for SAP Fiori, you know that alot of the actual “heavy lifting” is done by SAP Cloud Platform Mobile Services. Push, Offline, Log levels, feature management, app security, the Fiori Client and the Kapsel SDK are all provided by Mobile Services. The mobile service for SAP Fiori took these (mostly) runtime components and created features and workflows to simplify the end to end process.
The most important of these features is the cloud build service. The cloud build service allows customers to transform their web based SAP Fiori apps into hybrid apps, complete with robust customization capabilities, completely in the cloud. The cloud build service was unique to the mobile service for SAP Fiori.
I’m happy to say that, while the cloud build service continues to be part of the mobile service for SAP Fiori, it has been added as the “Cloud Build Feature” to SAP Cloud Platform Mobile Services. Let’s take a closer look!
There are 3 key areas where a Mobile Services customer could interact with the Cloud Build Service – when creating Destinations, when creating or updating Signing Profiles and when creating Application definitions .
A new destination type has been added of type “Fiori”:
Fiori destinations are designed to point to a Fiori Launchpad / Fiori application URL, and are the only type that can be used by the Cloud Build Feature. A destination for SAP Fiori Cloud is automatically created for you, you’ll only need to add a new destination if you’re using something other than the default SAP Fiori Cloud Launchpad. For example, if you are running your Fiori Launchpad on-premise, you would need to create a destination here in order to create a mobile app later on.
Code signing is a process by which a software author verifies that an app that he creates has not been tampered with. It does so through the creation of a cryptographic hash of the binary. Any alteration to the binary should fundamentally change the hash, resulting in an app that the OS knows has been tampered with. In Mobile Services, signing is done as part of the cloud build process, and the signing information used to sign apps is stored in Signing Profiles. For iOS developers, an enterprise or developer certificate can be uploaded, along with the provisioning profile. Since all data in the cloud is technically the customer’s data, it’s never really leaving your possession. For Android, you can upload a KeyStore file, password and Alias. Additionally Android developers may choose to simply have Mobile Services generate a signing profile by specifying the required information:
Creating Native/Hybrid Apps
A new Config Template has been added, called “SAP Fiori”:
Once created, by using the SAP Fiori Config Template the Cloud Build Service is automatically added as an included feature:
To complete the configuration is simple, all you need to do is click on the feature, and feature details will be opened:
Specify Device App Name. This is the name that end users will see when they install the app onto their device. Then specify a Fiori Destination. If you want, pick your own icons and splash screens. This is particularly useful if you want to create an enterprise branded user experience for your mobile app. Save those changes!
To create your app, click on the Build History tab, then click Build:
Pick a signing profile, a minimum supported OS, and any specific build customizations, then click OK. The app will begin building:
When the build is complete, you can download the binary and install the app onto your mobile device for testing:
You can also drill into the build to view items such as the build log and an indication of what build options were selected during the build process:
What is it that you’ve built? Your newly generated app is a custom SAP Fiori Client. It’s essentially the same app as you would download from the commercial app stores, but it’s pre-configured with your branding, pre-populated with the correct connectivity information, and it’s signed so it’s ready to install on your mobile device. To learn more about the SAP Fiori Client, please refer to the Overview in the SAP Help Portal, or the dedicated section on SAP EA Explorer.
And that’s it! The Cloud Build Feature is now a first class citizen in the Mobile Services fabric of capabilities. It can be used in conjunction with other features. Need your app to have a password, or want to gather usage information about the app you just built? Configure the Client Policies feature. Yes it is can be that simple.
We’re not done with the Cloud Build Feature, not even close. But since we don’t discuss roadmap items in blogs, you’re just going to have to stay tuned….