Show TOC

Architecture of System LandscapeLocate this document in the navigation structure

The following figures illustrate how you can use Social Media Integration (ABAP SMI) to forward notifications to SAP Jam in the form of REST API calls:

Figure 1: System Landscape for Directly Sending Notifications to SAP Jam
Figure 2: System Landscape for Sending Notifications Through the SAP Gateway Server (ABAP SMI Hub)
  1. Subscribe or Unsubscribe

    SAP Gateway manages subscriptions for all of its OData resources. When OData resources have been subscribed to – either by OData calls or using ABAP API calls on the SAP Gateway server – ABAP SMI can distribute notifications based on these subscriptions. As subscriptions are based on OData resources, an OData service representation (collection or entity set) must exist for this business object; the assignment of the right OData service and collection takes place through the ABAP SMI service registry (see Registering OData Service).

    The application add-on directly communicates with the subscription API of the SAP Gateway component that is installed in the back-end system.

    Prerequisites for successful subscriptions are:

    • You have installed an SAP Gateway system. This includes the SAP Gateway server that needs to be installed in the Business Suite system.
    • You have configured the RFC communication between the SAP Gateway server and the application back-end.
    • You have registered the relevant OData service with the SAP Gateway server.
  2. Notification Trigger

    Any application can issue notifications based on any type of event. For example, changes to a business object (change documents) or a workflow event can trigger the notification.

    This notification trigger might be a special application development, or a generic trigger function provided by ABAP SMI. For example, in ABAP SMI, you can add function CLB2_CD_NOTIFICATION_SEND in transaction SWEC as an event handler function for change documents. For more information, see Customizing for SAP NetWeaver under Start of the navigation path UI Technologies Next navigation step SAP Jam Integration Next navigation step Notifications Next navigation step Register Event Handler for Change Documents End of the navigation path.

  3. ABAP SMI in the Application Back-End System

    ABAP Social Media Integration (ABAP SMI) connects to SAP Jam, either from the Business Suite system, or from the SAP Gateway system. This configuration includes the registration of the service consumer with SAP Jam as explained in Connecting to SAP Jam with ABAP SMI. After that, ABAP SMI can make use of SAP Jam's REST API interface to create feed entries based on the notification.

    In addition, certain specific attributes that play a role in the Sending Notifications scenario must be set up in the back-end system.

  4. Business Object Display in SAP Jam

    SAP Jam is able to render business object data using a Business Record Viewer (Thing Inspector). The object data is not copied to SAP Jam; it is only represented by an OData resource link that dynamically and temporarily retrieves the data from the back-end system if the user is authorized to do so. The rendering is based on OData annotations that need to be specified for the OData resource.

    All necessary information (resource as well as annotation links) are transported with the notifications. For more information, see SAP Help Portal for SAP Jam at http://help.sap.com/sapjam Start of the navigation path Developer's Guide End of the navigation path.