This section describes how to use the collaboration features of the ABAP Social Media Integration (ABAP SMI) to integrate SAP Jam with your business applications.
The configuration described in the following sections focuses on the integration of SAP Jam as the service provider with ABAP-based business applications. This applies to applications:
This information is intended for system administrators working on the integration of SAP Jam with the customer’s on-premise SAP application landscape.
You have set up an ABAP-based SAP system that supports SAP Jam integration with ABAP SMI as described in Implementation of ABAP Social Media Integration (ABAP SMI).
The following table lists the transactions you should be familiar with when performing the configuration steps for connecting SAP Jam with your business application.
Transactions in SAP Back-End Systems
Transaction Code | Description | Remarks |
---|---|---|
CLB2_PLATF | Service Provider Settings | |
CLB2_APPLI_PLATF | Application Settings | |
CLB2_GW_SRV_C | OData Services | Only required if you will set up the system to send notifications (see Sending Notifications to SAP Jam) |
CLB2_TUNNEL | Configure REST Tunnel | Only required for SAP Fiori integrations or if you are using an ABAP SMI Hub |
SAML2 | SAML 2.0 Configuration of ABAP System | Not required if you are using an ABAP SMI Hub |
SE38 | Execute reports | Not required if you are using an ABAP SMI Hub |
SICF | Define Services | Not required if you are using an ABAP SMI Hub |
SPRO | Implementation Guide Customizing | Not required if you are using an ABAP SMI Hub |
SSFA | Change View "Application-Specific SSF Parameters" | Not required if you are using an ABAP SMI Hub |
STRUST | Trust Manager | Not required if you are using an ABAP SMI Hub |
SU01 | User Maintenance | Not required if you are using an ABAP SMI Hub |
For more information about these transactions, see the relevant documentation in your SAP system.