SAP ABAP IMG Activity /UI2/JAM_INTRO (Introduction to SAP Jam Integration and Collaboration)
Hierarchy
☛ SAP_UI (Software Component) User Interface Technology
   ⤷ CA-UI2 (Application Component) SAP UI for Decoupled Innovations
     ⤷ /UI2/IMG (Package) IMG Activities
IMG Activity
ID /UI2/JAM_INTRO Introduction to SAP Jam Integration and Collaboration  
Transaction Code /UI2/73000007   (empty) 
Created on 20130627    
Customizing Attributes /UI2/JAM_INTRO   Introduction to SAP Jam Integration and Collaboration 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /UI2/JAM_INTRO    

Use

The Social Media Integration for ABAP (ABAP SMI) provides an ABAP API that enables you to use features from external service providers such as SAP Jam.

The API sends HTTP requests to the service provider that address the specific REST or OData services of the provider.

Requirements

  • The Customizing activities are only necessary if an application supports this type of collaboration and you are using this application.
  • To integrate SAP Jam with your SAP system, you must obtain a valid SAP Jam license. Contact your account executive for further details.
  • You must be registered as a company administrator on the SAP Jam server.
  • You have maintained a unique email address for the SAP Jam users in the user master record of your back-end system.

Standard settings

The following Customizing entries have been preconfigured by SAP and delivered as entries of tables with delivery class S:

  • View cluster CLB2VC_PTYPE: Definition of service provider types (Jam, StreamWork), and their supported endpoints.
  • View CLB2V_IC_DISP: Definition of dispatcher classes for processing the HTTP requests.
  • View CLB2V_AUTH_CONT: Definition of authentication contexts.
  • View CLB2V_AUTH_METH: Definition of authentication methods.
  • View cluster CLB2VC_PLATF_DEF: Default servers of the service provider.
  • View CLB2V_APPLI: Applications using the collaboration scenario. The default value is DEFAULT (description: Social Media Integration for ABAP).

Activities

The following steps describe the Customizing settings that are specific for each customer system and client and thus not preconfigured by SAP. The steps must be carried out in each client of the back-end system as well as at the SAP Jam server.

The examples focus on connecting to SAP Jam.

Note

  • Previous releases of ABAP SMI known as Social Media ABAP Integration Library (SAIL) were delivered as part of SAP NetWeaver component SAP_BASIS. A previous release may be used in parallel with the version shipped with the UI Add-On. The Customizing tables are different therefore you will need to repeat the Customizing steps described in the following nodes even if the basis settings have been provided.
  • If you have an exisiting connection to SAP Jam established using SAIL, you can now use report RCLB2_CUST_MIGRATE to migrate your configuration data to ABAP SMI. SAIL and ABAP SMI belong to different SAP NetWeaver components and the respective configuration data is stored in different Customizing tables. The report allows you to conveniently migrate your SAIL configuration data to the relevant ABAP SMI Customizing tables. For more information, see Migration Report for SAIL Configuration Data.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG /UI2/JAM_INTRO 0 U000000043 SAP UI Integration - Social Media Collaboration Enablement 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20130701 
SAP Release Created in 100