Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-STW (Application Component) Social Media ABAP Integration Library⤷
S_CLB_CUST (Package) Customizing of the Collaboration Platform Library
IMG Activity
| ID | S_CLB_REGISTRY | Define OData Service Registry |
| Transaction Code | S_YI3_39000152 | (empty) |
| Created on | 20121022 | |
| Customizing Attributes | S_CLB_REGISTRY | Define OData Service Registry |
| Customizing Activity | S_CLB_REGISTRY | Define OData Service Registry |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | S_CLB_REGISTRY |
Use
The OData Service Registry is a reuse component for any application. The registry allows you to define a subset of OData services that can be published in a given application context to external or on-demand platforms.
The definition must take place in the application system, usually an SAP Business Suite system that also comprises the BEP (Backend Event Publisher) Add-On of SAP NetWeaver Gateway.
For more information, see SAP Note 1748988.
Requirements
The OData service registry only makes sense in connection with an SAP NetWeaver Gateway system. If you do not actively use SAP NetWeaver Gateway, for instance for sending notifications to an external social media platform, you can skip this activity.
Standard settings
SAP standard services may have been delivered from view cluster CLBVC_GW_SRV_S (transaction SE54). Check these default settings, first.
Activities
If necessary, you can register your own OData services in view cluster CLBVC_GW_SRV_C (Customer) as follows:
- The business object type (mandatory) and the application context (optional) determine your business context.
- The external service name is the external name of an OData Service. The value must correspond to an entry in Customizing of the Gateway hub (see in Customizing of SAP NetWeaver -> Gateway -> OData Channel Development with IW_BEP -> Activate and Maintain Services).
- The URL field shall contain the static part of the OData service, following the pattern:
/sap/opu/odata/{NAMESPACE}/{SERVICE}/{COLLECTION}/?$format=xml - The internal URL prefix for addressing the Gateway system is added from the information that has to be maintained (once) in the Customizing activity Server settings in the form of the RFC destination of the Gateway hub.
- You can fetch the entries from the registry by using the method GET_REGISTRY_SERVICES_BY_PTYPE of interface IF_CLB_CUST_QUERIES.
You get an instance of the interface by calling CL_CLB_CUST_QUERIES->S_GET_INSTANCE().
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | S_CLB_REGISTRY | 0 | BYI3000385 | Social Media ABAP Integration Library |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| CLBVC_GW_SRV_C | C - View cluster | CLB_GW_SRV_C |
History
| Last changed by/on | SAP | 20121030 |
| SAP Release Created in | 740 |
