The first version of the SAP Jam Gateway Notification Configuration Guide is available under https://scn.sap.com/docs/DOC-39577.

Motivation

SAP Gateway is capable of managing subscriptions for any of its OData resources.
Subscriptions can be made either by REST API calls, or via ABAP OO calls at the Gateway hub.
Subsequently, SAP Gateway can distribute notifications based on these notifications.
Any application can issue the notifications by any application or by any type of event. For instance,
changes to any business object (change documents) or a workflow event can trigger the notification.

On the other hand, an external service provider, such as SAP Jam, can be used as a feed aggregator
that collects all of the information that is important for a (business) user from different resources in
one place.

The specified document describes how both pieces can be connected: How you can aggregate the
Gateway notifications in SAP Jam, the SAP collaboration platform, with aid of the Social Media ABAP
Integration Library (SAIL).
It explains the scenario, the components that are involved, the necessary Customizing steps, and it
also may serve as an implementation guide if you need to connect an application on your own.

The following block diagram illustrates that the Social Media ABAP Integration Library (SAIL) can be used to forward Gateway notifications against SAP Jam in the form of REST API calls: