Utility and Test Reports

The information in this section may prove helpful during your configuration activities.

Customizing Check

If you want to check the current Customizing version, you can use report RCLB2_CUST_CHECK. It checks selected platforms to see whether Customizing is complete and plausible.

You can run the following transactions to correct your settings, if required.

Table	Transaction	Check
CLB2C_PTYPE	CLB2_PTYPE, node Service Provider Types	Lists the platform type Jam.
CLB2C_PTYPE_METH	CLB2_PTYPE, node API Methods	Enter any missing methods as provided by the check report.
CLB2C_PTYPE_VERS	CLB2_PTYPE, node API Method Versions	Contact SAP for a correction.
CLB2C_PTYPE_CF	CLB2_PTYPE, node Factory Classes	Contact SAP for a correction.
CLB2S_SERVICE	SAP table, use table CLB2C_SERVICE instead
CLB2C_IC_DISP	CLB2_IC_DISP	There should be an entry with: Interceptor Dispatcher ID: CLB_DEFAULT Description: Default Dispatcher without implementing class
CLB2C_PLATF_DEF	CLB2_PLATF_DEF, node Server	You should at least find an entry with: Serv. Provider type: Jam Server: Jam productive Description: SAP Jam Productive (Default) Server URL: https://www.cubetree.com Service Provider: cubetree.com
CLB2C_PLATF_METH	CLB2_PLATF_DEF, node API Method Versions	You must at least find the following entries: GENERIC 22.05.2013 V1 SESSION_GET 31.05.2013 V1 TOKEN_GET 31.05.2013 V1 TOKEN_REVOKE 31.05.2013 V1 USER_FEED_POST 01.01.2014 V1
CLB2C_APPLI	CLB2_APPLI	Contains the default application DEFAULT (= Social Media Integration for ABAP).
CLB2C_AUTH_CONT	CLB2_AUTH_CONT	Contains authentication contexts: APPLI APPUSR USER NONE
CLB2C_AUTH_METH	CLB2_AUTH_METH	For the authentication methods in this table, the following entries are available: OAUTH_10_SHA1 OAUTH_10_SHA1_3 SAML_20 NONE
CLB2C_PLATF	CLB2_PLATF, node Server Communication	Contains server settings as defined in Defining Server Settings.
CLB2C_PLATF_AUTH	CLB2_PLATF, node Authentication Methods	Definition of authentication methods for each server in this table includes entries for SAP Jam's productive server as defined in Defining Server Settings
CLB2S_GW_SRV	SAP table, use table CLB2C_GW_SRV instead
CLB2C_GW_SRV	CLB2_GW_SRV_C, node OData Services	Contains service registry entries as defined in Registering OData Services.
CLB2S_GW_SRV_REL	SAP table, use table CLB2C_GW_SRV_REL instead
CLB2C_GW_SRV_REL	CLB2_GW_SRV_C, node Related Services	Contains OData resources for the Share feature as defined in Registering OData Services.
CLB2S_SRV_PTYPE	SAP table, use table CLB2_GW_SRV_PTYPE instead
CLB2C_SRV_PTYPE	CLB2_GW_SRV_C, node Service Providers	Provides the service provider types as defined in Registering OData Services.
CLB2C_APPL_PLATF	CLB2_APPLI_PLATF, node Application-Server Assignment	Contains service provider for which the service registration is to be valid as defined in Defining Application Settings.
CLB2C_APPL_DATA	CLB2_APPLI_PLATF, node Server Settings	Contains the application ID to which the Jam server is assigned to as defined in Defining Application Settings.
CLB2C_SERVICE	SM31, view CLB2V_SERVICE_C	You do not require an entry in this view unless you are using an external service provider other than SAP Jam or have added a new OData endpoint for SAP Jam. In all other cases, the standard system settings apply. For more information, see Configuring Additional Endpoints.
CLB2C_CONTEXT	SM31, view CLB2V_CONTEXT	Provides the RFC destination to a back-end system for a given application context as defined in Registering OData Services.

If the Customizing check does not show any problems, you can continue to test the connectivity to SAP Jam using the sample reports described in the next section.

Test Reports

We provide test reports for the most important API features. You can use them to check whether the configuration works or to see an example of how tasks can be solved by using the Social Media Integration API.

The most important reports are:

Report	Feature
R_ODL_TEST	This report provides a UI for testing the ABAP SMI OData API. With this report, you can build OData requests, submit them to Jam and see result data. For example, you can create, read, update, or delete groups and feed entries. If this report is executed without errors, you can be sure that SAML2 was set up successfully.
RCLB2_DEMO_GENERIC	This report provides a UI for testing the ABAP SMI collaboration layer. With this report, you can send REST-based requests to SAP Jam and see result data. In contrast to the report R_ODL_TEST, this report does not use the ABAP SMI OData API. If the report is executed without errors, you can be sure that SAML2 was set up successfully.
RCLB2_USER_TOKEN_DELETE	If you get the error message unable to retrieve access token, most probably outdated access tokens are stored in table CLB2D_USER_TOKEN, which you can delete by running report RCLB2_USER_TOKEN_DELETE.

Report

Feature

R_ODL_TEST

This report provides a UI for testing the ABAP SMI OData API. With this report, you can build OData requests, submit them to Jam and see result data.

For example, you can create, read, update, or delete groups and feed entries.

If this report is executed without errors, you can be sure that SAML2 was set up successfully.

RCLB2_DEMO_GENERIC

This report provides a UI for testing the ABAP SMI collaboration layer. With this report, you can send REST-based requests to SAP Jam and see result data. In contrast to the report R_ODL_TEST, this report does not use the ABAP SMI OData API.

If the report is executed without errors, you can be sure that SAML2 was set up successfully.

RCLB2_USER_TOKEN_DELETE

If you get the error message unable to retrieve access token, most probably outdated access tokens are stored in table CLB2D_USER_TOKEN, which you can delete by running report RCLB2_USER_TOKEN_DELETE.

To run the reports, you require the following authorizations:

Authorization Object	Field	Value
S_PROGRAM ABAP: Program Flow Checks	P_GROUP	`CLB2_REP`
	P_ACTION	Enter `*`.