Skip to Content

#4.pngThis is a part of the implementation details of How To… Implement End-to-End Push Notifications with HCPms and SAP Gateway.

Steps to Test


Once it is done, you can test the push message via HCPms to see if the message correctly reaches to your device. If you have done the previous step correctly, following steps should work:

– Test the on-boarding via MAF Logon UI

During the user on-boarding, not only the device registration takes place but also updating the on-boarding info with the push identifier should happen. The device should be perfectly ready to receive the push notification from the REST client.

– Test the push from REST client via HCPms

Method – POST

URL – https://<HCPms host name (ex. hcpms-[id]>/Notification/<application connection id>?data=”Hello World!”

Headers – X-SMP-APPCID = <your app connection id on HCPms>


Let’s check the HCPms push log. Go to the log console of HCPms – typically the Mobile Service Cockpit URL is like https://hcpmsadmin-<id>  Find and click “Logs” icon.


Click on “Log Settings” and change the log level for the Push component with Debug/Enabled. It should be a good idea to disable all the other components so that you can focus on the Push message only.


After your HTTP POST message, you should be able to find log information for Notification, which indicates the posted message is coming in and HCPms is communicating with Push Provider.


Check the device for push notification. The message should come in!


What’s next? Reaching out to the SAP backend world.

#5 How To… Implement End-to-End Push Notifications with HCPms and SAP Gateway

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply