Show TOC

Architecture and Configuration FlowLocate this document in the navigation structure

This section explains the architecture of the system landscape:

  • SAP Jam

    SAP Jam is SAP's social collaboration platform that provides features such as polls, activity feeds, blogs, video and document sharing and versioning, wikis, public and private groups to help employees quickly connect with one another to enable better corporate problem-solving and decision-making and reduce company costs.

    For more information, see the SAP Library for SAP Jam on SAP Help Portal at http://help.sap.com/sapjam.

  • Web-based Application

    Web-based applications such as the SAP Fiori apps access the ABAP Social Media Integration (ABAP SMI) through the SMI UI5 collaboration components that address the respective OData service implementations on the front-end server.

  • ABAP Social Media Integration (ABAP SMI)

    ABAP Social Media Integration (ABAP SMI) is a library that provides ABAP-based APIs for OData consumption. These APIs send HTTP requests to SAP Jam and address the corresponding OData-based service APIs.

    In addition, ABAP SMI provides a general collaboration layer (package CLB2_MAIN) for the REST communication with any service provider.

  • ABAP SMI Hub

    SAP Jam integration involving multiple systems can be simple when your back-end systems connect to SAP Jam indirectly through one central system, the ABAP SMI hub. As the direct connection to SAP Jam for the central system is already fully configured, the ABAP SMI hub configuration option results in simplified configuration for the systems that call SAP Jam through the hub. We recommend that you set up one system in your system landscape as the ABAP SMI hub.

    Example For SAP Fiori, this can be the ABAP front-end server.
  • SAP Jam Integration

    SAP Jam Integration is the configuration the administrator performs to connect the SAP Jam service provider to an ABAP server.

    The main aspects of the configuration are:

    • Establish the HTTPS connection with service provider SAP Jam; set target server (data center)
    • Set up the SAML 2.0 and OAuth 1.0a authentication and authorization requirements
Figure 1: System Landscape for the SAP Jam Integration
Note

Optionally, ABAP SMI can also be consumed by ABAP-based applications such as SAP CRM in the back end, if the SAP_UI add-on is installed.

For some SAP Fiori apps, ABAP SMI must also be installed in the back-end system. For more information, see Implementation of Collaboration Components.

Configuration Flow

Complete the procedures described in the following sections for each of your SAP back-end systems:

  • The first time you set up the connection between the back-end system/front-end server and the service provider
  • When the technical prerequisites change
  • When adjustments are made for security reasons (such as regular changes of the certificate)

You have the following configuration options:

  • Direct connection to SAP Jam in a system used as an ABAP SMI hub or in any back-end system not using the ABAP SMI hub option

    1. Preparation

      To facilitate the configuration flow, we recommend that you complete the tasks (your server URL and user names) described in this section before you start with the configuration.

    2. Basic Back-End Configuration

      Activities for back-end configuration include setting up connectivity and authentication with SAP Jam.

    3. SAP Jam Configuration

      Activities to be performed in SAP Jam include steps with reference to the tasks you completed in the back end system.

    4. ABAP SMI Configuration

      In the ABAP SMI system, you customize server and application settings, the REST tunnel, and the OData service registry.

      Recommendation Carry out the configuration activities in the order described in the following sections. If you come across any errors during the configuration, see the helpful tips in the monitoring section for SAP Jam Connection.

  • Indirect connection to SAP Jam using an ABAP SMI hub

    1. Prerequisites

      The ABAP SMI hub system must be configured and the connection to SAP Jam tested. An HTTPS connection between the ABAP SMI hub system and the back-end system(s) must exist, and Single Sign-On (SSO) is activated.

    2. Preparation

      To facilitate the configuration flow, we recommend to complete the task (your server URL) described in this section before you start with the configuration of the indirect connection to SAP Jam.

    3. ABAP SMI Configuration

      In the ABAP SMI system, you customize server and application settings, the REST tunnel, and the OData service registry.

After completion of these tasks, you have successfully connected your business application to SAP Jam.

Note If you have used the Social Media ABAP Integration Library (SAIL) until now to integrate SAP Jam with your application, you can use migration report RCLB2_CUST_MIGRATE. For more information, see Migration of SAIL Configuration Data.