Ajith,

We've had similar questions about how to make use of the notification center without having a backing on-premise system. Right now, the most promising (if still theoretical) solution we've found is to try and mimic the OData/WebSocket services that would normally be provided by the on-premise gateway.

Taking inspiration from this blog post Enabling Fiori 2.0 Notification Center in the Cloud using Fiori Launchpad, we realized that it might be possible to have our own OData V4 and WebSocket services accessible at a destination named notifications. We figure if all endpoints remain consistent with those that would be defined on-premise it should work. For example, we know we'll need to have a GET endpoint with the following path to access the badge count:

Request:
GET /sap/opu/odata4/iwngw/notification/default/iwngw/notification_srv/0001/GetBadgeNumber()
Response:
{"@odata.context":"$metadata#Edm.Int32","value":18}

Result in the notification center:

We're still working on the implementation right now, with our primary focus on getting the OData read services up and running. Once we've confirmed that that works though, it'll just be a matter fleshing out the services to any other endpoints the notification center tries to access.

I'd also love to learn about other approaches if you've had any other suggestions.

Thanks,

Brian