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:
The REST tunnel is a new ABAP SMI feature and was not supported in SAIL.
While the report transfers the root services, you have to add the service mapping of the related services manually.
For more information, see the report documentation in your ABAP SMI system.
For information about how to test your Customizing settings for the connection to SAP Jam, see Utility and Test Reports.
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.