Show TOC

Message FlowLocate this document in the navigation structure

This section describes the message flow between a business application and SAP Jam when a notification is sent.

The figure below shows the message flow in case of a direct send from the back-end system.

Figure 1: Message Flow
  1. Trigger Event

    The application triggers an event that is caught by a specific event handler. For example, an application transaction posts changes to the database resulting in a change document. An event handler for such a change document may be registered in transaction SWEC. The event handler is now responsible for constructing and sending the notifications. If the application has not defined a specific event handler function, you can use the SMI default function CLB2_CD_NOTIFICATION_SEND in transaction SWEC to do so.

  2. Get Subscriptions

    The event handler collects the subscriptions from SAP Gateway using Gateway's ABAP API.

    The subscriptions must have been created before. Applications use the service registry of ABAP SMI to define the correct OData service for a specific business object type.

  3. Sort and Filter Subscriptions

    The event handler clusters the subscriptions to build only one notification for each target server and language of the subscribers. The list of subscriptions is filtered using the ABAP SMI notification filter. To prevent spamming, notifications are only sent for OData services that have been activated here. Optionally, an authorization check can take place that verifies that the user is authorized to send notifications.

  4. Send Notification

    The event handler finalizes the notification and passes it to ABAP SMI. The notification message may contain URLs for one of the following:

    • Navigating to the UI (application Web client) for displaying the business object in the original system
    • Retrieving further information about the business object using an OData service
  5. Parallelization of Distribution in ABAP SMI

    A bgRFC inbound communication is scheduled to forward the OData notifications asynchronously to all possible target servers.

  6. bgRFC Processing/Forward Notification to SAP Jam

    HTTPS communication with SAP Jam is required to post the BO notification as a feed entry in SAP Jam. Before posting the notification to SAP Jam, the ABAP SMI component sends an authentication request. As SAP Jam accepts only the author of the notification as the authenticating user, ABAP SMI repersonalizes the technical SAP Gateway user as used in the bgRFC communication.

    Due to security constraints as defined by SAP Jam, all potential authors of notifications or business object changes must satisfy the following conditions:

    • Have a user record and an email address in the back-end system (or in a connected SAP Identity Service)
    • Are registered as members of the specific company at SAP Jam