Registering OData Services

In this step, you customize ABAP SMI's OData service registry for the relevant OData services.

1. For each application context, check if the service registry entries must be defined in the local system, or a remote system. Access the right system to set up the service registry.
2. SAP delivers standard services in view cluster CLB2VC_GW_SRV_S (transaction SE54). Check whether these services cover your needs.
3. If necessary, register your own OData services. In Customizing for SAP NetWeaver, choose  UI Technologies  SAP Jam Integration>  Register OData Service  (or run transaction CLB2_GW_SRV_C).
4. 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 BO 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 Gateway server (See Customizing for SAP NetWeaver under  Gateway Service Enablement  Service Development for Backend OData Channel>  Maintain Services ).
   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. Example 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.

5. In the dialog structure, under Service Providers, assign all service providers for which the service registration is to be valid, for example, Jam.
6. [Optional]: In the dialog structure, under Related Services, define a service mapping.

   All OData resources that you add here are treated like the OData resource of the corresponding root entry. The resource information from the root node is used while sharing information with the external service provider.

   When using this service mapping, you may also need a key mapping. In this case, you need to implement BAdI CLB2_SERVICE_MAPPING. For this BAdI, a fallback class exists that does a 1:1 mapping; thus a special BAdI implementation is only needed if source and target service have a different key structure.

7. Save your entries.
   Note Entries in the customer table overrule definitions in the SAP table.
8. If a remote access is necessary for a specific application context (for example, CRM), enter an RFC destination for the same in view CLB2V_CONTEXT.
9. In the remote system, apply the following authorizations to the RFC user:

   Authorization Object	Field	Value
   S_RFC Authentication Check for RFC Access	RFC_TYPE	FUGR This is the type of RFC object to which access is to be allowed.
   	RFC_NAME	CLB2_CUST_RFC This is the name (white list) of the RFC object to which access is allowed.
   	ACTVT	16 (Execute)
   S_RFACL Authorization Check for RFC User (for example, Trusted System)	RFC_SYSID	Enter the RFC system ID for the trusted system connection.
   	RFC_CLIENT	Enter the RFC system client for the trusted system connection.
   	ACTVT	16 (Execute)
   S_TABU_DIS Table Maintenance (via standard tools such as SM30)	ACTVT	03 (Display)
   	DICBERCLS	CLB2 (Collaboration) This is the table authorization group.