Show TOC

Migration of SAIL Configuration DataLocate this document in the navigation structure

If your connection to the external service provider SAP Jam was established using Social Media ABAP Integration Library (SAIL), you can use report RCLB2_CUST_MIGRATE to migrate your configuration data to the successor to SAIL, ABAP Social Media Integration (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.

After successful execution of the report, you can skip all configuration tasks for connecting ABAP SMI with SAP Jam described in this section with the exception of the following procedures:

Prerequisites
  • The Social Media ABAP Integration Library (SAIL) in component SAP_BASIS is available in your back-end system.
  • You have connected your application to SAP Jam using SAIL.
  • You plan to use the collaboration features of ABAP SMI for your application.
  • You have not yet started the configuration for connecting ABAP Social Media Integration (ABAP SMI) in component SAP_UI with SAP Jam.
Procedure
  1. In your ABAP SMI system, run transaction SE38.
  2. Execute the report RCLB2_CUST_MIGRATE in Migration mode.

    For more information, see the report documentation in your ABAP SMI system.

  3. To verify that the migration of your configuration data was successful, run the Customizing test reports.

    For information about how to test your Customizing settings for the connection to SAP Jam, see Utility and Test Reports.

Results

You have transferred your SAIL configuration data and verified that the connection with SAP Jam works.

If required, complete the Customizing for the REST tunnel and the service mapping.