Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 


In March we present the following additions to Mobile Services


  • New Name!

  • New push features

  • Custom push provider

  • HANA Cloud integration services integration

  • Custom URL rewrite rules

  • Removal of inactive users – save your licenses!

New Name

Going forward you will see HANA Cloud Platform mobile services to become the umbrella term for all mobile related services on SAP HANA Cloud Platform. Therefore, HCP mobile services needs to be renamed. The new official product name is

“SAP HANA Cloud Platform mobile service for development and operations”

while the consumer edition is called:

“SAP HANA Cloud Platform mobile service for development and operations, consumer edition”.

We will gradually roll out this name in the product and in the documentation, so please don't be surprised. This is how it looks like now in HCP Cockpit (HCPms is now "Development & Operations"-tile:


New Push Features

All native notification venders improve their services all the time and so do we.

In this release we have included support for:

Google Notifications:

  • Resend Messages – allows to automatically resend messages under certain conditions when a message could not be delivered

  • Logging GCM error codes in the event log

Apple Push Notifications:

  • Support for title, title-loc-key and other additional attributes to better control notifications on iOS devices


  • Custom payload handling for individual WNS notifications


Custom Push Provider

The custom push provider substitutes the HCP mobile services implementation for push services with custom coding.

While configuring your app definition, you can multi-select your custom push provider URL for each device platform. For example, you can define a custom push provider URL for Android. Once you do this, HCP mobile services disables the the Android specific configuration for Android notifications. All Android related push events will then be forwarded to your provided URL – which is typically an HCP provided java application that handles the push for you.

This feature is very suitable, when you want to substitute the native push provides of the device venders.

This is how it looks like:



HANA Cloud Integration services integration

SAP HANA Cloud integration services integration – sounds funny and is an unlucky wording, but it describes best what has happened. Last month, our colleagues of HANA Cloud Integration services have released their new feature set to allow to transform non OData services into OData feeds. In order to consume those published OData services, we have built a small, but shiny integration to your HANA Cloud Integration content:

Once you have done all your integration work and published your service, just click the “Add…” button and select your service from the list. Provide the necessary authentication information and you will be able to access your service from your mobile app.


Custom URL Rewrite Rules

With this version we allow you to provide your own custom http payload rewrite rules. Typically, we rewrite URLs that appear in an OData service to an HCPms URL. In a given OData feed, each URL would be rewritten from “” to</id>”. with the new custom URL rewrite rules, you can completely control the way URLs in the payload should be rewritten.

Just select “Custom Rewrite URL” as Rewrite Mode.

Then click “Configure URLs” to manage your custom rules:


You can even provide regular expressions and test them online:



This is clearly for the advanced user.


Removal of Inactive Users

After a period of three months, unused APPCID (registered users) will be inactivated, saving user licenses. No more to say about this feature.



Have fun,

Martin Grasshoff