Show TOC

Registering OData ServiceLocate this document in the navigation structure

In this step, you register the OData service for your Sending Notifications scenario.

Context

Note

The following procedure is only relevant if your application has defined services that are to be registered.

ABAP Social Media Integration (ABAP SMI) provides an OData service registry as a reuse component for SAP applications. The registry allows you to define a subset of OData services that can be exposed in a specific application context to external or on-demand platforms. Unlike the notification filter, the service registry is not integrated into SAP Gateway or ABAP SMI as part of the notification process. It represents an independent service that applications are free to use. There are the following use cases:
  • Supply OData URIs that are part of the notification
    Example OData URIs to address the annotation resource
  • Supply resource URL of the OData service for a subscription (base URL)
    Note

    The metadata link is implicitly derived from this base URL.

  • Support service mapping. Instead of a service A, another service B that covers the same business object that is to be used. This service mapping can be used to replace a service without annotations with an annotated service.

Procedure

  1. In Customizing for SAP NetWeaver, choose Start of the navigation path UI Technologies Next navigation step SAP Jam Integration> Next navigation step Register OData Service End of the navigation path (or run transaction CLB2_GW_SRV_C).

    The "Change View "OData Services (Customer)": Overview screen appears.

  2. Choose New Entries, and complete the fields as follows:
    Field Value
    Bus. Object Type The Business Object Type is mandatory to determine your business context. Usually, the name of the corresponding business object type is used.
    Example BUS1006
    Appl. Context The application context is optional.
    Example SAP CRM uses the application context CRM.
    Ext. Srv. Name The external name of an OData service.

    The value must correspond to an entry in Customizing for the SAP Gateway server (see Customizing for SAP NetWeaver under Start of the navigation path Gateway Service Enablement Next navigation step Service Development for Backend OData Channel> Next navigation step Maintain Services End of the navigation path).
    Service Version Version of the OData Service.
    Example 1
    Collection
    • Enter the collection name or the entity set.
      Example OpportunityCollection
    • If the collection must be determined dynamically, implement BAdI CLB2_REGISTRY (method DETERMINE_COLLECTION).

      You may have to implement the BAdI in a remote system. If this is the case, define the remote RFC destination in view CLB2V_CONTEXT.

    Resource URL Enter the service root URL of the OData service.

    OData services delivered by SAP have the following format:

    /sap/opu/odata/{NAMESPACE}/{SERVICE}/
    Example /sap/opu/odata/CRMSWI01/CRMSMI_SRV/
    Annotation URL
    • Enter URL of the OData annotation resource that describes the specific entity set.
      Example /sap/opu/odata/CRMSWI01/CRMSMI_SRV/AnnotationCollection('x')/Content/$value
    • If the annotation must be determined dynamically, implement BAdI CLB2_REGISTRY (method DETERMINE_ANNOTATION).

      You may have to implement the BAdI in a remote system. If this is the case, define the remote RFC destination in view CLB2V_CONTEXT.
  3. Save your entries.

Results

You have set up the OData service registry.