Collaboration platforms (external service providers) such as SAP Jam can be used as feed aggregators that consolidate information that is important for a business user from different resources in one place. This section describes how to use ABAP Social Media Integration (ABAP SMI) to configure the distribution of notifications to SAP Jam.
The Sending Notifications scenario as described in the following sections focuses on the integration of SAP Jam as the service provider, based on change documents originating from ABAP-based business applications. This applies to applications:
SAP Gateway services are used as follows:
Note that the consumption model (OData model implementation) specific to the Business Suite component is installed in the Business Suite system.
You can run the SAP Gateway components as follows:
This information is intended for system administrators working on the integration of SAP Jam with a customer’s on-premise SAP application landscape.
Before you start with the configuration activities described in this section, you must have done the following:
The following table lists the transactions you should be familiar with when performing the configuration steps for sending notifications to SAP Jam.
Transactions in SAP Back-End Systems
|SAP Gateway System|
|/IWFND/ERROR_LOG||SAP Gateway: Error Log|
|/IWFND/MAINT_SERVICE||Activate and Maintain Services|
|SAML2||SAML 2.0 Configuration|
|SOAUTH2||OAuth 2.0 Configuration|
|SAP Business Suite System|
|CLB2_PLATF||Service Provider Settings|
|CLB2_GW_SRV_C||ABAP SMI Service Registry|
|SBGRFCCONF||bgRFC System Configuration|
Events for Change Documents
|SAP Gateway and SAP Business Suite systems|
Analyze Application Log
|SM59||Configuration of RFC Connections|
|SPRO||Implementation Guide Customizing|
For more information about these transactions, see the relevant documentation in your SAP system.